Microsoft.CrmSdk.XrmTooling.PackageDeployment.Core 9.1.0.184

• .NETFramework 4.6.2

  • Azure.Identity (>= 1.11.0)
  • Azure.Security.KeyVault.Secrets (>= 4.5.0)
  • Microsoft.CrmSdk.XrmTooling.CoreAssembly (>= 9.1.1.49)
  • Microsoft.Extensions.Caching.Memory (>= 3.1.8)
  • Microsoft.Identity.Client (>= 4.61.1)
  • Microsoft.IdentityModel.Clients.ActiveDirectory (>= 3.19.8)
  • Microsoft.PowerPlatform.PackageGeneratorLib (>= 1.0.22)
  • Microsoft.Rest.ClientRuntime (>= 2.3.24)
  • Newtonsoft.Json (>= 13.0.1)

This package contains assemblies for Dynamics 365 (online and on-premises). These assemblies require application development using the Microsoft .NET Framework 4.6.2 or later.

9.1.0.184:
Possible BREAKING CHANGE:
- Removed all UII dependencies and libraries.
- Removed UII centric interface method in Base Package Contract - this will break your package code if your using this in a package.
  - if you are impacted by this, please remove the use of the "PerApplicationImport" interface override from your package code.
Updated dependency Microsoft.Identity.Client to 4.61.1

9.1.0.171:
Added support for deleting Failed upgrades by adding removefailedupgrades="true" as an attrubte of configdatastorage node in importconfig.xml
 - Also can be passed as a setting to package by passing PD.ForceDeleteUpgradeSolutions=true.
Added support for wildcard settings value solutiontemplatesuffix=*:<suffix> to support deploying all assets in the package as template.

9.1.0.167:
Added support in CMT to declare that a given table's records should only ever be created as new records.
 - SkipUpdate and ForceCreate are mutually exclusive operations. If they exist together, ForceCreate will be used.
Fix to force PD to load common files from the execution directory to prevent binding redirect issue.
Fix for CMT being asked to use the primary id of data to import when that ID is not included in the incoming data.

9.1.0.148:
Updated to current release of CrmSDK and CSC
Added support for deployment setting "PD.OverrideAsyncRibbonProcessingBehavior". if passed "skipall", all ribbon processing for this run will be skipped.
Added package property ServiceClient of type IOrganizationService
Updated behavior for importing solution in template mode. Templates will not call overridesolutionimport decision and import even when the same version.
Deprecated: Package property CrmSvc is now flagged as deprecated, this is being replaced with ServiceClient.

9.1.0.147:
Added support for to write deployment logs to package table in target dataverse instance.
Added new control flag to control log write behavior called "EnableLogWriteToOrganization".  This is both a property and app setting.

9.1.0.143:
Resynced to current SDK baseline

9.1.0.139:
Resynced to current SDK baseline
Updated dependency on Azure KeyVault client libraries

9.1.0.137
Added support for unified packaging of Finance and Operations Assets.
Added initial support for several new features of package deployer around unified packaging for the power platform and keyvault intergration.
     This support requires that you base64encode the settings file ( by solution ) and pass string as a property in the /Settings: of the Package Deployer client.
     The format to use is %solutionunqiuename%_deploymentsettings=%base64string%
     Multiple settings can be passed by using the Key=Value| format.

9.1.0.106
CMT: Corrected missing support for team membership type for AAD connected Teams.
Added support for Identity Management in Package Deployer.

9.1.0.87:
Updated logic to bug fix issues with Posting Package linking data.

9.1.0.86:
Uptaking new SDK and ServiceClient Libs
Updates for FnOps.
Uptaking fixes from CMT

9.1.0.85:
Added Support for New Import Async pattern for SolutionImport
Fixed a issue where an Error thown from Package code ( provided by customer ) caused an premature abort of Importing Solutions
Fixed a issue where solution stage event was not being raised on error of first solution.
Added support for solution template system.
CMT: Corrected an issue with the Teams entity that prevented the AAD Group Object ID imported.

9.1.0.76:
Corrected an issue in the Assembly Resolution logic to prevent possibility of incorrect type name parsing.
Added support for in-memory log capture for package deployer and CMT
Added Telemetry support files to Nuget package
Adding functionality to interact and install Finance and Operations apps.
Adding functionality to override and modify Finance and Operations configuration with runtime settings.
Separated out Finance and Operations code to separate module.
Above changes are isolated and should not impact CDS related installs.

9.1.0.46:
Corrected an issue with CMT lookup resolution that would prefer the display name over the ID of the target of the lookup.
Corrected an issue with CMT where a failure to import would occur if, during the decision process for update vs insert, an existing record was not found by ID and the Name field of the record was null
This would only impact default search patterns.  Entities that defined custom search's would not be impacted.


9.1.0.44:
Fixed an issue with Batch mode import that is caused by invalid guid's being hand edited into datafiles.
Fixed an issue where CMT would prefer ID/Name over comparison keys when pre-caching data for comparison.

9.1.0.43:
Fix in Data import to compensate for Import files created during a window of time where new virtual fields generated by CDS were incorrectly identified as valid fields.
This issue would cause schema validation to fail during import of complex data for some types of "attributeOf" type fields.

9.1.0.40:
Fixed a bug in runtime settings parsing that would mis identify a = in the value as a key value separator.

9.1.0.39:
Fixed an issue where data import could hang without error

9.1.0.37:
Fix for an issue where importing business units that included a lookup for their own team (looped back to the entity) would not be populated on update.
Fixed a general issue were related LookUp ID's that were discovered in the target system were not properly linked.
Behavior Change: when using BatchMode, Create will always include the ID of the record from the source system, even if not explicitly included as a field in the exported system.

9.1.0.36:
Fix for an issue reported where related objects were not being correctly identified by name and thus not correctly linked to importing records
This only impacted imports where the related entity did not have comparison keys

9.0.1.33:
Altering the default client engine to move coreobjects to a non static type,
Staging for merger of MTPD code with mainline PD.
Added in memory configuration parsing logic
Optimized dependency checking logic

9.1.0.27:
Cleaned up extra lines in logging output.
Adding Logging for time taken during configuraiton parsing to aid in performance info.
Uptook New CDS SDK drop.

9.1.0.24:
Fixed an issue preventing logs from being generated correctly,  Logs should once again write to the log directory

9.1.0.21:
Many Logging improvements
Fixed an issue with Async Solution Import.
Includes fixes from DMT: Fixed bug with preprocessing that would cause an apparent runaway, removed check for display name on attributes, updated batch mode system.

9.1.0.20:
Introduced binding redirect for Microsoft.IdentityModel.Clients.ActiveDirectory dll.
Package developers can define error type as application error or publisher error - internal only.

9.0.2.30:
Enhanced PD logs and temporary file delete logic.

9.0.2.29:
Enhanced PD logs and raise fail event immediately when AfterPackageImport returns fail.

9.0.2.26:
Enhanced PD to pass more error details to invoker of PD lib

9.0.2.24:
Published PackageDeployerException class which can be used by package developers
Enhanced PD to bubble up error details to invoker of PD lib with progress status in case of failure - internal only

9.0.2.23:
Internal updates - No Public changes

9.0.2.22:
Internal updates - No Public changes

9.0.2.21:
Logging updates for async import error scenario.

9.0.2.20:
Logging Updates
Added support for default async mode for DeleteAndPromote, regardless of how a given package is configured.
Reverted change for RaiseFail event which done in version 9.0.2.19.  Now it will not cause PD to stop with an overall failure and stick to old behavior of continuing package installation.

9.0.2.19:
Logging Updates
Added support for forcing all packages to run Sync mode, regardless of how a given package is configured.
Modified RaiseFail event for RaiseFail generated from the package.  New behavior will cause PD to stop with an overall failure.

9.0.2.16:
Added native support for handing throttling messages from server.
Improved handling of retry logic for blocked imports due to concurrent metadata import

9.0.2.14:
Corrected an error that occurs when a Async Upgrade Fails due to a recoverable server issue.  PD will attempt to recovery correctly vs aborting and requiring a restart.

9.0.2.12:
Correcting Dependency Info on Package
Fixed bug in CrmServiceClient which would cause some OnPrem connections to fail with an error "Item already added to List"
Minor Pref Improvements

9.0.2.11:
Updated to include Fixed version of CrmServiceClient and login control for new US Geo ( US Gov High )
Added support for Preferring Affinity with a given node to improve cache hit success rate.

9.0.2.9:
Note .net 4.6.2 is now required as a baseline
Fixed a user reported issue that would cause an import patch to fail due to being misapplied.
Fixed a user reported issue that would cause the incorrect version of a solution to be imported under some circumstances during update.
Added better error detection for failed Async Jobs when using Async Solution Import.
Major updates to error logging to make logs more concise and useful.

9.0.2.8:
Corrected an issue which would occur while importing a package that contained an upgrade for a deployed solution, where a prior version upgrade had failed leaving a holding solution. The system will now attempt to apply the current holding solution, and upon success, apply the new upgrade contained.

9.0.2.7:
Picked up updated CrmServiceClient (Microsoft.Xrm.Tooling.Connector)


9.0.2.5:
Corrected use of strong types inside Package Deployer to allow it to work properly with packages that also include overlapping strong typed objects.
Corrected a case where Async Solution Deployment could fail and not be correctly caught by PD.

9.0.2.4:
Updated install flows to more correctly trigger failures on failures within user code or data import.
Added support several configuration settings dealing with timeouts and dials.
These settings are set in the app.config of the host process
StaleImportProgressOverride -
This setting is the number of times a solution import be polled for progress.  This is rolling property, the count resets each time a solution moves forward.
Default setting is 50
Note: this property only applies when solutions import mode is sync.

SolutionStatusPollingFrequencyOverride -
This setting is the delay between check for solution progress.
The default setting is :  5 (seconds)
Note: this property only applies when solutions import mode is sync.

SolutionImportBlockedRetryCountOverride -
This setting is the number of retries that will be attempted when a solution import is blocked by a concurrent metadata operation.
The default setting for this is 10

SolutionImportBlockedWaitOverride -
This setting is the number of seconds that a retry will wait before attempting another solution import.
The default setting for this is 60 (seconds)

UseAsyncForSolutionImport -
This setting controls the default behavior of the import operations for Package Deployer.
If set to true, Package deployer will attempt to use an Async Pattern for all solution operations where possible to do, given the server configuration.
The default setting for this is false ( sync mode )

Importconfig.xml - Solutions node updates.
Added requiredimportmode as an option to force an Async or Sync import behavior for a given solution.
This includes, upgrade or new install.
Valid settings for this property are :
async -  Requires the Import of this solution to be done in an async manner if the server supports it.
sync - Requires the import of this solution to be done in a sync manner if the server supports it.
Default behavior follows the default setting for the Package Deployer Core Process.

9.0.2.3:
Updated with Xrm.Tooling.Connector support
Fixed issues that caused unhandled exceptions to be thrown when a package resulted in an error
Added new notifications in logs and UX for faults (where applicable).
Added logic to detect stuck solution import and abort the import process

9.0.0.9: Added missing Xrm.Tooling.Connector DLLs due to some packages requiring them.
9.0.0.8: Added missing CAB DLLs
9.0.0.7: Fixed a bug in CMT Lookup processing logic that was causing incorrect linking where the data set includes records that require related lookup records which share the same default name.
9.0.0.5: 9.0 Initial Release
9.0.0.2-preview:
Using Xrm.Tooling 3.x and CRM 9.x assemblies

Initial release of the 2.2.2 core PD module.