Sample: Query connections by a record (early bound)
This sample shows how to query connections for a particular record. It creates connections between a contact and two accounts, and then searches for the contact’s connections. You can download the sample from here.
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:
- 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 instance/organization 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 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.
What this sample does
This sample creates account and contact records and creates connection roles between them. The QueryExpression
retrieves the connections for a particular record.
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 a connection role. - The
ConnectionRoleObjectType
creates a connection role object type code record for account entity. - Creates few account and contact records for use in the connection.
Demonstrate
The QueryExpression
retrieves all the connections associated with the contact created in the sample.
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.