Sample: Remove a role for a user
This sample shows how to disassociate a role from a user by using the IOrganizationService.Disassociate method.
This sample requires an additional user that isn't available in your system. Create the required user manually in Microsoft 365 in order to run the sample without any errors. For this sample create a user profile as is shown below.
First Name: Dan
Last Name: Park
Security Role: No security role
UserName: dpark@yourorg.onmicrosoft.com
How to run this sample
- Download or clone the Samples repo so that you have a local copy.
- (Optional) Edit the dataverse/App.config file to define a connection string specifying the Microsoft Dataverse instance you want to connect to.
- Open the sample solution in Visual Studio and press F5 to run the sample. After you specify a connection string in dataverse/App.config, any sample you run will use that connection information.
If you do not specify a connection string in dataverse/App.config file, a dialog will open each time you run the sample and you will need to enter information about which Dataverse instance you want to connect to and which credentials you want to use. This dialog will cache previous connections so that you can choose a previously used connection.
Those samples in this repo that require a connection to a Dataverse instance to run will include a linked reference to the dataverse/App.config file.
What this sample does
The IOrganizationService.Disassociate message is intended to be used in a scenario where it deletes a link between records.
How this sample works
In order to simulate the scenario described in What this sample does, the sample will do the following:
Setup
- Checks for the current version of the org.
- The
CreateRequiredRecords
method creates the records required by the sample.
Demonstrate
- The
query
method retrieves a role from Microsoft Dataverse. - The
Disassociate
message removes the role to a team.
Clean up
This sample creates no records. No cleanup is required.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for