Force Specific View (CAT) from Application Navigator Shortcut for Custom Table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2025 11:55 PM
Hi everyone 👋,
I encountered a common issue while working with a custom table in ServiceNow where I needed to create multiple views — in my case, one of them was named CAT. To simplify navigation, I added shortcuts for each view in the Application Navigator.
However, I noticed that clicking a shortcut sometimes loads the last-used view instead of the intended one. This happens because ServiceNow remembers the last view used for that table.
✅ Solution: Force the Correct View
To ensure the correct view (CAT) always loads:
- Go to the module configuration for the shortcut.
- Under the "Link Type" tab, choose:
- Link type: URL (from Arguments)
- In the Arguments field, use:
- sysparm_view=CAT specifies the view.
- sysparm_view_forced=true ensures ServiceNow forces this view to load, overriding the last-used one.
🛡️ Make Sure a View Rule Is Created
To ensure the CAT view is only shown under the right conditions, make sure a View Rule is created for your custom table.
📌 Note: If you're filtering records using a specific field like case_type, make sure the sys_id used in the query is correct.
Once the rule is in place, forcing the view using &sysparm_view_forced=true will work as expected and consistently load the correct layout.
This ensures the view is contextually relevant and doesn't appear where it shouldn't.
Note: The image used is for educational purposes only.
Let me know if you’ve tried something similar or have other tips to share 😊
- 968 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Friday - last edited Friday
This is helpful as certain views OOB may allow bypassing certain mandatory fields controlled via UI policy.
If they aren't on the form and the only thing mandating the field is a UI policy and not say the dictionary entry or a business rule, then users could bypass populating the field.
Also, just to add to this, if you work with Workspaces, this support article is helpful and explains how Workspaces don't respect this property and rely on other methods like Workspace Experience View Rules.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3038160
