Unanswered

CDS Configuration Migration Tool - Date Import Error

(0) Share

Report

Posted on by Chris Miles

When using the CDS Migration Tool, we have an issue where dates set in the export system are not migrating to the import solution correctly. Both systems are set to AEST but on import the tool seems to reset them to UTC time. Is this a bug or is there a way to stop this behaviour?

Categories:

Administer & monitor

I have the same question (0)

All responses (3)

Answers (0)

Sort by

oliver.rodrigues 9,475 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi, is this how the Portal is showing the date on pages? or how records are being created in the system?

can you share snapshots?

Was this reply helpful? Yes No
Chris Miles 4 on at

Like (0)

Report
Copy link

Link copied!

I believe this is how dates are stored in the Dataverse (User Local), which is the correct format, but it seems when it imports the data, instead of retaining the converted UTC date for the fields in the source dataverse, it assumes the importing date is a user local data again and reconverts it to UTC from my timezone (AEST). Is there a way to retain the original timezone conversion data on import? (i.e. assume the data is already in UTC). This behaviour seems to happen with any import tool (DataFactory, Dataflows, Migration Tool, etc).

Was this reply helpful? Yes No
Parvez Ghumra 1,579 Moderator on at

Like (0)

Report
Copy link

Link copied!

@chrisvistec I've had similar issues with DateTime fields with the Configuration Migration Tool in the past (outside of Power Pages/Portals).

If this is for the movement of portal configuration movement between environments, here are some alternatives you may wish to consider:

You can use the PAC CLI to migration portal configuration between environment using the pac paportal or pac powerpages groups of commands - specifically use pac paportal download or pac powerpages download to export from your source environment and pac paportal upload or pac powerpages upload to import to your target environment: https://learn.microsoft.com/en-us/power-platform/developer/cli/reference/powerpages

There are also Azure DevOps pipeline tasks available from Power Platform Build Tools which do the equivalent if you don't wish to use to use the PAC CLI directly: https://learn.microsoft.com/en-us/power-platform/alm/devops-build-tool-tasks#power-pages-management-tasks

And corresponding Github Actions for Power Platform: https://learn.microsoft.com/en-us/power-platform/alm/devops-github-available-actions#portal-tasks

Was this reply helpful? Yes No