تحرير

مشاركة عبر

Sample: Enable field security for an entity

  • مقالة

This sample shows how to enable field security for an entity. You can download the sample from here.

This sample requires additional users that are not in your system. Create the required users manually in Office 365 in order to run the sample without any errors. For this sample, create a user profile as is shown below.

First Name: Samantha
Last Name: Smith
Security Role: Marketing Manager
UserName: ssmith@yourorg.onmicrosoft.com

Note

This sample applies to both Dynamics 365 Customer Engagement (on-premises) and Dataverse.

How to run this sample

To obtain a local copy of all samples and build them, follow these steps:

  1. Download or clone the Samples repo so that you have a local copy.
  2. (Optional) Edit the dataverse/App.config file to define a connection string specifying the instance/organization you want to connect to.
  3. 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 don't specify a connection string in dataverse/App.config file, a dialog opens each time you run the sample, and you'll need to enter information about which instance or org you want to connect to and which credentials you want to use. This dialog caches previous connections so that you can choose a previously used connection.

How this sample works

In order to simulate the scenario described above, the sample will do the following:

Setup

  1. Checks for the current version of the org.
  2. Gets the user that you have created manually in Office 365.
  3. Retrieve the security role needed to assign to the user.
  4. Retrieve the default business unit needed to create the team.
  5. Instantiate a team entity record and set its property values.

Demonstrate

  1. Creates field security profile and create the request object and set the monikers with the teamprofiles_assocation relationship.
  2. Creates custom activity entity and attributes using the CreateEntityRequest and CreateAttributeRequest message.
  3. Create the field permission for the identity attribute.

Clean up

Display an option to delete the records in Setup. The deletion is optional in case you want to examine the entities and data created by the sample. You can manually delete the records to achieve the same result.