A duplicate field name "IsolatedDomain" was found. about flowpowerappsmigrator HOT 21 OPEN

Hi @Zerg00s , I did a test with version 3.8.1 using the two sites in English between different tenants, now the screen to choose the lists appeared, but at the time of import on the destination site I get an access denied msg. see the image.

It displays both source and destination authentication screens, I don't know what's going on.

@sauslash, I got the same Access Denied error last week, but on my end it was due to scripting being disabled on the newly created sitecollection. I don't know if this is also the case with you sitecollection where you got the error, but can you check if the sitecollection has scripting capabilities enabled?

I think you can change this in the UI but I added this line to the PowerShell script of @Zerg00s:
Set-PnPTenantSite -Url $TARGET_SITE_URL -DenyAddAndCustomizePages:$false

from flowpowerappsmigrator.

Also found this issue

from flowpowerappsmigrator.

Good and bad news. If I create a blank site and create a list, then creating an automatic app from that list and repeating the process should work right?
That's exactly what I did, I just created a list and created an automatic app. I exported between different tenants and it worked. 🤣. I will simulate soon with several lists with lookup columns and let you know. Thank you @Zerg00s

from flowpowerappsmigrator.

Hi @QJappie22 / @Zerg00s ,
I enabled the script on the target site, but the error happened. The problem seems to be when the source site has a app catalog(I use for SPFx), this generates a SiteFields node that multiple fields from the site that conflict on the destination site.
When it worked, both sites didn't have the app catalog created.
Thank you.

from flowpowerappsmigrator.

@sauslash
Thank you. I remember I tried deploying this schema. It's something to do with the site columns. But I didn't figure out exactly which fields are causing the problem.

from flowpowerappsmigrator.

I would like to congratulate you for this project that will surely help many people.
Another point I identified was, my language is Portuguese, the columns were created with strange characters because we have accents in our language.
Thank you.

from flowpowerappsmigrator.

language is Portugue

Hi @sauslash, thank you for describing the issue. Would you be able to try a new version, please? There was an issue with the encoding that I hopefully fixed now.

You might need to delete your list(s) from the target SharePoint site just in case it was corrupted by the wrong encoding.

from flowpowerappsmigrator.

Hi Zergs, I tried again with the new version 3.8, see my comments.
The new version did not create the fields and lists. I used another project that doesn't use content types. The window to choose the lists I would like to create on the target site did not appear as it did in version 3.7

from flowpowerappsmigrator.

Hi Zergs, another test using the cenario bellow.

I found that the IsolatedDomain error only happens when I export from a communication template site and try to import into a team template site.

I did a test from team site to team site on different tenants and the error does not occur.
Both sites are English language and I didn't use content types.

However, several messages that the lists do not exist on the target site,
because they were not actually created with new version 3.8.

from flowpowerappsmigrator.

Hi @sauslash,

Oops. I had a bug in the 3.8 version: Lists were not even migrated in that version. I had to upload a new release 3.8.1 with a fix. Can you try again, please?

I have just tried migrating a list from English Communication site to English Team site and I could not replicate any issues there.

If you see warnings that some lists are missing - it's completely normal. These are just information messages that explain that some lists in the source site are missing from the target site. It's up to you if you want to move these lists. If the missing lists are not needed by the apps and flows - then there is no point migrating them.

In terms IsolatedDomain - I am not sure what that might be... Maybe you could try re-creating a target site from scratch? Not sure if it's an option in your case. Or, perhaps, you can find this site or list column and delete it?

from flowpowerappsmigrator.

Hi @Zerg00s , I did a test with version 3.8.1 using the two sites in English between different tenants, now the screen to choose the lists appeared, but at the time of import on the destination site I get an access denied msg. see the image.

It displays both source and destination authentication screens, I don't know what's going on.

from flowpowerappsmigrator.

Hi @sauslash, can you try the migrator again with the CLEAR_CREDENTIALS_CACHE property set to True (screenshot)?

If that does not work, can you try picking a different destination site as a test? It's a common problem with the PnP PowerShell module and I still can't figure out what's causing this error.

from flowpowerappsmigrator.

Hi @Zerg00s , when i try on the same tenant i get the IsolatedDomain msg(this field dont appear at my columns site), when i try between different tenants using clear_credentials i still get the access denied msg.
Sorry :(

from flowpowerappsmigrator.

1. In terms of Access denied, I'm sure you checked, but is it possible you don't have enough permissions on the target site? Are you a site collection administrator?
2. In terms of the IsolatedDomain field - I found this advice:

I was able to confirm that running the Apply command multiple times would throw this error since the custom columns are already created and it's not overwriting them. 
Is there any way to force overwrite the column creation process?

I simply deleted the custom columns and re-ran the Apply command and it went through. 
its strange though that after I did that cleanup now every time I run the command it updates the columns and it doesn't crash anymore...

from flowpowerappsmigrator.

Can you share your Lists.xml generated in the root folder? I will try to run it against my tenants as a test.

from flowpowerappsmigrator.

Can you share your Lists.xml generated in the root folder? I will try to run it against my tenants as a test.
Yes, my file.
Lists.xml

from flowpowerappsmigrator.

Thank you for the template. I'm getting the same issue when I run the Apply-PnPProvisioningTemplate -Path Lists.xml command:

It's likely something to do with this template. For example:

IsolatedDomain is a hidden site field

<Field Name="IsolatedDomain" ID="{68021728-C04C-45BB-B51F-7BCB5AB997B1}" Type="Text" DisplayName="Domínio Isolado" Group="_Hidden" Hidden="FALSE" Sealed="TRUE" ReadOnly="TRUE" ShowInEditForm="FALSE" ShowInDisplayForm="FALSE" ShowInNewForm="FALSE" />

It is indeed mentioned twice in the same template:

<Field Name="IsolatedDomain" ID="{93C24D72-351F-4711-83F1-023783753740}" Type="Text" DisplayName="Domínio Isolado" Group="_Hidden" Sealed="TRUE" ReadOnly="TRUE" ShowInEditForm="FALSE" ShowInDisplayForm="FALSE" ShowInNewForm="FALSE" />

I have just removed both of these fields, but the issue Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) is still present.

When I removed the entire <pnp:SiteFields> node, then Apply-PnPProvisioningTemplate -Path Lists.xml ran successfully.

So the issue is probably related to the site columns.

I would need more time to figure it out, but maybe that's all I found so far.

from flowpowerappsmigrator.

hi @sauslash ,

I tried replicating the issue, but no matter whether I have app catalog on the source or destination site I get no error. do you have a sample Lists.xml that causes this error?

from flowpowerappsmigrator.

hi @sauslash ,

I tried replicating the issue, but no matter whether I have app catalog on the source or destination site I get no error. do you have a sample Lists.xml that causes this error?

Hi Zerg, is the same Lists.xml that I shared here #27 (comment)

from flowpowerappsmigrator.

@Zerg00s , I generated a new xml with version 8.3, I hope it helps.
https://github.com/sauslash/PowerPlatform/blob/main/Lists-v8.3.xml

from flowpowerappsmigrator.

hi @sauslash, I was able to replicate this issue on my end yesterday. Interestingly, the issue occurs

• Even when both source and target sites are in English
• Both source and target site have the same Modern Team site templates

I am thinking this is somehow related to the fact that I created some content types which have related site columns. I will try to find time in the next few weeks to troubleshoot it. It's a very busy period right now, unfortunately, but the good news is that I have a Guinea pig site for testing.

from flowpowerappsmigrator.