Hi,
I have a PBI report that is embedded into a portal. The portal team would like to pass through the contactid (a GUID) to the PBI report for the report's Row Level Security (RLS) to consume so to restrict the viewing data.
I have built a PBI report that has Power Query (PQ) to accept this contactid and do the necessaryto restrict the data. However, when I confirgured the report's RLS roles and attempt a 'View as' and pass a contactid the report doesn't filter (doesn't restrict the data) but when I apply an email address (so the USERPRINCIPALNAME() ) as the 'View as' parameter the report does restrict the data. The table in the data-model is built to accept either a contactid or email to filter the report.
This tells me that a PBI report's RLS, the actual RLS mechanism itself, cannot accept a contactid as a parameter, passed from the portal, but instead can only accept a USERPRINCIPALNAME() as a valid RLS parameter.
Am I correct in my findings or can a contactid (GUID) be accepted as a RLS parameter for an embedded PBI report?
I would like to be sure before I respond back to the portal team informing them that only a USERPRINCIPALNAME() (or even the USERNAME() ) can be used.
Thanks.
