Редагувати

Поділитися через

Sample: Convert queries between FetchXML and QueryExpression

  • Стаття

This sample shows how to convert queries between FetchXML and QueryExpression.

SDK for .NET: Convert queries between FetchXML and QueryExpression sample code

How to run this sample

  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 Microsoft Dataverse 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 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 QueryExpression and fetchExpression messages are intended to be used in a scenario that contains queries in a hierarchy of expressions and FetchXML respectively.

How this sample works

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

Setup

  1. Checks for the current version of the org.
  2. The CreateRequireRecords method creates an account and two contact records that are used by the sample.
  3. The QueryExpression builds a QueryExpression to convert into FetchXML.
  4. The DoFetchXmlToQueryExpressionConversion class creates a Fetch query to convert into a QueryExpression.
  5. The conversionRequest method converts the generated QueryExpression into FetchXML and vice versa.
  6. Use the converted query to with a RetrieveMultiple request.

Clean up

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