Hi Chandan.
As you noted the SR is a SYSTEM level object and as such the SITE level restrictions will not automatically apply.
There is a SITEID and ORGID attribute on the SR, but as I tested it seems that even if those are populated the domain level filters do not apply. Someone else may prove me wrong on this, but that was the result of my initial tests.
You may look into adding a data restriction instead that is based on the SITEID and ORGID, but you would also need to consider if you populated the domain field and then changed the SITEID or if you allowed that to happen. That can all be handled with automation scripts, but it may get somewhat complicated as you work through all the permutations.
Regards,
Jason
------------------------------
Jason VenHuizen
Sharptree
https://sharptree.iohttps://opqo.io------------------------------
Original Message:
Sent: Mon September 16, 2024 05:09 AM
From: Chandan Singh
Subject: SR Application doesn't show site level domain values
Hello,
I have a need to show site level values for reported priority field in Service Request application, for e.g. Site-A wants to choose from values 1, 2 and 3 while Site-B would like to have only 1 and 2 in it's value list. I added site level values in the ticketpriority domain, which is associated with SR.REPORTEDPRIORITY field but site level values are never shown in the lookup, only system level values show up. I make sure siteid value is set and record is saved, but still the same outcome.
Any idea why? I know one reason, maybe because SR and TICKET is a system level object?
------------------------------
Chandan Singh
------------------------------