Change Time Zone Independent back to User Local because of error in Deployment

(0) Share

Report

Posted on by Shah-Zaib

Hi can anybody help me why I cannot edit a column, specifically change from Time Zone Independent to User Local. I have a calculated field and when i deployed this solution. it gives me error

Categories:

Microsoft Dataverse with Power Apps

image.png

I have the same question (0)

All responses (4)

Answers (0)

a33ik 3,306 Most Valuable Professional on at

Like (0)

Report

Hello,

The reason is mentioned in the error. Here is what you can do but it will be a multi step tweaks:

1. Rollback timezone field behavior to the original.

2. Update the calculated field formula so as not to rely on the datetime field you mentioned. Export from DEV/Import into Upstream.

3. Update the behavior of datetime field. Export from DEV/Import into Upstream.

4. Revert your calculated field formula to rely on the datetime field. Export from DEV/Import into Upstream.

Was this reply helpful? Yes No
Shah-Zaib 2 on at

Like (0)

Report

How can i rollback field , because it is disabled and can't revert when we select timezone independent

Was this reply helpful? Yes No
a33ik 3,306 Most Valuable Professional on at

Like (0)

Report

I see. I didn't know it was a one-way path. So, here is what you can do:

1. Update the calculated field formula so as not to rely on the datetime field you mentioned. Export from DEV/Import into Upstream.

2. Delete datetime field. Export from DEV/Import into Upstream.

3. Create a new datetime field with the proper behavior and update the calculated field formula to rely on the newly introduced field. Export from DEV/Import into Upstream.

Was this reply helpful? Yes No
js3 15 on at

Like (0)

Report

Hi,
Just putting this here for others who encounter this issue - it is most likely much too late for the original poster.

There are a few ways to change the field back to User Local.
1. If this change was part of a managed solution, this will be fixed by removing the solution layer from the field. [EDIT: This won't work in Power Apps - you have to use Classic Mode to remove the solution layer from the field]
2. Otherwise, the field can be fixed by restoring the entire environment to a backup from before the field was changed. You can do this in Admin Centre, where it seems like there are automatically backups taken every half hour or so.

Was this reply helpful? Yes No