UI Builder - Context.props is not getting the sysID
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2023 08:37 AM
Hi,
I'm having trouble getting the sysId on the context.props in the UI Builder.
My requirement is to have a dynamic stepper to fetch the state from the current record.
In one page its working fine, but in another it isn't.
The sysId is already part of the parameters of the page:
Thank you for your help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2023 04:08 PM
Hello I am having a similar issue. Did you find any resolution? Thanks!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2023 01:27 AM
It's possible that there might be a configuration issue or a difference between the two pages that is causing the problem. To help you debug this issue, here are some suggestions:
-
Verify the parameter: Double-check that the sysId parameter is correctly defined in the non-working page. Compare the configurations of both pages to ensure there are no discrepancies in how the sysId parameter is set up.
-
Check the URL: Make sure the URL for the non-working page includes the sysId parameter. The URL should be in the following format:
https://your-instance.service-now.com/your_page.do?sysId=your_sysId
-
Inspect the data: Use the UI Builder's Data panel to review the data sources and properties being used in both pages. Make sure there are no differences in how the sysId is being passed through the data.
-
Debug the client script: If you're using a client script to fetch the sysId from context.props, add console.log statements to print out the values of context.props and the sysId for both pages. This can help you identify any differences or issues in the client script logic.
-
Verify component bindings: Ensure that the component bindings in the non-working page are correctly set up to use the sysId from the context.props.
---------------
Regards,
Rajesh Singh