Sample: Query connections by reciprocal roles (early bound)
This sample shows how to create matching roles and then find a matching role for a particular role.
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
This sample shows how to create matching roles and then find a matching role for a particular role.
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.
- Defines some anonymous types to define the range of possible connection property values.
- The
ConnectionRole
creates the primary connection role instance. - The
ConnectionRoleObjectTypeCode
creates a connection role object type code record for account and contact table. - The
AssociateRequest
associates the connection roles.
Demonstrate
The QueryExpression
retrieves all connection roles that have this role listed as reciprocal role.
Clean up
Display an option to delete the records in Setup. The deletion is optional in case you want to examine the tables and data created by the sample. You can manually delete the records to achieve the same result.
反馈
https://aka.ms/ContentUserFeedback。
即将发布:在整个 2024 年,我们将逐步淘汰作为内容反馈机制的“GitHub 问题”,并将其取代为新的反馈系统。 有关详细信息,请参阅:提交和查看相关反馈