Error parsing EntityName on app screen / PS error in log Current site is not a tenant administration site about flowpowerappsmigrator HOT 11 OPEN

hi @BordyCCQ,

It must be a new bug in the latest version of my script. I am attempting to remove a couple of site columns from the Lists.xml. And as a result, it might make this XML file invalid. would it be OK if I ask you to share this Lists.xml file with me?

from flowpowerappsmigrator.

hi @Zerg00s,
Here's the file:

Lists - Copy.log

from flowpowerappsmigrator.

Thank you for sharing the XML file!

I am not yet sure how to fix this, but it seems that the issue is related to the & character in the taxonomy term for the UA0226 field:

It might be a little tricky to fix safely, but I need to experiment with escaping the & character in the XML.

Another workaround would be to somehow remove the & character from the source data source and then re-run the migrator.

from flowpowerappsmigrator.

@BordyCCQ , can you help me test a fix, please?

• Open the Move-Lists.Ps1 file
• On the line 109, replace the existing code with the following:

  ((Get-Content -Path Lists.xml -Raw -Encoding UTF8) -replace '<\?xml version="1.0"\?>', '' -replace 'RootSite', 'Web' -replace '(?<=\{[^}]*)\&(?=[^}]*\})', '&amp;') | Set-Content -Path Lists.xml -Encoding UTF8

• Run the migrator again

If this runs successfully, I will release a new version with a patch.

from flowpowerappsmigrator.

@Zerg00s: Same error
I'll remove the & and retry with original .ps1

from flowpowerappsmigrator.

Now working OK!
I can rerun with the & if you want to test a new line 109

from flowpowerappsmigrator.

Yes, please! Re-run with the & character in place :)

from flowpowerappsmigrator.

... with same line 109 .ps1??

from flowpowerappsmigrator.

yes, with the updated line 109 :)

from flowpowerappsmigrator.

I did try the new line 109 with the & in the term set name and It crashed again same place.

I then put back the old line 109 and removed the & in the term set and the App worked OK!

UNTIL...

Still running on a 'fresh' new target SPO site (previous one had copy of list with content type existing - App stopped at CT already error exist).

---- And now stopped: Parent CT ID does not exist

I can see in the trace.log that the CT mentionned is an artefact of SP2010, migrated to SPO... Need to clean up the source SPO site before trying again.

I can test a new line 109 next week, with the & term set.
Thx again - tool seems very good!

from flowpowerappsmigrator.

I see. Thank you for trying it. I will need to find time to experiment with moving the taxonomy fields. I am not sure it works very well.

from flowpowerappsmigrator.