Unanswered

Systemusers table not including all users

(0) Share

Report

Posted on by siimgorczyca

Hi,

A few months/years back we prepared a solution that allows users 'inviting' new users to an application - in a model driven app they were able to select a user from the systemusers table, select which role they should get, which application should they receive access to, etc.

In the background, a power automate flow then gave the user the role and, if he didn't have one before, gave him a license.

That worked very well, because all the enabled users from AAD were present. However, recently we noticed that new users do not appear in the systemusers table. In MS documentation it states that to add a user to an environment, they need to have a license - but it wasn't the case earlier. So right now our solution, which helps to give users licenses, does not work properly, because you need to have a license in the first place to appear in the systemusers table...

Is this really the case that there was recently a change in this behavior, or am I missing something? Is there a workaround (other than replacing the systemusers table with the aaduser table)

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Devvj 1,132 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @siimgorczyca ,
To my understanding it have been this way for years, back OnPrem you could handle the user-table in a different way but for Online this have not been the case (for me anyway).
It have, however taken some (rather long) time for MS to enforce this on their customers, so i could be that you have not been affected until recently.
But the short answer is that they would need a "Dataverse"-license to be in the systemuser-table, yes...

Was this reply helpful? Yes No
ChrisPiasecki 6,426 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @siimgorczyca,

The only users that will be synced to the environment will be users assigned a Power Apps license, and members of the security group set on the environment (if one is applied).

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

Was this reply helpful? Yes No
ivan_apps 2,189 Moderator on at

Like (0)

Report
Copy link

Link copied!

Not sure if this trick works for all environments but I found that if you share a Model-Driven App url and the user accesses the link, it will take the user to the application and create the systemuser record automatically. It will then throw the access check error and tell them they need a license. But now the user is in Dataverse and you could potentially trigger a Flow that triggers after creation of the systemuser record to assign the license.

So instead of proactively creating user accounts and assigning licenses, you would reactively assign licenses when the user tries to access an app.

Was this reply helpful? Yes No