Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit7d4e8c0

Browse files
committed
readme update
1 parent27d5615 commit7d4e8c0

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

‎README.md‎

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,6 @@
22
![Windows](https://img.shields.io/static/v1?label=OS&message=Windows&color=green)
33
![Version](https://img.shields.io/static/v1?label=Version&message=3.10.0&color=white)
44

5-
65
#Flow & Power Apps Migrator
76

87
Have you ever tried moving canvas apps or cloud flows across Microsoft 365 tenants or sites? This is a common task when deploying apps and flows to production. Apps and flows must be exported, and imported, and SharePoint actions must be manually updated. These manual updates are error-prone and labor-intensive.**Flow & Power Apps Migrator** automatically converts exported flows and apps to be compatible with the target environment.
@@ -257,6 +256,11 @@ SharePoint List forms customized with Power Apps can be migrated if you follow t
257256
- Migrated lists with custom content types end up with an extra content type that should be deleted manually after migration.
258257
- Migrated lists might need fields added to the content type or a form. In some cases, migrated lists show only the Title in the edit form.
259258

259+
###3.10.1 Version - 2025-06-08
260+
261+
####Changes
262+
- Added more error handling to the migrator. If the migrator fails, it will now display a more descriptive error message.
263+
260264
###3.8.6 Version - 2023-05-10
261265

262266
####Changes

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp