&sysparm_use_polaris=false Appending to Portal Page URL

[BehelC]

Our customer has a business need to allow users to manage notification preferences on the portal. I saw that there is an existing SN widget that will work for us, sys_platform_notification_preferences. The functionality is good but we needed to customize the widget as the customer didnt want all of the default options that the widget provides so we cloned it and threw it on a portal page. 

For some reason when we load the page with the cloned widget, it keeps appending "&sysparm_use_polaris=false" to the url and it breaks the widget/locks up the page. This happens before we've made any changes so the cloned widget is exactly the same as the OOB widget, which seems to work fine. 

Also of some note, if we put both the OOB widget and the cloned widget on the page, it works fine. Every once in awhile the page with just the cloned widget will work but I cant replicate a reliable pattern for that. 

Just wondering if anyone has a similar experience or a potential fix

has context menu. I've attached the widget for context. 

[Ramesh Lohar]

The issue you're experiencing seems to be related to the cloning of the widget. Here are some steps you can follow to troubleshoot and potentially fix the issue:

1. **Check the Cloned Widget Code**: Ensure that the cloned widget code is exactly the same as the original widget. Any minor changes or errors could cause the widget to malfunction.

2. **Inspect the URL Parameter**: The URL parameter "

For ServiceNow Live Classes, Books, Sample Resumes, Interview Questions, CSA Quizzes.
And getting better services's on ServiceNow you can visits our website.
Please visit : https://nowkb.com/home
Our Website :https://nowkb.com/home

[Michael O J]

Hi,

did you find the root cause here?

I'm experiencing the exact same behaviour with the Knowledge Field Facet (kb-field-facet), but only when I choose the Knowledge Base attribute on the Knowledge table. My cloned widget works fine when selecting the Category attribute.

[THOUSIF S N1]

Hello.. were you able to resolve this issue ? I have similar kind of problem can you please help me out?

[BehelC · Accepted solution]

Figured out the original widget had angular ng templates that were not copied as part of the clone. I had assumed cloning a widget would clone everything it needed so I just overlooked it. We had to copy the templates and change all of the names and references in the code to get it to work.