Microsoft.PowerPlatform.Dataverse.Client 0.6.1

Prefix Reserved
There is a newer version of this package available.
See the version list below for details.
dotnet add package Microsoft.PowerPlatform.Dataverse.Client --version 0.6.1                
NuGet\Install-Package Microsoft.PowerPlatform.Dataverse.Client -Version 0.6.1                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Microsoft.PowerPlatform.Dataverse.Client" Version="0.6.1" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Microsoft.PowerPlatform.Dataverse.Client --version 0.6.1                
#r "nuget: Microsoft.PowerPlatform.Dataverse.Client, 0.6.1"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Microsoft.PowerPlatform.Dataverse.Client as a Cake Addin
#addin nuget:?package=Microsoft.PowerPlatform.Dataverse.Client&version=0.6.1

// Install Microsoft.PowerPlatform.Dataverse.Client as a Cake Tool
#tool nuget:?package=Microsoft.PowerPlatform.Dataverse.Client&version=0.6.1                

This package contains the preview of the .net core Dataverse ServiceClient. Used to connect to Microsoft Dataverse. This Package has been authored by the Microsoft Dataverse SDK team.

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp3.1 is compatible. 
.NET Framework net462 is compatible.  net463 was computed.  net47 was computed.  net471 was computed.  net472 is compatible.  net48 is compatible.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (94)

Showing the top 5 NuGet packages that depend on Microsoft.PowerPlatform.Dataverse.Client:

Package Downloads
Microsoft.PowerPlatform.Dataverse.Client.Dynamics

This package contains a set of Dynamics 365 specific extensions, used with the Dataverse ServiceClient. This Package has been authored by the Microsoft Dataverse SDK team.

Rystem.RepositoryFramework.Infrastructure.Dynamics.Dataverse

Rystem.RepositoryFramework allows you to use correctly concepts like repository pattern, CQRS and DDD. You have interfaces for your domains, auto-generated api, auto-generated HttpClient to simplify connection "api to front-end", a functionality for auto-population in memory of your models, a functionality to simulate exceptions and waiting time from external sources to improve your implementation/business test and load test.

Microsoft.Dynamics.Sdk.Messages

This package contains the preview of the .net core Dynamics Messages Assembly. Used to issue commands to Dynamics Applications Installed on Microsoft Dataverse. This Package has been authored by the Microsoft Dataverse SDK team.

FakeXrmEasy.Abstractions.v9

FakeXrmEasy is the open source test automation framework for .net core and the Power Platform / Dataverse. This is an abstractions package containing only interfaces.

FakeXrmEasy.Core.v9

FakeXrmEasy is the open source test automation framework for .net core and the Power Platform. This is the core package containing a configurable middleware, crud operators, and query translation between FetchXml, QueryExpression, CRM LINQ, and QueryByAttribute.

GitHub repositories (4)

Showing the top 4 popular GitHub repositories that depend on Microsoft.PowerPlatform.Dataverse.Client:

Repository Stars
microsoft/PowerApps-Samples
Sample code for Power Apps, including Dataverse, model-driven apps, canvas apps, Power Apps component framework, portals, and AI Builder.
Avanade/Liquid-Application-Framework
Liquid Application Framework documentation, useful links and sample project
microsoft/PowerPlatform-DataverseServiceClient
Code Replica for Microsoft.PowerPlatform.Dataverse.Client and supporting nuget packages.
neronotte/Greg.Xrm.Command
Command Line utility for Dataverse
Version Downloads Last updated
1.2.2 4,443 11/7/2024
1.1.32 484,243 8/10/2024
1.1.27 155,871 7/10/2024
1.1.22 240,160 4/25/2024
1.1.17 418,333 1/8/2024
1.1.16 208,757 11/8/2023
1.1.14 354,101 8/24/2023
1.1.12 161,708 7/14/2023
1.1.9 157,760 6/8/2023
1.0.39 800,689 3/13/2023
1.0.26 478,900 11/4/2022
1.0.23 101,354 10/10/2022
1.0.9 275,006 7/19/2022
1.0.4 40,245 7/7/2022
1.0.1 377,924 6/13/2022
0.6.6 138,175 4/25/2022
0.6.1 201,994 3/9/2022
0.5.17 220,237 1/7/2022
0.5.10 191,220 10/22/2021
0.5.7 79,621 10/15/2021
0.5.5 20,386 10/5/2021
0.5.4 2,013 10/4/2021
0.5.2 41,894 9/24/2021
0.4.21 83,574 8/17/2021
0.4.20 21,466 7/30/2021
0.4.19 8,891 7/27/2021
0.4.12 132,511 4/28/2021
0.4.11 33,354 4/13/2021
0.4.6 20,468 3/25/2021
0.4.4 22,012 3/8/2021
0.4.3 39,260 3/5/2021

Notice:
   This package is in a public preview release.
   This package is intended to work with .net full framework 4.6.2, 4.7.2 and 4.8, .net core 3.1, 5.0 and 6.0
   General Documentation is the same as CrmServiceClient and can be found here:
       https://docs.microsoft.com/en-us/dotnet/api/microsoft.xrm.tooling.connector.crmserviceclient?view=dynamics-xrmtooling-ce-9
   Connection String Docs can be found here:
       https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/xrm-tooling/use-connection-strings-xrm-tooling-connect
   Note: that only AD on FullFramework, OAuth, Certificate, ClientSecret Authentication types are supported at this time.

0.6.1:
Minor Bump to 0.6.x - *Should* be last bump prior to 1.0.

Added initial support for AD auth for OnPremise.  This will work for full framework only.
Added new constructor that will accept a ConnectionOptions class and a ConfigurationOptions Options Object.  This constructor is currently not fully implemented.
   This is prep work for a builder process and intended to unify the connection flow to a single constructor at some point in the future.
   The goal of this work will be to resolve the issues caused by lazy loading hosts.
Fixed a bug in Logger when working with Connection Strings where log events would not be correctly generated.
Speculative fix for GIT issue #219 and #220
Fixed a bug where LastError was not properly reset, fixed Git #229
Fixed Error message issue between onPrem and onLine , Fixed Git #232
Added configuration support to allow for better memory management of very large return sets,  Git #207
   New AppSetting is called "MaxBufferPoolSizeOveride" - there is currently not a way to set this via code at runtime.
   Support for configuration of this will be added as part of the new Constructor for .net core, .net framework can use it by setting the appsetting value now.
Fixed exceptions not being thrown from several paths during login flows.

-- WARNING --
.net 3.0 Target Removed from Nuget packages.
REFACTORED helpers and utilities for the DataverseServiceClient into the Microsoft.PowerPlatform.Dataverse.Client.Extensions Namespace of the DataverseClient.
Dependency changes:
   Removed Microsoft.Dynamics.Messages.Sdk.nuspec for Dynamics messages at this time.  This will return in the future in some form.
   Removed Microsoft.Cds.Sdk.Proxy.dll from Package and replaced with Microsoft.Crm.Sdk.Proxy.dll in package.
   System.Text.Json moved to 6.0.2 min dependency.
       -- Note: As of this writing, when using Azure functions you cannot use Microsoft.Net.Sdk.Functions.3.0.12 or .3.0.13 due to blocks on System.Text.Json dependencies.  You need to either use .3.0.11 or move up to 4.x
   System.ServiceModel.Http moved to 4.9.0 due to internal dependencies on Microsoft.Xrm.Sdk


0.5.17:
Accepted fix requested here: https://github.com/microsoft/PowerPlatform-DataverseServiceClient/issues/205
 fixing delete by alternate key request in client.
Fixed dependency issue for System.Security.Premisions  (git #203)  
Refactored AuthorityResolver to discover AAD authentication authorities to allow for direct access by other clients.


0.5.10:
Added new property "RecommendedDegreesOfParallelism".
   This property will report the recommended number of threads for communicating with Dataverse.

0.5.8:
Changed internal dependencies to better align with Dataverse Server.
Fixed an issue with updating ManyToOneRelationship based attributes.
Fixed an issue with activity parties relationships.

0.5.7:
Removed Sealed attribute from the Service Client Class.
Fixed an issue with null values being sent to the API causing a null exception to be raised.
Fixed missing nuget dependency for Microsoft.Identity.Client.Extensions.Msal, Nuget now properly includes that package.

0.5.5:
Fixed a nuget dependency issue for Microsoft.Extensions.Caching.Memory
   Microsoft.Extensions.Caching.Memory, min version 3.1.8

0.5.4:
Fixed and issue with the client being non-castable to IOrganizationServiceAsync, Client will now cast again. (Internal Report)
   Special note:
       IOrganizationServiceAsync has async methods without cancellation support. this is required for service mapping as the dataverse server does not natively support this feature.
       IOrganizationServiceAsync2 has async methods WITH cancellation support.  
       This surfaces in the client as 2 forms of each async method and is currently necessary to support internal auto generation of contracts for service communication. We will work to improve this in the future.
       Cancellation events will currently raise an OperationCancelled Exception, this can either be the topmost exception, or embedded in a DataverseException.
       Cancellation methods are 'preferred' if you need to support cancellation in your application.
Fixed an issue with External authentication type not being properly passed though to cloned clients.  (git #162)

0.5.2:
***** Breaking Changes *****
Removed the constructor:
   public ServiceClient(OrganizationWebProxyClient externalOrgWebProxyClient, ILogger logger = null)
       Removed as we are refactoring how we will accept an external created client for internal use cases.
Contract change:
   Added Support to set token file storage location back to connection string and constructors supporting User Authentication.
   Modified DiscoverOrganizationsAsync to return a new return object called DiscoverOrganizationsResult
   Modified Exception type thrown when external authentication fail to return DataverseOperationExecption vs general exception.

Updates:
Accepted suggestion to Updated logic to detect SDK runtime version for client.  Thanks to GitHub user 0xced
Updated behavior of Token refresh to reduce cache hits, Optimized token lookup for cache hits over network calls.
Added Handlers to support timeouts from AAD Token service. (GIT #148)
Added InMemory Token Cache system for S2S flows. (GIT #144)
   This pulls a new dependency on Microsoft.Extensions.Caching.Memory, min version 5.0.0
Added FileToken Storage Provider back into Client - works for User Access flows only... Does not work for S2S accounts.
Added configuration override support for setting MSAL Token Acquire Timeout, Retry Count, and MSALPIILogger
   MSAL Token Timeout control : appsetting = MSALRequestTimeoutOverride,  default is 30 seconds.
   MSAL Token Acquire retry count: appsetting = MSALRequestRetryCountOverride, default is 3.
   MSAL Allow PII in Log data: appsetting = MSALLogPII, default is false
Updated Async Implementation older SDK flow ( non-OData ) which should improve thread support. (Git #146)
Updated Internal interaction behaviors for communication to Dataverse Server
   Added temp properties to allow for field control of this if the behavior does not work as intended.
Fixed an issue where an Guid.Empty Session ID was set the server.
Fixed an issue where Create and Update Operations would not properly respect API allowed fields for create or update. (Git #163)
Fixed an issue where logical name was being used instead of Schema name for Activity parties (Git #166)

0.4.20:
Fixed Connection Creation "Hang" behavior that could occur when trying to create a Dataverse Service Client inside a thread.
Fixed an issue with ILogger not propagating correctly when used with connection string flows.
Fixed an issue when attempting to Null a lookup that would cause a Microsoft.OData.ODataException: Does not support untyped value in non-open type error
Changed the behavior of Update message to be consistent with Organization Service Update behavior instead of an Upsert behavior.
Added compensating code to deal with a null ref issue when logging which could cause a client crash.
Added optional WebAPI support during login and solution import & export operations
Refactored ServiceClient and ConnectionService

0.4.19:
Updated behavior of ImportSolutionAsync to leverage updated Dataverse behavior post 9.2 release.
Updated Display name for Northamerica 2 Region to reflect that it is more commonly know as GCC.
Updated Newtonsoft.Json to v11.0.2 to match server.
Fixed an issue with ActivityParty when using an Entity Array vs an EntityCollection for ActivityParties

0.4.12:
Fixed an issue raised when updating some entities\attributes values to null.
Fixed and issue with DataTime formatting for Timezone independent, Timezone specific, and 'normal' DateTime types.
Update for Current Dataverse System Messages.

0.4.11:
Update for Current Dataverse System Messages.
Fixed an issue where authentication could fail during throttling due to token not being refreshed on retry.
Adding Exception behaviors for all Metadata Operations.
Adding EnableAffinityCookie to allow for override of Affinity behavior when interacting with Dataverse.
   In general, users should not manipulate this property. more details can be found here: https://docs.microsoft.com/en-us/powerapps/developer/data-platform/api-limits#remove-the-affinity-cookie
Adding support for enhanced features for solution import.

0.4.6:
Exposing ILogger support on all constructors and Static API commands.

0.4.4:
Added support for related entity create as part of general "create" operation.
Updated Async Operations to return task's for async methods that were returning void's
Updated DataverseOperationException to include HttpOperationResponse, where it exists.
Fixed issue with Cloned Connections not refreshing their tokens on token expiration
Updated Logger to remove string builder property
Added Initial code for ILogger implementation. (Not exposed as of yet but coming soon)
Corrected an issue when using the Entity myEnt = new Entity(string, guid) not properly setting the primary id.

0.4.1:
Supersedes Microsoft.PowerPlatform.Cds.Client,  Previous nuget has been retired.
***** MAJOR Breaking Changes *****
Complete renaming of CdsServiceClient for Dataverse naming.
Major differences:
   Namespace: Microsoft.PowerPlatform.Cds.Client =>  Microsoft.PowerPlatform.Dataverse.Client
   CdsServiceClient is now ServiceClient
   All methods in CdsServiceClient that had Cds in the name have been updated to remove cds Name
   Exception's have been updated to
       CdsConnectionException => DataverseConnectionException
       CdsOperationException => DataverseOperationException


0.3.10-Alpha:
Initial async implementation of SDK Client. - note this is a WORK IN PROGRESS and may not work as expected under all circumstances.
   Please report bugs or behaviors issues in the normal way
Fixes and issue with exceptions being thrown by code that is supposed to log exceptions.
Corrected issue with DateOnly data types when using CUD events.
Included additions to logging when failures occur during connection string based login. - credit to GIT:@nicknow for the suggestion of fix.

0.3.6-Alpha:
Fixed an issue where Activity Party types were not being properly processed
Fixed an issue where the incorrect format was used for Data only types.
Fixed an issue where BypassPluginExecution property on request was not being understood properly by the server.

0.3.1-Alpha
***** Breaking Changes *****

MSAL Port completed.
   Auth processes have been ported to MSAL.
   UserID/PW flows are now enabled on .net core for login where possible ( per AAD security rules and host OS)
   Auth flow Logging capture is still under development.

Authentication constructors are now updated to remove some ADAL.net patterns
Removed Token Cache path from constructors and ignore on connection string at this time
   Token Cache handle support will be revisited, however if you have a pressing need, we recommend you use the external token management constructor in the mean time and self manage that.
   For now, only MSAL In-Memory support will be provided for token cache
Refactored to support Shared HTTPClientFactory for WebAPI connections to cut down on some noise for folks that are doing repeated logins.
Refactored code a bit to help with clarity on various functional areas.
Renamed/Refactored Discovery methods to as Async methods.


0.2.31-Alpha:
Rerouted all Upsert Request to use OrganizationService API.
Added new InMemory Logging Options to support returning Logs captured either as Array of Tuples or a string list.
Added new public property for OrganizationDetail Information called "OrganizationDetail" for the currently connected environment.
Added new enum for ImportSolution additional property options called "ImportSolutionProperties" - this contains valid options for additional properties for the ImportSolution handler
Fixed an issue with telemetry for the client that was using incorrect format for useragent content
Updated Core CDS Sdk assemblies

0.2.24-Alpha:
Fixed an issue with .Clone not correctly supporting adding telemetry handlers to cloned connections

0.2.23-Alpha:
Adding Switzerland Geo to Regions List.
Added support for Alternate key use on entity references as part of Create Update Delete Operations running over the webAPI.
Added concurrency support to Create Update Delete Operations running over the webAPI.

0.2.17-Alpha:
***BREAKING CHANGE***
Renamed Exception CdsConnectionException to CdsClientConnectionException.  No other change to the Exception
***
Improved handling of cached connection retrieval failures from memory when an invalid object is returned.
Fixed a bug where a WebAPI navigation property did not match with its metadata descriptor.
Fixed Retry delay issue when making calls to the CDS WebAPI – thanks to GIT user stvonolf for the catch of this issue.
Added new Exception, CdsClientOperationException - this will be used when an exception is raised via the CDSClient when CDSClient is using WebAPI.
Added IntelliSense Doc Support
Added support for bypassing custom Plug-in Execution during SDK Operation.
   This is a special use capability that requires a specialized permission in the CDS infrastructure to use.
   Currently this is only permitted for use by users that have the System Administrator Security Role.

0.2.16-Alpha:
Fixed issue when CUD via WebAPI when entity contains a entity reference that is a polymorphic reference. ( IE customer data type )

0.2.15-Alpha:
Corrected a bug in Org request to WebAPI operation when attempting to set fields to null values.
Added initial support for in memory log capture support.

0.2.14-Alpha:
Update to internal support libraries

0.2.8-Alpha:
Fixed an issue with sovereign cloud discovery reference data that would prevent a future login control from picking the correct global discovery server.

0.2.7-Alpha:
Fixed missing ConfigureAwait on ADAL Authority acquire flow.
Added some additional logging to understand what version of ADAL is being used.
Fixed an issue with translation of Money types to WebAPI requests.

0.2.5-Alpha:
Fixed Authority property data loss post clone process
Added temp logic to run upsert requests that have anything other than string keys via the Native OrgAPI vs webAPI, this is a workaround for an open issue with the webAPI where it does not support none string key's on upsert(patch) requests that result in a create operation.
Rerouted CdsServiceClient Helpers to use WebAPI path for CUD requests.

0.2.2-Alpha:
Several updates to Create / Update / Delete operations to move the underlying features over to use the WebAPI.
Please report any bugs that you run into with this.  This has been "mostly" tested with our current test suite, however we have not full tested all data type translation at this point.

0.2.1-Alpha:
BREAKING CHANGE!!!
Altering Nuget Version to 3 digit semantic version
Namespace change from Microsoft.Powerplatform.xxxx to Microsoft.PowerPlatform.xxxx
Fixed an error with setting CallerId when ClientSecret Auth type is used.
   Thanks for all the bug reports on this and repro's that really helped us run it down.

0.0.1.11-Alpha:
Fixed a number of discovery related issue that were broken during the port.
Added new forms of DiscoveryGlobalOrganziations to allow for a token function to be passed to enabled this for use in WebSites and functions where it makes sense.
Updated several sovereign GEO's configs to reflect use of Global discovery for those GEOs
Fixed a bug in LinQ create methods that would appear on non-windows deployments.
   This would manifest as a missing method exception when trying to create a sequential guid.

0.0.1.9-Alpha:
Fixes a bug in using ExecuteCdsWebRequest that blocked connections using clientSecretAuth types.

0.0.1.8-Alpha:
Removed IOverrideAuthHookWrapper and property and replaced with a new constructor form.
   This capability was replaced with a new constructor that accepts a function pointer as a parameter to the constructor.
   This user provided function takes the form of string FunctionName (string InstanceUri),  When called, the current instance URI will be
   passed in and the function is expected to return an access token for access to that instance.
   This form allows an given instance of the CdsServiceClient to be associated with a Auth Processor vs having the auth processor at the process level.

Fixed a bug reported in .clone in .net core builds.  When cloning a connection in .net core, the system would think you were using an invalid auth type.

Known issues:
   None at this time.. Please report any issues on the GitHub Issues site.


0.0.1.7-Alpha
   Fixed a Nuget Package dependency issue in Microsoft.Dynamics.Sdk.Messages

0.0.1.6-Alpha
Intial Alpha release of Microsoft.Cds.Client.CdsServiceClient
   WARNING: This is an ALPHA release.
   This library is a rename and renamespace of the Microsoft.Xrm.Tooling.Connector.CrmSeriviceClient.
   If you are familiar with the CrmServiceClient,  By Renaming each occurrence of Crm to Cds, you should find that API's match up.
   Major changes from CrmServiceClient:
       This library does not support User Interactive or User Password Auth flows in .net core.
       This library does not support AD or ADFS login to OnPremise,
           to use against an onPrem instance of CDS, your instance must be configured with
           ADFS + OAuth and the application ID you wish to use registered.
       This library removes several Dynamics specific helper methods from CrmServiceClient.
           this additional methods can be found by include the nuget package Microsoft.Cds.Client.Dynamics