#Power Platform Related Codes

#PP-AppLeaseConflict

Issue:

The app failed in the migration with the following error: 

Details:

The destination app is edited by a user and cannot be migrated.

Recommendations:

Log in to Power Apps with the destination service account to save and exit the app. Then rerun the migration job.

#PP-AppListNotFound

Issue:

The object failed in the migration with the following error:

Details:

The destination does not have a list with the same title as the associated source list of the app.

Recommendations:

Manually create a list in the destination with the same title as the source list and rerun the migration job.

#PP-AppNotFound

#Issue:

The app failed in the migration with the following error: 

Details:

The source app does not exist in the source environment.

Recommendations:

Make sure the app exists in the source environment, and rerun the migration job.

#PP-AppProfileLackPermission

Issue:

The parameter failed in the migration with the following error: 

Details:

The app profile does not have sufficient permissions to process the trigger parameters.

Recommendations:

Refer to to grant the app profiles with required permissions, and rerun the migration job.

#PP-AppRelatedFlowNotFound

Issue:

The app failed in the migration with the following error: 

Details:

The app's related flow has been deleted.

Recommendations:

Please remove the related flow from the app to ensure that the app can be exported successfully, and then rerun the migration job.

#PP-AppSiteCollectionNotFound

Issue:

The object failed in the migration with the following error:

Details:

The destination does not have a site with the relative URL as the associated source site of the app.

Recommendations:

Here are two options to resolve this issue:

Then, rerun the migration job.

#PP-ChannelFailedDueToTeamFailed

Issue:

The parameter failed in the migration with the following error: 

Details:

The source Channel parameter value cannot be mapped to a destination channel since the mapping from the source Team parameter to a destination Team failed.

Recommendations:

Refer to the error details about the Team in the same Migration errors section. Try resolving the error of the Team and rerun the migration job.

#PP-DestinationParameterForbidden

Issue:

The parameter failed in the migration with the following error:

Details:

The destination app profile does not have sufficient permissions to retrieve destination parameters.

Recommendations:

Make sure the destination app profile has sufficient permissions to retrieve destination parameters, and rerun the migration job. If this issue persists, you can contact AvePoint Technical Support for assistance.

#PP-DestinationPermissionMoreThanSource

Issue:

The user/group is skipped in the migration with the following information: 

Details:

The destination user or group has a greater permission level than the source user or group.

#PP-DestinationUserOrGroupNotFound

Issue:

The user/group failed in the migration with the following error: 

Details:

No mapped user/group can be found in the destination based on the configured user mapping or enabled mapping properties in the migration policy.

Recommendations:

Configure a new user/group mapping/Update the existing user/group mapping to map the source user/group to an existing user/group in the destination, and run an incremental migration job.

#PP-DueToParentFailed

Issue:

The object failed in the migration with the following error: 

Details:

The parent of this object failed in the migration.

Recommendations:

Refer to the error details about the parent in the same Migration errors section. Try resolving the error of the parent and rerun the migration job.

#PP-DuplicatedFlowNameUnderPowerApps

Issue:

The app failed in the migration with the following error: 

Details:

The Power App has multiple flows with the same display name.

Recommendations:

Edit the app in the source environment and rename the flows to have unique names. Save your changes and republish the app. Then rerun the migration job.

#PP-ExportPackageError

Issue:

The object failed in the migration with the following error: 

Details:

An error occurred while exporting the package.

Recommendations:

Check in Power Automate/Power Apps, and ensure that the Power Platform connection used by the source app/flow is correct. Log in to the Power Platform with the service account and manually export a package to see if that is successful. Then rerun the migration job.

#PP-FlowNotFound

Issue:

The flow failed in the migration with the following error: 

Details:

The source flow does not exist in the source environment.

Recommendations:

Make sure the flow exists in the source environment, and rerun the migration job.

#PP-FlowRequiredActionConnectionHasNoPermission

Issue:

The flow failed in the migration with the following error: 

Details:

The destination Power Platform connection user does not have permissions to the parameters configured in the destination flow action.

Recommendations:

Grant at least the "Read" permission to the parameters for the user, and rerun the migration job.

#PP-FlowRequiredActionParameterIsIncorrect

Issue:

The flow failed in the migration with the following error: 

Details:

Some action parameters are incorrect.

Recommendations:

Refer to the error details about the action parameters in the comment of the mapping by navigating to the Projects > Project mappings > View mapping report > Migration error page in the Fly interface. Try resolving the errors for the action parameters and rerun the migration job.

#PP-FlowSPTriggerConnectionHasNoPermission

Issue:

The flow failed in the migration with the following error: 

Details:

The user of the connection used by the destination flow trigger does not have permissions to the list configured in the destination flow trigger.

Recommendations:

Grant at least the Read permission of the list to the user, and rerun the migration job.

#PP-FlowSPTriggerParameterIsIncorrect

Issue:

The flow failed in the migration with the following error: 

Details:

The destination does not have a site/list/view with the same title as the source site/list/view configured in the flow trigger.

Recommendations:

Correct the destination site collection URL configured in the site mapping. Ensure the destination has a site/list/view with the same title as the source site/list/view configured in the flow trigger. Rerun the migration job.

#PP-FlowTriggerParameterIsIncorrect

Issue:

The flow failed in the migration with the following error: 

Details:

The parameters configured in the source flow trigger are not supported in the migration.

#PP-FormsIdCannotReplaceWarning

Issue:

The parameter has been migrated but has the following error: 

Details:

The Microsoft form ID of the Form Id parameter value cannot be replaced with a destination Microsoft form ID due to Microsoft Forms API limitations.

The source form.

The Form ID parameter.

In the destination, the source form ID will be displayed in the Form Id parameter.

The destination form.

Recommendations:

Refer to the following steps to resolve this issue:

1. Find the migrated flow in the destination.

2. Manually configure the Form Id parameter of related Microsoft form actions/triggers to a valid Microsoft form ID.

3. Check whether the flow can work as expected.

#PP-FormsIdPlaceHolderWarning

Issue:

The parameter has been migrated but has the following error: 

Details:

Due to Microsoft Forms API limitations, the Microsoft form ID of the Form Id parameter value of the Get response details action cannot be replaced with a destination Microsoft form ID. To ensure the flow can be migrated, Fly has replaced the Microsoft form ID with a placeholder.

Source

Form ID

Destination

Recommendations:

Refer to the following steps to resolve this issue:

1. Find the migrated flow in the destination.

2. Manually update the placeholder in the Form Id parameter of the related Microsoft form action to a valid Microsoft form ID.

3. Check whether the flow can work as expected.

#PP-GroupNotSecurityEnabled

Issue:

The permission failed in the migration with the following error: 

Details:

The destination group is not a mail-enabled security group, and cannot be added to the destination app/flow.

Recommendations:

Update the user mapping to map the source group to a mail-enabled security group, and rerun the migration job.

#PP-IncorrectReplacementForPackage

Issue:

The flow failed in the migration with the following error: 

Details:

Errors in replacing the flow’s packages caused an invalid JSON structure, resulting in an unsuccessful import to the destination environment.

Recommendations:

Contact Support and provide the migration mapping information and job ID to analyze the error.

#PP-LackCorrespondingTypeConnection

Issue:

The app/flow failed in the migration with the following error: 

Details:

When the destination service account or app profile consent user does not have the connections of the same type as the source connection in the destination Power Platform environment, this error will appear.

Recommendations:

Make sure corresponding connections are created by the service account/app profile consent user in the destination environment, and rerun the migration job. If you use both service account and app profile authentications, make sure the service account has the connections.

#PP-ListNotFound

Issue:

The parameter failed in the migration with the following error: 

Details:

The destination does not have a list, which has the same title as the source list configured in the source parameter.

Recommendations:

Manually create a list in the destination with the same title as the source list, and rerun the migration job.

#PP-NetworkError

Issue:

The flow/app failed in the migration with the following error: 

Details:

If you run many migration jobs at the same time, the error may occur on some flows/apps due to the following reasons:

Recommendations:

You can separate your jobs in multiple waves, and rerun the jobs later. Generally, the error will be resolved. If the error persists after you retry many times, you can contact Support and provide related job IDs for analysis.

#PP-NoAppProfileForMappingParameters

Issue:

The object failed in the migration with the following error: 

Details:

There is no app profile in the source or destination connection.

Recommendations:

Make sure both the source and destination connections have an app profile to map the source and destination trigger parameters, and rerun the migration job.

#PP-NoMapResultInDestination

Issue:

The parameter failed in the migration with the following error: 

Details:

No object in the destination can map to the object configured in the source parameter.

Recommendations:

Manually create an object in the destination with the same email address or URL as the source object, and rerun the migration job.

#PP-NotSupportChangeFlowOwner

Issue:

The user is skipped in the migration with the following information: 

Details:

The source and destination flow owners are not the same. Fly does not support changing owners for Power Automate flows due to API limitations.

#PP-NoSourceEnvironmentVariableInDestinationSolution

Issue:

The flow failed in the migration with the following error: 

Details:

The source flow uses environment variables, but the destination flow’s solution does not have the same environment variables of the source flow.

Recommendations:

According to the name, display name, and type of all environment variables used by the source flow, add the same environment variables to the destination solution. Then rerun the migration job.

#PP-NotSupportPermissionType

Issue:

The permission is skipped in the migration with the following information: 

Details:

Fly does not support migrating the permission.

#PP-ObjectNotFound

Issue:

The object failed in the migration with the following error: 

Details:

The object failed in the last migration job and was deleted from the source after the last migration job. Fly will not migrate the object and will report it as Not found.

Recommendations:

Check whether the object exists in the environment. If the object does not exist, you can ignore this error. If the object exists, you can contact Support and provide the screenshot of the object in the environment, migration mapping information, and job ID to analyze the error.

#PP-ParameterDuplicatedResult

Issue:

The parameter failed in the migration with the following error: 

Details:

The destination has multiple Microsoft 365 objects with the same display name as the object configured in the destination parameter.

Recommendations:

Make sure the object name is unique, and rerun the migration job.

#PP-ParameterWarning

Issue:

The object has been migrated but has the following error: 

Details:

There are errors in the object's parameter.

Recommendations:

Refer to the error details about the parameter in the same Migration errors section. Resolve the error of the parameter, and rerun the migration job.

#PP-PermissionWarning

Issue:

The object has been migrated but has the following error: 

Details:

There are errors in the object's permission.

Recommendations:

Refer to the error details about the permission in the same Migration errors section. Resolve the error of the permission, and rerun the migration job.

#PP-SiteCollectionNotFound

Issue:

The parameter failed in the migration with the following error: 

Details:

The destination does not have a site collection, which has the same relative URL as the source site collection configured in the source parameter.

Recommendations:

Here are two options to resolve this issue:

Then rerun the migration job.

#PP-SourceAppHasBeenDeleted

Issue:

The app failed in the migration with the following error: 

Details:

The source app has been deleted from the source environment.

Recommendations:

If you want to re-migrate the app, delete the current migration mapping, and create a new mapping for the app. Then rerun the migration job.

#PP-SkipByResolutionPolicy

Issue:

The app/flow is skipped in the migration with the following information: 

Details:

The destination has an app/flow with the same name. Based on the Skip conflict resolution configured in the migration policy, the app/flow is skipped.

#PP-SourceEmailIsEmpty

Issue:

The user failed in the migration with the following error: 

Details:

Only the Email address prefix property is enabled in the migration policy to map users, but the source user does not have a mailbox.

Recommendations:

Make sure the source user has a mailbox or enable multiple properties in the migration policy. Then rerun the migration job.

#PP-SourceFlowHasBeenDeleted

Issue:

The flow failed in the migration with the following error: 

Details:

The source flow has been deleted from the source environment.

Recommendations:

If you want to re-migrate the flow, delete the current migration mapping, and create a new mapping for the flow. Then rerun the migration job.

#PP-SourceParameterForbidden

Issue:

The parameter failed in the migration with the following error:

Details:

The source app profile does not have sufficient permissions to retrieve source parameters.

Recommendations:

Make sure the source app profile has sufficient permissions to retrieve source parameters, and rerun the migration job. If this issue persists, you can contact AvePoint Technical Support for assistance.

#PP-SourceParameterNotFound

Issue:

The parameter failed in the migration with the following error:

Details:

The object configured in the source parameter does not exist in the source tenant.

Recommendations:

Update the source parameter with an existing object, and rerun the migration job.

#PP-SourceUserOrGroupNotFound

Issue:

The user/group failed in the migration with the following error: 

Details:

The source user/group does not exist in the tenant.

Recommendations:

Check to make sure the source user/group exists in the tenant, and run an incremental migration job.

#PP-SPColumnParameterRequiredException

Issue:

The flow failed in the migration with the following error: 

Details:

The SharePoint column related to the source action or trigger does not require information and the column value is empty, but the corresponding destination column requires information. In this way, source parameters will fail in the verification by the destination.

Recommendations:

Here are two options to resolve this issue:

Then rerun the migration job.

#PP-SPContentTypeParameterException

Issue:

The flow failed in the migration with the following error: 

Details:

An error occurred while replacing the content type parameters of the source and destination flows.

Recommendations:

Refer to the following steps to resolve this issue:

1. Enable the Allow management of content types setting for the list/library related to the destination flow.

2. Configure a content type ID mapping in the format of ExtraMappings={"SourceContentTypeID*":"DestinationContentTypeID**"}, and added the configured ExtraMappings={"SourceContentTypeID":"DestinationContentTypeID"}* feature string in the Customized features section in the migration policy.

3. Rerun the migration job.

#PP-SPListTypeMismatchError

Issue:

The flow/app failed in the migration with the following error: 

Details:

The error occurs in the following situation:

When migrating the flow or app that is associated with a SharePoint list or library, Fly will find the corresponding list or library using the list title in the destination. However, the found destination list’s or library’s template is different from the source one. Therefore, the migrated flow or app in the destination cannot work correctly.

Recommendations:

Make sure the destination site collection of the associated source site collection has a list or library, which has the same title, template, columns, content types, and other configurations as the source. Then rerun the migration job.

#PP-TurnOffFlowInSolution

Issue:

The flow failed in the migration with the following error: 

Details:

The flow is created in solution and has been turned off.

Recommendations:

Turn on the flow and rerun the migration job. If the error persists, contact Support and provide the migration mapping information and job ID to analyze the error.

#PP-UnknownError

Issue:

The object failed in the migration with the following error: 

Details:

An unknown error occurred while migrating the object.

Recommendations:

Contact Support and provide the migration mapping information and job ID to analyze the error.

#PP-UnknownParameterError

Issue:

The parameter failed in the migration with the following error: 

Details:

An unknown error occurred while migrating the parameter.

Recommendations:

Contact Support and provide the migration mapping information and job ID to analyze the error.

#PP-UnknownPermissionError

Issue:

The user failed in the migration with the following error: 

Details:

An unknown error occurred while migrating the user.

Recommendations:

Contact Support and provide the migration mapping information and job ID to analyze the error.

#PP-UserCanNotShareAppWithEveryone

Issue:

The permission failed in the migration with the following error:

Details:

The Power App cannot be shared to everyone in the destination.

Recommendations:

Refer to the to configure the destination environment and rerun the migration job.

#PP-UserFindOptionsNotConfigured

Issue:

The user failed in the migration with the following error:

Details:

There is no user mapping configured, and no auto-mapping option (User Principal Name Prefix, Display Name, or Email Address Prefix) enabled in the migration policy.

Recommendations:

Create a user mapping to map the source user to an existing destination user, or enable at least one auto-mapping option in the migration policy. Then rerun the migration job.

#PP-UserFlowLimitReached

Issue:

The flow failed in the migration with the following error:

Details:

The number of flows created by the destination service account has reached the allowed limit.

Recommendations:

You can delete flows created by the destination service account that are no longer needed, or change to use a different service account. Then rerun the migration job.

#PP-ZipPackageBroken

Issue:

The app/flow failed in the migration with the following error:

Details:

The error occurs in the following situation:

When migrating the app/flow, Fly will replace and transfer the source definition package to the corresponding destination storage, but cannot retrieve sufficient permissions to check the package due to Microsoft restrictions on the storage. When meeting a bad network, the package on the storage may be broken though related migration APIs are not affected.

Recommendations:

Rerun a migration job to resolve this error. If the error persists, add the EnableDebugLog=true customized feature in the migration policy and rerun the migration job again. If the error persists, contact Support and provide the tenant owner and the last job ID for assistance.