Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Error] Invalid field name. #69

Open
ChristerRussbergVGRIT opened this issue Sep 17, 2023 · 3 comments
Open

[Error] Invalid field name. #69

ChristerRussbergVGRIT opened this issue Sep 17, 2023 · 3 comments

Comments

@ChristerRussbergVGRIT
Copy link

Hi
I am testing your solution when trying to migrate a list with Power Apps customized form.
I want to move it from tenant A to tenant B.
I have manually created the list in both tenants.
It is a simple list with 4 columns "Title", "Description" (multifield), "Status" (choice field) and "Manager" (person field).

But I get the error message as seen below.
[Error] Invalid field name. {2b67bcd7-14d4-4c13-85dd-605eb8109b5e} https://xxx.shareoint.com/sites/TESTplanering

@Zerg00s
Copy link
Owner

Zerg00s commented Sep 22, 2023

hi @ChristerRussbergVGRIT,

Sorry for the delay. Can you remove the list in the target tenant B? It's best to let the Migrator do the list migration. Doing it manually causes some issues.

If you still get an issue, please share a screenshot with the full error message.

@ChristerRussbergVGRIT
Copy link
Author

Hi, thansks for the tip. It worked to move from tenant A to tenant B the first time.
But when I try the second time (to mimic an update) I can't get it to work.
I get the error as seen below and I have check that both tenant A and tenant B uses English.

What is your best tip of getting an update of the form in tenat A to tenant B?

Make sure that both target site and the source sites created with the same language. Cross-language list migration is not supported.

image

@Zerg00s
Copy link
Owner

Zerg00s commented Sep 24, 2023

Hi @ChristerRussbergVGRIT,

This is a common issue, but the best workaround so far is to run the Migrator using SharePoint-only apps

If you are a SharePoint Tenant admin in both tenants, you might want to try this approach.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants