Skip to main content
SharePoint

Return to Question

Update about msapp file
Source Link
Danny
Danny
  • 548
  • 1
  • 5
  • 21

We have several SharePoint Online List form Power Apps. We export and import them to different site collections in our tenant [DEV/TEST/ACCEPTANCE/PROD]. This requires to change the datasources.json file that is in the zip file when you export the app. We use a script to achieve this. This script unzips the export, unzips the .msapp file. changes the datasources.json file in the .msapp file and makes a new zip.msapp file with zip. We rezip the entire app which we import in Power Platform. This was working fine.

We now moved to PowerShell 7 on our dev machines. Since this change the zip file can be imported but the app doesn't work after import. We get a file not found error when editing the app. When we revert back to PowerShell 5 the app can be imported and works fine.

We make use of the default Compress-Archive cmdlet to zip the file. When inspecting the zip files we see that there is a difference. When we user Compress-Archive in PowerShell 5 file paths are combined using a "". In PowerShell 7 file paths are combined using a "/".

Why can't we import a zip file that is using "/" as a seperator? I think both should work.

We have several SharePoint Online List form Power Apps. We export and import them to different site collections in our tenant [DEV/TEST/ACCEPTANCE/PROD]. This requires to change the datasources.json file that is in the zip file when you export the app. We use a script to achieve this. This script unzips the export, changes the datasources.json file in the .msapp file and makes a new zip file which we import in Power Platform. This was working fine.

We now moved to PowerShell 7 on our dev machines. Since this change the zip file can be imported but the app doesn't work after import. When we revert back to PowerShell 5 the app can be imported and works fine.

We make use of the default Compress-Archive cmdlet to zip the file. When inspecting the zip files we see that there is a difference. When we user Compress-Archive in PowerShell 5 file paths are combined using a "". In PowerShell 7 file paths are combined using a "/".

Why can't we import a zip file that is using "/" as a seperator? I think both should work.

We have several SharePoint Online List form Power Apps. We export and import them to different site collections in our tenant [DEV/TEST/ACCEPTANCE/PROD]. This requires to change the datasources.json file that is in the zip file when you export the app. We use a script to achieve this. This script unzips the export, unzips the .msapp file. changes the datasources.json file in the .msapp file and makes a new .msapp file with zip. We rezip the entire app which we import in Power Platform. This was working fine.

We now moved to PowerShell 7 on our dev machines. Since this change the zip file can be imported but the app doesn't work after import. We get a file not found error when editing the app. When we revert back to PowerShell 5 the app can be imported and works fine.

We make use of the default Compress-Archive cmdlet to zip the file. When inspecting the zip files we see that there is a difference. When we user Compress-Archive in PowerShell 5 file paths are combined using a "". In PowerShell 7 file paths are combined using a "/".

Why can't we import a zip file that is using "/" as a seperator? I think both should work.

Source Link
Danny
Danny
  • 548
  • 1
  • 5
  • 21

SharePoint Online List Form PowerApp zip file difference between PS5 and PS7

We have several SharePoint Online List form Power Apps. We export and import them to different site collections in our tenant [DEV/TEST/ACCEPTANCE/PROD]. This requires to change the datasources.json file that is in the zip file when you export the app. We use a script to achieve this. This script unzips the export, changes the datasources.json file in the .msapp file and makes a new zip file which we import in Power Platform. This was working fine.

We now moved to PowerShell 7 on our dev machines. Since this change the zip file can be imported but the app doesn't work after import. When we revert back to PowerShell 5 the app can be imported and works fine.

We make use of the default Compress-Archive cmdlet to zip the file. When inspecting the zip files we see that there is a difference. When we user Compress-Archive in PowerShell 5 file paths are combined using a "". In PowerShell 7 file paths are combined using a "/".

Why can't we import a zip file that is using "/" as a seperator? I think both should work.