Dashboard URL is giving an error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2025 12:33 AM
Hi Team,
We have non admin users facing issue after upgrade from Xanadu to Yokohama the below URL used to work before for the user but not now.
Instance namenow/nav/ui/classic/params/target/%2F%24pa_dashboards_overview.do%3Fsysparm_border%3Dtrue
now giving error as {{ setEmptySearchResultMessage(); }}.
No issue for same user in dev and test but can be seen in prod . If we reload the form it is working fine and observed after Reload
instance name /
now/nav/ui/classic/params/target/%24pa_dashboards_overview.do%3Fsysparm_border%3Dtrue.
The only difference observed is %2F% is available in first instance.
Can someone suggest what may be the rootcause ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2025 02:27 AM
raise a case as this happened after the upgrade.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2025 02:44 AM
Go to System Definition -> Plugins and check for any updates available for plugins Platform Analytics, UI builder and Data Visualization components. If yes, update it to latest version, clear the cache using /cache.do, logout and login again.
I have seen random issues happening when plugins are outdated and updating it helps to fix random unexpected behavior.
If this helped to answer your query, please mark it helpful & accept the solution.
Thanks,
Bhuvan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2025 04:24 AM
Hi @Pooja P ,
This seems related to URL encoding changes after the Yokohama upgrade. The issue occurs because %2F (which represents “/”) is being handled differently, causing the page to fail to load correctly for non-admin users.
After reload, the URL is interpreted without %2F, which is why it works fine.
You can refer to these discussions — they explain similar behavior and possible fixes:
🔗 URL encoding changing “%2F” to “/”
🔗 UI Action – remove the %2F in URL
If my response helped, please mark it as the accepted solution so others can benefit as well.