Replies: 1 comment
-
Also, I want to point out that during the import phase the second part of the import when you select the account to use for the connections required for the powerapp, there were NO connections listed. I believe this might be something related. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I was wondering if anyone has had this issue:
The tool ran with no issues, and I could import the converted package into my target tenant. Still, when testing the app, in the gallery where I display the sharepoint data, I received an error stating the list ID was not recognized, meaning the app was connecting to the list properly. This is interesting because I was authenticated correctly with the target tenant and also, when I click on edit data source it correctly re-directs me to the correct sharepoint list in question.
Is there any artifacts from the source tenant that can linger within the .maspp file that could cause this error? Because the JSON files within the zip file all correctly map to the target tenant.
Beta Was this translation helpful? Give feedback.
All reactions