UI Policy not working on native view of record producer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-31-2025 09:03 AM
While working on record producer, when clicking on "try it" UI action, the Catalog UI policies are not working on the view that appears(catalog_cat_item_view). The same catalog UI policies are working on the portal view. Is there a way we can fix it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-31-2025 09:50 AM
Hi @Shivalika ,
The UI Policy is making few catalog variables visible and mandatory on certain condition.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-31-2025 09:52 AM
@Swapnil Srivas1 what type of variables ?
Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket.
Regards,
Shivalika
My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194
My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-31-2025 09:54 AM
Yes/No, string, date/time, reference. These variables are mapped to backend table fields.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-31-2025 04:55 PM - edited ‎03-31-2025 04:56 PM
These standard UI policies should work in the platform view with the Try It button. Are you in the right scope? It's possible you have other conflicting UI policies that are keeping them hidden. Also, make sure that UI Policy Actions have different Order numbers so not too many are trying to execute at the same time.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-31-2025 07:58 PM
Hii @Swapnil Srivas1
I read your question again and it's a record producer. Which means that it's backend name and the field in the target record backend name should be same. This definitely happens with record producers due to this conflict that it will not reflect in native view. Because in native view system has access to both.
Instead of you want it to reflect on target record, you can select the checkbox "Applies on target record" in your UI policy. But there is doubtable feasibility of if working in native view if the field names are completely same as you mentioned "you have done mapping".
Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket.
Regards,
Shivalika
My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194
My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY*
