Use the logical name of the embedded canvas app
Problem: I have embedded canvas apps inside a Model app that I deploy via a solution. When I move from Development to Test, the users reported that they don't have access "This app isn't opening correctly" "It looks like you don't have access to this app." And when I dive deeper, I see the Model app in Test is point to the Development Canvas App; not the test canvas app.
Initial Hypothesis: My thinking is that the Model App in Test is pointing to the Canvas App in Dev. In dev, I point to the test canvas app and it works. The workaround is to Open the managed solution in the Test environment and change the AppId to the App Id of the canvas App in TEST. It works but it's an awful work around. This tells me that my App Name is not working, as the Static App name is used before the AppId (looks for the app name in the current environment) and then the AppId when the app Name doesn't resolve, I believe the app name is not working.
I changed the AppId (to a non-existing guid) and the app wouldn't load in dev. The app name should be the logical name and not the display name.
"The App Name property specifies the name of the canvas app to embed. The model-driven form looks for the canvas app with the specified name in the current environment. If a canvas app with that name can't be found in the environment, the canvas app control will use the App ID to load the canvas app. Enter the App Name for an existing canvas app." Add an embedded canvas app on a model-driven form - Power Apps | Microsoft Learn
Resolution: Open the table > Forms > Form containing the canvas app
More Info:
0 comments:
Post a Comment