
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-12-2018 08:08 AM
I'm at a loss to figure out why this is happening. On the form widget on portal, I have one field that is not displaying the proper choice value. It does display on the back-end. The screenshots below were both taken on the same user account. This is the same record, same view on both portal and backend.
I've attached the images since Community doesn't seem to like embedding images for me.
Does anyone have any suggestions?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-12-2018 11:07 AM
So I figured out the issue - the parent request I was populating the field from had the value as "No" instead of "no". And since that wasn't a valid choice it wasn't showing on portal.
Let that be a lesson to me to check sources...

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-12-2018 08:48 AM
Hello,
Is this a custom field? If so, could you share the configuration of the field? what type, choice list specifications it has, etc.
if not, could you provide the field and table name?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-12-2018 09:02 AM
It's a custom field of type "String". The choices I have defined are
value: "no" / label: "No"
value: "yes" / label: "Yes"
It's configured as "Dropdown with -- None --"
I have another field on the same table with exactly the same configuration which is displaying fine in the form widget on the portal.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-12-2018 10:30 AM
Hmm ok. Do you have any client scripts or ui policies on this field?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-12-2018 11:07 AM
So I figured out the issue - the parent request I was populating the field from had the value as "No" instead of "no". And since that wasn't a valid choice it wasn't showing on portal.
Let that be a lesson to me to check sources...