편집

다음을 통해 공유

Sample: Validate record state and set the state of the record

  • 아티클

This sample shows how to validate a change of state of an entity and set a state of an entity. 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:

  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.

What this sample does

The IsValidStateTransitionRequest message is intended to be used in a scenario where it contains the data that is needed to validate the state transition.

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 CreateRequiredRecords method creates any entity records that this sample requires.

Demonstrate

  1. The EntityReference method creates a EntityReference to represent open case.
  2. The IsValidStateTransitionRequest method sets the transition request to an open case.
  3. The checkState.NewState property checks if a new state of resolved and a new state of problem solved are valid.
  4. The IsValidStateTransitionResponse method executes the request.

Clean up

Display an option to delete the sample data that is created 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.