Skip to content

Releases: dotnetprog/dataverse-configuration-migration-tool

Release v1.1.1

07 Aug 11:50
e4430db
Compare
Choose a tag to compare

🆕 What's New ?

✔️ Fixed some issues when import data that referenced those tables:

  • TransactionCurrency
  • UoM (Unit)
  • UoMSchedule (Unit Group)

the tool tries to resolves the references with their Id, if not found, it tries again with the name otherwise it ignores the field when pushing to dataverse.

Release v1.1.0

03 Aug 14:27
c49de59
Compare
Choose a tag to compare

🆕 What's New ?

✔️ Export configuration data from Dataverse is now available using the verb: export-data
✔️ Owner,Team And Business Unit field is now supported. If by Unique Id is not found in target env, it matches by name otherwise it ignores the field. Caching is used to avoid unnecessary calls to dataverse.

export-data command verb:

This new command exports the data the same way as the Microsoft Configuration Migration Tool does.

This command has been added to enable this tool for upcoming updates to support more data types (ex: MultiSelectOptionSet) for export and import.
Microsoft Configuration Migration Tool does not seem to evolve as fast as the platform does.

Release v1.0.0

22 Jul 22:06
64a1d97
Compare
Choose a tag to compare
Merge pull request #12 from dotnetprog/feature/CreateReleaseOntagWork…