You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When migrating data from 1 environment to another and checking the box to map the Statuscode field, all records in the target environment become Active (Statecode=0/Statuscode=1) regardless of status settings in the Source environment.
Wondering if this is related to the fact that it looks like MS recently moved the actual state change function to an async function after setting the new state/status codes. In the tool, it appears only Statuscode is mapped but not the Statecode. Since the actual state change is asynchronous, no error is detected by the tool? Just guessing though.
The text was updated successfully, but these errors were encountered:
When migrating data from 1 environment to another and checking the box to map the Statuscode field, all records in the target environment become Active (Statecode=0/Statuscode=1) regardless of status settings in the Source environment.
Wondering if this is related to the fact that it looks like MS recently moved the actual state change function to an async function after setting the new state/status codes. In the tool, it appears only Statuscode is mapped but not the Statecode. Since the actual state change is asynchronous, no error is detected by the tool? Just guessing though.
The text was updated successfully, but these errors were encountered: