Tag: Model Driven Apps
While modern app designer provides phenomenal low code experience, it still misses some small and useful components in the classic editor. One such component is spacer control. Currently, this can be added to the form only by switching back to the classic designer, once added, we can switch back to the modern editor. Please upvote the Idea suggestion here to enable this component in the modern designer.
Every time when a user runs a powerapp with connectors for the first time, they will receive a popup asking their consent to use the connectors in the specific app.
Use the Set-AdminPowerAppApisToBypassConsent cmdlet to bypass this pop-up, so that users are are not required to authorize API connections for the input app. The command changes the
bypassConsent flag of an app to true. Using this command, end users will observe consent is bypassed for First Party connectors that support single sign-on and custom connectors that don’t require authentication. This includes custom connectors with or without a gateway. Read more here.
It’s known behavior that, if you test a cloud flow that runs for longer than 10 minutes, you may get a timeout message in Power Automate, even though the flow continues to run in the background. If this happens, reopen the view to receive the current status.
Changing an environment type to sandbox will immediately reduce backup retention to 7 days. If you do not need backups (restore points) older than 7 days, then you can safely switch the type. If you think you may need restore points older than 7 days, it is recommended that you keep the environment as production and consider restoring to a different environment of type sandbox. Read more on the official docs here.
The new modern model-driven app designer has an easy to use interface, and in sync with canvas app designer. However, the preview has the following known limitations.
- You can’t add the following model-driven app components:
- Business process flows
- You can’t add more than one area to the app’s navigation site map.
- You can’t change the app’s icon.
- You can’t specify the app’s URL.
You can use the Switch to classic option to use the classic designer to complete the above app design tasks.
Don’t be like our Buddy in the above comic strip, always check the official docs to see the known limitations, read more here.
Sometimes, the most useful things may go unnoticed, this FLOW template can provide a list of new apps, flows, and connectors that have been introduced into your tenant within a configurable window. This is very useful when you are an admin and have to do some house keeping activities in the tenant.
Sharing an app with the user and, asking the user to run the app for one time will resolve this issue for most cases. I have had few instances where, new users with maker roles were unable to see the environment in the maker portal even after sharing the app. However, sharing a sample App with Co-owner permission resolved this issue.
The underlying structure of Model-Driven apps are totally different than Canvas apps. Model-Driven apps are created at environment level and owned by the organization so, if you need to give delete permission for model-driven apps, it should be given at the environment level. Means, this will give the permission to delete apps created by other users as well. This is the main reason why Model-Driven app delete permission is restricted to admin roles.
Backups for production environments that have been created with a database and have one or more Dynamics 365 applications installed are retained up to 28 days. Backups for production environments which do not have Dynamics 365 applications deployed in them will be retained for 7 days. Sometimes, this can be a bit confusing but, very important to understand the differences, read more from official docs here.