Xrm. Tooling. ConfigurationMigration
PowerShell Module for Microsoft Dynamics CRM Configuration Migration Utility
Microsoft Common Data Service Team
Â© 2020 Microsoft Corporation. All rights reserved
This module has no dependencies.
Corrected an issue that would cause CMT to hang when executing prefetch. this situation was caused by very large record counts in entities that were being prefetched.
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 searchs would not be impacted.
Fixed an issue with Batch mode import that is caused by invalid guids being hand edited into datafiles.
Fixed an issue where CMT would prefer ID/Name over comparison keys when precaching data for comparison.
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.
Up-taking fixes for Sovereign cloud discovery connectivity for login controls
Fixed an issue where data import could hang without error
Added new optional parameter called PrefetchRecordLimitCount ( defaults to 4000 ) this controls the number of records that are prefetched when doing pre-validation during import.
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 IDs 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.
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
Fix for Entity model changes in CDS to support filtering out non importable fields introduced by new entity types.
Fix for a fail to import bug that can occur if an incoming data file has either a state or status code but not both
Fix for a non-failing data error that can occur when creating pre-parse data for import.
Fix for activating Duplicate Detection rules properly post when present.
Speculative fix for Concurrency issue with Batch and Threaded Mode import.
Modified threaded import to improve performance and throughput.
Fixed a bug where status of a record would not be updated for records in an active state.
Fixed a bug in batch mode when the client is provided only 1 connection to work with.
Optimized updates for state/status events to prevent unnecessary updates to Cds. (only affects version 9.0 +)
Reduced chattiness of logs, logs will now only emit once for the same type per thread.
Fixed an issue preventing logs from being generated correctly, Logs should once again write to the log directory
Added new cmdlet switch called EmitLogToConsole. When set, the log will be written to the console of the powershell session in addition to logs. Intended to used in conjunction with the -verbose parameter
Increased default timeout for Export-CrmData cmdlet.
Added 2 new parameters to Import-CrmData
EnabledBatchMode – instructs CMT to import into CDS using batches ( default size of 600 records ). Note this does work in conjunction with multiple connections, thus 2 connections creates 2 batches of 600 records.
BatchSize - Allows you to override the default batch size ( 600 records ).
Fixed a bug with pre-processing in CMT that would cause the system to runout of memory when importing to entities that had large numbers of records.
Inital release for Configuration Migration Tool Powershell.
|126.96.36.199 (current version)||11,129||8/3/2020|