Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This sample shows how to serialize early-bound and late-bound entity instances into an XML format, and how to de-serialize from an XML format to an early-bound entity instances.
How to run this sample
- Download or clone the Microsoft/PowerApps-Samples repo so that you have a local copy.
- (Optional) Edit the
dataverse/App.configfile 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 don't specify a connection string in dataverse/App.config file, a dialog opens each time you run the sample and you need to enter information about which Dataverse instance 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.
Those samples in this repo that require a connection to a Dataverse instance to run include a linked reference to the dataverse/App.config file.
What this sample does
The DataContractSerializer message is intended to be used in a scenario where it Serializes and deserializes an instance of a type into an XML stream or document using a supplied data contract. This class cannot be inherited.
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.
- The
CreateRequiredRecordsmethod creates required sample data for the sample.
Demonstrate
- The
DataContractSerializermethod serializes the contact records into XML and write it to the hard drive. - The
earlyBoundSerializermethod deserializes the entity instance.
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.