- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2023 09:29 AM - edited 07-27-2023 11:15 AM
I have a Catalog Item where the user is selecting a supplier/vendor. I am using a Catalog Data Lookup Definition to pull in supplier info after a selection is made.
The problem I am having (edit: only on a portal) is that if a 2nd selection is made, and a matcher field is blank, it is not overwriting the previous value, even though "Always replace" is checked on the Catalog Setter Variable Definition.
As an example, if I select AT&T as the supplier, it populates the supplier info, including Contact name.
But if I then select Amazon Web Services, where the Contact name field is blank, the existing value is not getting replaced.
In the Catalog Setter Variable Definition "Always replace" is checked.
Anyone else encounter this and have a workaround? I would rather not have to script an Ajax call to get the data.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-15-2023 11:15 AM
Working with support, we found that this issue does not happen in Utah (patch 4). We were able to reproduce the issue in Tokyo (patch 9). So our solution was to upgrade to Utah.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2023 09:44 AM
Hi there,
In the Catalog Data Lookup Definitions form, you must check the "Run on form change". It'll setter the new value when you change the field value.
Regards,
Huy Lam
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2023 10:10 AM
Hi @Community Alums ,
Hope you are doing well.
I tried in my PDI but it was working , the value getting cleared if empty. So it should work OOB
Just out of curiosity could you please check if there is any UI policy/client script written on contact name field.
Regards,
Harshal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2023 10:56 AM - edited 07-27-2023 11:09 AM
I should have mentioned that this issue happens when viewing the catalog item on a portal. It also does not work in my PDI.
However it does work correctly when viewing the catalog item on the Now platform.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-15-2023 11:15 AM
Working with support, we found that this issue does not happen in Utah (patch 4). We were able to reproduce the issue in Tokyo (patch 9). So our solution was to upgrade to Utah.