Has anyone had success activating Session-Based Permission Sets for Portal Users?
Use Case:
Displaying DataTable of Object A via Screen Flow on a community portal.
DataTable used is the UnofficialSF version.
One of the fields displayed is a lookup to Account. We want it to be a clickable link.
DataTable requires that the running user have Edit permission for Object A for the lookup to show up as a clickable link. Otherwise, it just shows up as the AccountId (unclickable).
I've created a Session-Based Permission Set called Temp Access that gives Edit permission to Object A.
I've created a flow that Activates the Session-Based Permission Set while the portal user is on the page.
Although the flow runs, according to the Setup Audit Trail, the Permission Set doesn't get Activated, so I don't get the desired clickable link.
One thing I noticed: when I assign the Permission Set to only Portal Users and run the Activate flow, I get an error: The permission set must be pre-assigned to the user before being activated. But if I assign the Permission Set to myself as well (Sys Admin), the flow "finishes" without error, but again, it doesn't actually activate the permission set.
Another thing I noticed: If I change the Permission Set to not be Session-Based, I get the desired clickable link. However, we cannot give Portal Users that much permission. It needs to be Session-Based.
Has anyone solved this for a session-based permission set applied to platform users? I've assigned the session-based permission set to the test user, but when I run it in debug, it throws the "The permission set must be pre-assigned to the user before being activated" error when it hits the Activate Session-Based Permission Set action.