You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: powerapps-docs/developer/data-platform/dataverse-odata-dataflows-migration.md
+8-4Lines changed: 8 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -1,19 +1,23 @@
1
1
---
2
2
title: Migrate data between Microsoft Dataverse environments using the dataflows OData connector
3
3
author: denisem-msft
4
-
ms.reviewer: "nabuthuk"
4
+
ms.reviewer: jdaly
5
5
description: Migrate data between Microsoft Dataverse environments using dataflows OData connector.
6
-
ms.date: 11/24/2021
7
-
ms.topic: "article"
6
+
ms.date: 10/03/2022
7
+
ms.topic: article
8
8
ms.subservice: dataverse-developer
9
9
ms.author: demora
10
10
search.app:
11
11
- PowerApps
12
+
contributors:
13
+
- JimDaly
12
14
---
13
15
14
16
# Migrate data between Microsoft Dataverse environments using the dataflows OData connector
15
17
16
-
18
+
> [!NOTE]
19
+
> Consider using the [Power Query Dataverse Connector](/power-query/connectors/dataverse) with Dataflows rather than the OData connector.
20
+
> Dataflows are the recommended method to migrate data between Dataverse environments. More information [What are dataflows?](/power-query/dataflows/overview-dataflows-across-power-platform-dynamics-365)
17
21
18
22
Dataverse [Web API](./webapi/overview.md) works with any technology that supports OData and OAuth. There are many options available to move data in and out of Dataverse. OData connector is one of the dataflows, which is designed to support migration and synchronization of large datasets in Dataverse.
Copy file name to clipboardExpand all lines: powerapps-docs/developer/data-platform/dependent-assembly-plugins.md
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -347,6 +347,10 @@ More information:
347
347
348
348
The following are known issues that should be resolved before dependent assemblies for plug-ins becomes generally available.
349
349
350
+
### Asynchronous plug-in steps do not work
351
+
352
+
If you use dependent assemblies for a plug-in registered for an asynchronous step an error with the message `Expected non-empty Guid.` will occur.
353
+
350
354
### Plug-in profiler
351
355
352
356
You cannot use Plug-in Profiler to debug plug-ins that are part of a plug-in package. More information: [Use Plug-in profiler](debug-plug-in.md#use-plug-in-profiler)
Copy file name to clipboardExpand all lines: powerapps-docs/developer/data-platform/developer-tools.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ Developers will use the following tools and resources when working with solution
24
24
25
25
*Power Platform Tools for Visual Studio* - supports the rapid creation, debugging, and deployment of plug-ins. Other capabilities currently in preview include development of custom workflow activities, web resources, integration technologies like Azure Service endpoints and webhooks, and more. To learn more about the tool, install the [extension](tools/devtools-install.md) and try the available [quickstart](tools/devtools-create-project.md) topics.
26
26
27
-
*Microsoft Power Platform CLI* - a simple, one-stop developer CLI that empowers developers and ISVs to perform various operations in Microsoft Power Platform related to environment lifecycle features, and to authenticate and work with Microsoft Dataverse environments, solution packages, portals, code components, and so on. To learn more about the tool, install the [extension](powerapps-cli.md#install-microsoft-power-platform-cli) or try the available [standalone](powerapps-cli.md#standalone-power-platform-cli) version.
27
+
*Microsoft Power Platform CLI* - a simple, one-stop developer CLI that empowers developers and ISVs to perform various operations in Microsoft Power Platform related to environment lifecycle features, and to authenticate and work with Microsoft Dataverse environments, solution packages, portals, code components, and so on. To learn more about the tool, see [What is Microsoft Power Platform CLI?](powerapps-cli.md).
Copy file name to clipboardExpand all lines: powerapps-docs/developer/data-platform/org-service/iorganizationservice-interface.md
+8-12Lines changed: 8 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
---
2
2
title: "IOrganizationService Interface (Microsoft Dataverse) | Microsoft Docs"# Intent and product brand in a unique string of 43-59 chars including spaces
3
-
description: "Learn about the common methods exposed to perform data operations with Microsoft Dataverse."# 115-145 characters including spaces. This abstract displays in the search result.
3
+
description: "Learn about the common web service methods exposed to perform data operations in Microsoft Dataverse."# 115-145 characters including spaces. This abstract displays in the search result.
The <xref:Microsoft.Xrm.Sdk.IOrganizationService> interface provides a set of methods used to perform the most common operations on system and custom tables and on the table definitions for your organization.
25
+
The <xref:Microsoft.Xrm.Sdk.IOrganizationService> interface exposes methods used to perform web service operations on system and custom tables and on the table definitions (metadata) for your environment.
26
26
27
27
## Client applications
28
28
29
-
This interface is implemented in a number of classes that you can use in your code when creating client applications.
29
+
This interface is implemented by a couple of classes that you can use in your code when creating client applications.
30
30
31
31
|Class|Description|
32
32
|--|--|
33
-
|<xref:Microsoft.Xrm.Sdk.Client.OrganizationServiceProxy>|This is the original low-level class which is used by WCF and the Organization service endpoint |
34
-
|<xref:Microsoft.Xrm.Sdk.WebServiceClient.OrganizationWebProxyClient>|This low-level class was created to enable OAuth authentication to the Organization service endpoint|
35
-
|<xref:Microsoft.Xrm.Tooling.Connector.CrmServiceClient>|This is the class you should use when creating .NET client applications. |
36
-
37
-
> [!NOTE]
38
-
> You may find older code or samples using the low-level <xref:Microsoft.Xrm.Sdk.Client.OrganizationServiceProxy> or <xref:Microsoft.Xrm.Sdk.WebServiceClient.OrganizationWebProxyClient> classes, but we recommend you use <xref:Microsoft.Xrm.Tooling.Connector.CrmServiceClient> for new .NET Client applications
33
+
|<xref:Microsoft.Xrm.Tooling.Connector.CrmServiceClient>|This is the class you should use when creating .NET Framework client applications. |
34
+
|<xref:Microsoft.PowerPlatform.Dataverse.Client.ServiceClient>|This is the class you should use when creating .NET Framework or .NET Core client applications. |
39
35
40
36
## Plug-ins
41
37
42
-
When you write plug-ins, there is also an object returned from the <xref:Microsoft.Xrm.Sdk.IOrganizationServiceFactory>.<xref:Microsoft.Xrm.Sdk.IOrganizationServiceFactory.CreateOrganizationService(System.Nullable{System.Guid})> which implements the <xref:Microsoft.Xrm.Sdk.IOrganizationService> interface but is not any of the types in the classes above.
38
+
When you write plug-ins, there is also an object returned from the <xref:Microsoft.Xrm.Sdk.IOrganizationServiceFactory>.<xref:Microsoft.Xrm.Sdk.IOrganizationServiceFactory.CreateOrganizationService(System.Nullable{System.Guid})> which implements the <xref:Microsoft.Xrm.Sdk.IOrganizationService> interface but is not any of the types in the service client classes above.
title: "Quickstart: Organization service sample (C#) (Microsoft Dataverse) | Microsoft Docs"# Intent and product brand in a unique string of 43-59 chars including spaces
3
-
description: "This quickstart will show you how to connect to the organization service of the Microsoft Dataverse"# 115-145 characters including spaces. This abstract displays in the search result.
4
-
ms.date: 04/03/2022
5
-
author: JimDaly
6
-
ms.author: jdaly
2
+
title: "Quickstart: Execute an Organization service request (C#) (Microsoft Dataverse) | Microsoft Docs"# Intent and product brand in a unique string of 43-59 chars including spaces
3
+
description: "Demonstrates how to connect to the Organization service of Microsoft Dataverse and execute a request."# 115-145 characters including spaces. This abstract displays in the search result.
In this quickstart, you will create a minimum console application to connect to the Organization service using the <xref:Microsoft.Xrm.Tooling.Connector.CrmServiceClient> class. You will pass your connection information using a connection string passed to the constructor.
24
+
This topic shows you how to begin using classes in the SDK for .NET assemblies to work with Microsoft Dataverse business data. You will create a minimal console application to connect to your environment's Organization service using the <xref:Microsoft.PowerPlatform.Dataverse.Client.ServiceClient> class and execute a web service operation.
26
25
27
-
You will use the <xref:Microsoft.Xrm.Sdk.IOrganizationService>.<xref:Microsoft.Xrm.Sdk.IOrganizationService.Execute*> method passing an instance of the <xref:Microsoft.Crm.Sdk.Messages.WhoAmIRequest> class, and you will display the <xref:Microsoft.Crm.Sdk.Messages.WhoAmIResponse>.<xref:Microsoft.Crm.Sdk.Messages.WhoAmIResponse.UserId> value.
26
+
Your application will call the <xref:Microsoft.Xrm.Sdk.IOrganizationService>.<xref:Microsoft.Xrm.Sdk.IOrganizationService.Execute*> method passing an instance of the <xref:Microsoft.Crm.Sdk.Messages.WhoAmIRequest> class. The result returned from the web service is a populated <xref:Microsoft.Crm.Sdk.Messages.WhoAmIResponse>.<xref:Microsoft.Crm.Sdk.Messages.WhoAmIResponse.UserId> value which is the unique identifier of your Dataverse system user account.
28
27
29
28
> [!NOTE]
30
-
> This quickstart example does not include error handling. This is a minimum example of what you need to connect to and use the Organization service.
29
+
> This quick start example does not include exception handling for brevity. This is a minimum code example of what you need to connect to and use the Organization service.
31
30
31
+
You can download the complete code sample from GitHub [quickstart-execute-request](https://github.com/microsoft/PowerApps-Samples/blob/master/dataverse/orgsvc/C%23-NETCore/GetStarted/quickstart-execute-request/).
32
32
33
33
## Prerequisites
34
34
35
-
- Visual Studio (2019 recommended)
35
+
- Visual Studio (2019 or later)
36
36
- Internet connection
37
-
- Valid user account for a Dataverse instance
38
-
- Your username
39
-
- Your password
40
-
- Url to the Dataverse environment you want to connect with
37
+
- Logon credentials of a Dataverse system user account for the target environment
38
+
- URL address of the Dataverse environment you want to connect with
41
39
- Basic understanding of the Visual C# language
42
40
43
41
## Create Visual Studio project
44
42
45
-
1. Create a new Console App (.NET Framework) project using .NET Framework 4.6.2
43
+
1. Create a new .NET console app project. For this project we are using Visual Studio 2022 and targeting .NET 6, but .NET Framework will also work.
46
44
47
45

48
46
49
-
> [!NOTE]
50
-
> This screenshot shows the name `OrgServiceQuickStart`, but you can choose to name the project and solution whatever you want.
51
-
52
47
1. In **Solution Explorer**, right-click the project you created and select **Manage NuGet Packages...** in the context menu.
Console.WriteLine("User ID is {0}.", response.UserId);
95
+
}
96
+
else
97
+
{
98
+
Console.WriteLine(
99
+
"A web service connection was not established.");
100
+
}
101
+
}
102
+
103
+
// Pause the console so it does not close.
103
104
Console.WriteLine("Press any key to exit.");
104
105
Console.ReadLine();
105
106
}
106
107
}
107
108
```
108
109
109
-
1. Editthefollowingvaluestoaddinformationforyour environment. You can find your environment URL in the Web application under **Settings > Customization > Developer Resources**.
110
+
1. Changethevaluesforthe environment URL, username, and password as indicated by the TODO code comment.
> You can find supported values for *AuthType* listed in [Connection string parameters](../xrm-tooling/use-connection-strings-xrm-tooling-connect.md#connection-string-parameters). YoucanfindyourenvironmentURLinthelegacywebapplicationunder**Settings>Customization>DeveloperResources**orinPowerApps**Settings** (gearicon) >**DeveloperResources**.
114
+
>
115
+
>Whilethiscodesampleplacestheusername/passwordinformationinthecodefor simplicity, other code samples will use the more recommended approach of prompting for that information or storing it in a separate App.config or appsettings.json file.
The console app demonstrates how to connect to the Organization web service using a connection string, execute a web service message request, and access some data in the response. Next, you may want to look at common web service data operations like create, retrieve, update, and delete.
0 commit comments