I am building a context-driven Extensible Data Security (XDS) policy to restrict sales representatives so they can only view customer accounts that are explicitly assigned to them.
What is the recommended architectural approach for this? Specifically, how should the query and the MyConstruct temporary table be structured to dynamically link the current user session (Worker record) to the CustTable? Additionally, knowing that XDS policies are natively bypassed by OData endpoints, what is the best workaround to ensure this row-level security holds up if reps try to use the "Open in Excel" add-in?

Report
All responses (
Answers (