Restricting Catalog Item visibility to specific customer segment

rahulchhibb
Tera Contributor

Hi All,
i have created an external catalog item called "Contact CSM" which should only be visible to customer belonging to account segment called Europe.

What i have done so far:

1. Added a user criteria (europe_customers_only) created with advanced script

2. linked this user criteria under Available For on the catalog item

Issue: 
- When i impersonate a non-europe customer, the catalog item still shows up in the portal.

- On opening the form, the account field shows the account name but throws "no records found" when selected.

Expectation:

- Non-Europe customers should not see the catalog item at all

- Only Europe customers should see & submit the form.

Has anyone run into this before? Am I missing something? Any pointers would be appreciated.

3 REPLIES 3

Josh Pirozzi
Kilo Sage

Hi @rahulchhibb,

 

Have you tried updating the OOB 'Available For' or 'Not Available For' on the Catalog Item? From here you can restrict visibility / access based on various User Criteria. 

 

Thanks,

Josh

dzmitryKon
Tera Contributor

User Criteria records work by evaluating conditions for the logged‑in user.
When a user sees the item despite not meeting criteria, either the user matches another “Available for” condition or the criteria script is incomplete.

Make sure the “Available for” list contains only the europe_customers_only criteria. Have you tested that your Advanced script working correctly? As per your explanation the issue is in User Criteria: which allows user to see wrong catalog item; and then catalogue item itself has some logic which is being broken because of bad user & related data

Nikhil Bajaj9
Tera Sage

Hi @rahulchhibb ,

 

Try user criteria [Available for/Not available for] and if required add code in advance script under user criteria.

 

Please appreciate my efforts, help and support extended to you by clicking on – “Accept as Solution”; button under my answer. It will motivate me to help others as well.
Regards,
Nikhil Bajaj