Form looks and works differently in different places
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2024 12:31 PM
I just spent 2 months creating a form and when we look at the form from the portal, it looks and works (or doesn't work) completely differently than when I would just click "Try it" from the editor.
refences don't have the searching of columns to find what you want, etc.
It ignores all javascript/ui policies. Reference fields work completely different and don't show all the columns for the thing being referenced.
Containers don't toggle, almost nothing works and I have absolutely no idea why.
If I do it from the editor with "try it" it works perfectly and looks completely different.
What am I missing?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2024 04:53 PM
When using a Database View as a reference, it only displays the Sys ID because Database Views lack native Sys IDs and behave differently from standard tables. Variable Attributes like ref_ac_columns
and ref_ac_display_value
do not work with views. To resolve this, use a standard table instead or build a custom widget/client script to display the required columns in the Service Portal.
Rampriya S
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2024 04:56 PM
ugg...
that makes this all SO much more difficult. is there any way to just default the form links to the non-dashboard version? People get to these through a cataglog page.
so dumb they display completely differently and have different functionality.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2024 05:25 PM
can you give me an example of how to use this dictionary thing to make it show more than field in the box in the dashboard view?
I think I can overcome this by creating the view in SQL and pushing a CSV to SN and importingf the data into a new table and then using that table but that box HAS to show more than just the display values and not being able to search via certain columns makes this absolutely terrible to use either way.
freaking stupid.....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2024 03:07 PM
I still get issues with javascript not working even though all ui policies and scripts are now set to all. Soon as the form loads it has thatr red box that says there is an error in your javascript console and I can't figure out what those are.
Containers do not roll up, is that not a thing on these forms outside of the "try it" section?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2024 06:18 AM
ok it seems like ServiceNow ONLY cares about the service portal experience for these things anymore and therefore things do not work, or were removed, etc to fit the service portal experience. Why do you still have a "try it" and "preview item" buttons/links that take you to the experience you no longer want people to use? Why is there no option to allow the non-service portal version to be used at all times?
I've spent 2 months working on something just to find this out 2 days before we wanted to launch it because we have all been using the "try it" button, where it works wonderfully.
Now I have to make absurd changes in order to make it work and look good on the service portal.