Where is located the teammembership Entity in Common Data Service and how can I use it ?

(0) Share

Report

Posted on by Arioule

156

Hi,

I have added members to one of my teams defined in the Team entity.

It seems that there is a Many to Many relationship between the Team Entity and the User Entity and teammembership is the Relationship entity name.

However I can not find this teammembership Entity in the CDS.

So I was wondering where is it actually located.

What I want to achieve :

I would like :

- To make the entity that contains team members available in my Model Driven App via the Site Map

- To implement a flow that will be triggered whenever an add or updated event occurs on this entity

How can I do this ?

Also, Teams I have created so far are Owner Team Type. But what is the difference between Owner and Access Type ?

Thanks,

Arioule

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (6)

Answers (1)

v-xida-msft on at

Like (1)

Report

Hi @Arioule ,

Based on the issue that you mentioned, I think you have some misunderstanding on the relationship in CDS Entities.

Currently, within CDS, the Users Entity and the Teams Entity are related together through the "teammembership_association" relationship (Many-to-Many). There is no actual Entity in CDS to store the relationship between the Teams Entity and Users Entity.

More details about the Relationship in CDS, please check the following article:

https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/create-edit-entity-relationships

For your first question, I suppose that you want to display Team Members for specific Team in your Model-Driven app, is it right? Based on the needs that you mentioned, I think the Sub-Grid control in Model-Driven app form could achieve your needs.

On your side, you could consider create a Model-Driven app based on your Teams Entity. Edit the Main Form of your Teams Entity, then add a Sub-Grid component into it as below:

then click "Save"-> "Publish" to publish your changes you made to your Team Entity Main Form. After that, edit your Model-Driven app, enable above Teams Entity Main Form as the Only Edit Main Form. Then publish your Model-Driven app.

When you run your Model-Driven app, and edit one Team record, the related Team Members would be show up in above Subgrid section. Within that section, you could also add new members to this Team.

For your second question, do you want to fire a flow when add or updated event occurs on teammembership Entity? I afraid that there is no way to achieve your needs in PowerApps currently.

If you would like this feature to be added in PowerApps, please consider submit an idea to PowerApps Ideas Forum:

https://powerusers.microsoft.com/t5/Power-Apps-Ideas/idb-p/PowerAppsIdeas

Best regards,

Was this reply helpful? Yes No
Arioule 156 on at

Like (0)

Report

Hi @v-xida-msft,

First, thanks for answering me.

I would like also to ask 2 more questions :
1 - Is it still possible to get the list of a cds team member (or to add/remove members in a cds team) using flow and how to do it ?
2 - What is the difference between Owner and Access Type when you create a cds team ?

Thanks a lot again for your help,

Arioule

Was this reply helpful? Yes No
Verified answer

v-xida-msft on at

Like (0)

Report

Hi @Arioule ,

For your first question, do you want to add or remove members in a CDS Team using Power Automate flow or workflow? I afraid that there is no way to achieve your needs using Power Automate flow or workflow.

Actually, the needs that you want to achieve is that you want to relate or unrelate a member to a specific Team, is it right? Based on the needs that you mentioned, I think the Relate function or Unrelate function in PowerApps app could achieve your needs.

Please check and see if the following article would help in your scenario:

https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/functions/function-relate-unrelate

For your second question, An owner team owns records and has security roles assigned to the team. The team's privileges are defined by these security roles. The access team doesn't own records and doesn't have security roles assigned to the team. The team members have privileges defined by their individual security roles and by roles from the teams in which they are members.

Please check the following article for more details:

https://docs.microsoft.com/en-us/power-platform/admin/manage-teams#about-group-teams

If above reply is helpful in your scenario, please consider go ahead to click "Accept as Solution" to identify my reply as helpful.

Best regards,

Was this reply helpful? Yes No
Kiki 31 on at

Like (0)

Report

Thanks a lot for your help

Was this reply helpful? Yes No
R4isin 76 on at

Like (0)

Report

Hello,

I guess that you found an alternative or a workaround since June but it's possible to add a systemuser (from CDS/Dataverse) to a Team (from CDS/Dataverse) via a step in Power Automate (can be useful if someone passes by here 😉 ).

For this, you need to use the action "Perform a bound action" from the CDS Connector.

Firstly, you choose the "Teams" entity as input for "Table Name" and the "AddMembersTeam" as input for "Action Name".

When it's done, you need to specify the "team" and the "systemuser" which must be linked.
For the team, you just need to put the guid of your involved team in the field "Item ID" (simple for this one)
For the systemuser, you need to "switch to input entire array" (to have the field "Members")
and when it's done, you can add the guid of you users as showed below (with the key word "ownerid”). And because it's an array of Members, you need to put the brakets [ ])
And after the save, the "Members" field will become something like that (
You have now a Power Automate which adds a user (CDS) to an owner team (CDS) 😋

Kr,

R4isin

Was this reply helpful? Yes No
Fubar 8,350 Super User 2025 Season 2 on at

Like (0)

Report

Just adding to this as it is possible via both Flow (as highlighted by @R4isin ) and it is also traditional Workflow using a custom workflow activity such as what is available in this library https://github.com/demianrasko/Dynamics-365-Workflow-Tools

Was this reply helpful? Yes No