Sample: Retrieve records from an intersect table

This sample shows how to retrieve records from an intersect table. You can download the sample from here.

How to run this sample

  1. Download or clone the Samples repo so that you have a local copy.
  2. (Optional) Edit the cds/App.config file to define a connection string specifying the Common Data Service instance 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 cds/App.config, any sample you run will use that connection information.

If you do not specify a connection string in cds/App.config file, a dialog will open each time you run the sample and you will need to enter information about which Common Data Service 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 Common Data Service instance to run will include a linked reference to the cds/App.config file.

What this sample does

The QueryExpression message is intended to be used in a scenario that contains queries in a hierarchy of expressions.

How this sample works

In order to simulate the scenario described in What this sample does, the sample will do the following:

Setup

  1. Checks for the current version of the org.
  2. The CreateRequireRecords method creates entity records that are used by the sample.
  3. The QueryExpression message is used to retrieve the default business unit needed to create the team.
  4. The WhoAmIRequest gets the GUID of the current user.
  5. The Role message instantiate a role entity record and set its property values.
  6. The AssociateRequest assigns the user to the Managers role.

Demonstrate

  1. The QueryExpression retrieves the records from an intersect table.
  2. The RetrieveMultipleRequest builds the fetch request and obtains the results.

Clean up

  1. Display an option to delete the records created in the 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.