Caching problem with webrole

[GMB1]

Hi,

I have an onboarding process that triggers a power automate flow to assign a webrole to the user based on certain criteria. The flow is assigning the webrole and also updates the contact table with a value in order to make it clear that the flow has ended.

The issue is that even if the flow has ran and I can see the updates are done in dataverse, there is a delay before the new role is recognized on the site.

I have read that the cache can be refreshed by updating the relevant table with a PATCH or PUT request containing a timestamp or another unique value. I can't seem to make that work for the webroles. I am using the enhanced data model.

Does anyone have an idea on how to ensure the webrole is up to date when the user lands on the site?

Thank you!

[Fubar]

Wait 15 mins after the Web Role is assigned to the contact, and then send them an email.

(15 mins is Microsoft's SLA on the cache)

If the user is not already a portal user, the other way is to attach Web Roles to an Invitation record and send the  invitation to the contact, redeeming the invitation should give them permissions straight away. 

[GMB1]

This is what I will push for in the future but in this case, the registration is open. The onboarding script starts when the user arrives on the website after Azure B2C authentication.

Once the script finishes, the user is redirected to a role restricted page. 

It does work 50% of the time but I would need it to be more dependable.

Thank you for taking the time to answer Fubar!

[Fubar]

Part of your problem is that you are trying to assign based on some conditions - if no conditions can use the Authenticated User web role inheritance.

The other part of the problem with working around the cache is that you are using a Flow. Flow for dataverse is Asynchonous, if you move that logic into a realtime (synchnonous) workflow or plugin on create of the contact record, then from the portal you may be able to make a liquid fetchxml or web api call from the power pages page (e.g. Web Roles for the current user where created on date is less than or equal to today with today formatted to down to seconds) and in doing so pull the new data up.

[Akshay_Shah]

We are already create process for associate web role when user register themselves and it is working real time but facing same issue. it will redirect on home page or signin page automatically.

Please help us.

Thanks,

Akshay shah

[GMB1]

From what I've read, it seems like removing a webrole can take effect quicker than giving it. I would like to explore this approach as a possible solution to this cache delay during self registration.

Is it possible to assign custom roles by default ? Like adding other roles when the authenticated user role is assigned ? 

This is probably not a common use case but if anyone has a tip to share I would greatly appreciate it.

Thanks!

@Fubar  @OliverRodrigues (I hope it's okay to tag, you have great insigths) 

[OliverRodrigues]

"Is it possible to assign custom roles by default ? Like adding other roles when the authenticated user role is assigned ? "

Within the Web Role properties, there is a flag for "Authenticated Web Role", this is false by default for every custom web role and true by default for the Authenticated Web Role.

You can make this true for your custom Web Role and this will make your Web Role to be the default authenticated web role.

Please note that you need to change the OOB Authenticated Web Role with that setting to false then. You should only have 1 Web Role with that property set to true.

But in my opinion here, caching is very annoying during DEV/TEST of a project, however it's rarely an issue in a Live scenario, I think that waiting 15 mins to send the e-mail is a simple solution that should work.

[GMB1]

Ok great, I will give it a try after the testing phase is over.

As for the email part, I will push for the invitation method in the future but it was decided early on in the project that the registration was going to be open. The whole onboarding experience (creating the account or relating the user to an existing account and assigning the role) is automated and happens in real time while a loading screen is shown.

Thank you very much for shedding light on the subject!

[Fubar]

Note: as per Oliver's response only 1 Web Role can have the checkbox ticked - it will let you tick more, but your user will only inherit off one of them (if there are multiple the system will decide which one).