FlowPowerAppsMigrator icon indicating copy to clipboard operation
FlowPowerAppsMigrator copied to clipboard

Migrated Power Apps List Forms

Open Zerg00s opened this issue 2 years ago • 7 comments

Short explanation

  • Around February/March, 2022, Migrated Power App forms stopped working. After a migrated App is imported to the new tenant, it does not appear in a SharePoint List form.

From my research, I've noticed that an imported Power App does not trigger several SharePoint-specific artifacts to be created.

Zerg00s avatar May 19 '22 02:05 Zerg00s

Is this still in development? Just curious. I was researching ways to handle this scenario.

robertcaretta avatar Jun 24 '22 19:06 robertcaretta

hi @robertcaretta,

I am still looking into this issue. but it's a problem I can't figure out yet. It used to work fine until around February. And I don't yet know what to do about it. I still hope I can find a way.

Of course, if someone can help with it - I will gladly accept this help 🙂

Zerg00s avatar Jun 24 '22 19:06 Zerg00s

hi @Zerg00s,

For me PowerApps List Forms migration works just fine, but only if I create lists directly in the destination Site Collection. If I use the "Migrate Lists" feature from your script then I get an error message during the import saying

"The sharePoint request failed with error: '{"odata.error":{"code":"-1, Microsoft.SharePoint.SPConnectorException","message":{"lang":"en-US","value":"An App already exists for this list. Remove the existing App before adding a new one."}}}'. "

Up to my research it really seems that migrating a list with your code somehow also copies the information about the assigned form. As when I go to Form Settings menu of the migrated list and click "Customize in PowerApps" it takes me to the already existing app of the source list (instead of creating a new app for the migrated list).

kvadratnymedved avatar Aug 12 '22 09:08 kvadratnymedved

Hi @kvadratnymedved,

seems that migrating a list with your code somehow also copies the information about the assigned form

Wow. Thank you very much. This is a very valuable observation! I just tested it and I confirm the same result.

Let me also do some experiments today. I want to have a look what the "Migrate Lists" feature does to break the form.

Now I have a very good chance to finally make the Form migration work again.

Zerg00s avatar Aug 12 '22 13:08 Zerg00s

I was able to get the Sharepoint Lists that had customized PowerApps Forms migrated using Migrate Lists and export & import of the apps.

Prior to entering credentials for the target environment, I modified Lists.xml and removed 3 lines for PropertyBagEntries for each list that had a PowerApps Form associated with it. Once this was done, I continued with the script to import the lists into the target environment and convert the apps in src. All finished with no issues and when importing the apps as Canvas Apps it also did so with no issues. At which point I just opened the form by clicking Open App, saving & publishing it.

Seems like the Move-Lists.ps1 script is adding PropertyBagEntries in which powerapps information exists which is causing this error. I tried using "-ExcludeHandlers PropertyBagEntries" in get-pnpprovisiongtemplate, but that caused other issues.

amariak avatar Sep 01 '22 15:09 amariak

@amariak,

Thank you very much! You probably saved me many hours of work with this tip. Let me fix it. I might be able to publish an update tonight.

Zerg00s avatar Sep 02 '22 01:09 Zerg00s

@amariak , thank you for your help. I have published a new release with credits to you and updated the readme file to include the instructions on how to migrate SharePoint List forms customized with Power Apps

Zerg00s avatar Sep 02 '22 03:09 Zerg00s