How to Resolve "No Content to Display" in Service Operation Workspace (SOW) Carousel?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-28-2025 10:51 PM
Hi everyone,
I’m currently working with the Service Operation Workspace (SOW) in ServiceNow, specifically on the /now/sow/home page. However, I’m encountering an issue where the workspace displays the message:
No content to display
(But there should be)
The issue persists. Has anyone else encountered this problem? If so, how did you resolve it? .
Thank you in advance for your help!
Best regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-28-2025 11:54 PM
Can you share the config of the landing page? You say 'there should be', but you haven't told us what you are expecting there and how you configured that. From this information alone, the answer is going to be 'you need to configure it correctly so it shows'.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2025 03:51 AM
Mark,
That's the thing, it wasn't configured, it happened after the upgrade to Xanadu and I can't locate the config file of the landing page.
(instance).service-now.com/now/sow/home
I can't locate the config file for it, how would I do that?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-03-2025 01:08 AM
The landingpage is in the SOW Workspace and you can open it through the UI Builder.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2025 05:41 AM
That's how it should look like , from Xanadu developers instance
Seems like the data is not even passed to the carousel in my instance. Which widget or configurations would have to be adjusted via where in order to fix the issue?