Initial Sync error after copy environment

(1) Share

Report

Posted on by IbrahimBukhari

Hi Everyone,

I am facing Initial Sync error between F&O and dataverse after copying environment using copy over Everything, there error related to main team ID which still mapping to the teams id for the original enviroment "Couldn't resolve the guid for the field: teamid.businessUnit. The lookup value was not found: "New Enviroment name".

Any advise of someone faced the same issue before or how i can change the default team assigned to the parent business unit.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (4)

All responses (4)

Answers (0)

Sort by

MichaelFP 2,008 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!

Check the root business unit in the new Dataverse environment it looks that during the copy the process keep it the ID when the environment was created. If is different you will need to made a transformation to translate from the old ID to the new one.

If my answer helped you, please give me a Kudo (👍). If solve your question please mark as solution. This is help the community.

Was this reply helpful? Yes No
IbrahimBukhari 4 on at

Like
a
(1)

Report
Copy link

Link copied!

Thanks @Michaelfp , yes i was able to identify the root cause but couldn't fix , can you please advise how to do the transformation ?

Was this reply helpful? Yes No
Suggested answer

CU26071910-0 2 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi Ibrahim,

You can't change the name of the default team but you can change the name of the parent business unit.

When you do that the default team name will automatically change it's name to the parent business unit.

I had the same issue copying my DEV Environment to the UAT Environment

Was this reply helpful? Yes No
Suggested answer

MGR 4 on at

Like
a
(1)

Report
Copy link

Link copied!

We had a very similar issue.

Couldn't resolve the guid for the field: teamid.businessUnit. The lookup value was not found: ...

The only difference of what the odata query suggested and what I've found in our CE was that the query was looking for uppercase and in CE the name of the root Business Unit was lowercase.

So I've updated the name of the root BU to uppercase and that fixed the issue with the initial sync error.

Was this reply helpful? Yes No