-
Notifications
You must be signed in to change notification settings - Fork 10
FAQ
Note: Exercise caution when performing any of these actions to mitigate the risk of unintended consequences.
If you're facing this issue, perform the following steps:
- Navigate to the flow's Overview page which is dependent on the problematic
connectionreference
. - Click on Owners, then Edit.
- Scroll down to the section named Embedded Connection References.
- Remove all items listed under Other Connection References.
These references are extraneous and not actively utilized by your flow. Removing them should resolve the issue.
The exported solution captures the "live" version of your app. To include your latest changes in the export, follow these steps:
- Open Solution Explorer.
- Select your app.
- Click the ellipses (...) for additional options.
- Choose Details, then go to Versions.
- Select the version you wish to include in your export.
The Power Platform may cache query results from your SAP system. This could mean that subsequent queries do not reflect the latest changes in SAP. To force a cache refresh:
- Turn off the flow and then turn it back on.
- Change the variables value via the Default Solution
- Turn all flows off and then back on so the new value is used.
Source: Third Bullet point on this page. Use environment variables in solutions - Power Apps | Microsoft Learn
- Make sure the connection references are pointed at valid connections within your account.
- Double check and possibly delete the unmanaged layer ontop of that flow.
GIT is designed to track changes in text-based files. However, it lacks support for performing a diff
on .msapp
files. To work around this, the processCanvasApps
flag is used during the downloading process. This enables us to unpack the .msapp
files using the Power Platform CLI. As a result, all changes become trackable and easily viewable in your GitHub repository.