I Wish I Would Have Known #19: Maker Portal: User Cannot See an Environment

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.

I Wish I Would Have Known #18: Delete Permission for Model-Driven Apps

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.

I Wish I Would Have Known #17: Environment Backup Retention Periods

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.

I Wish I Would Have Known #13: Canvas-App Date Picker Accepting Invalid Formats.

The IsEditable property of Canvas-App’s Date Picker control decides whether the date picker text can be edited. If false, the date can only be changed by using the calendar. Read about the date picker properties here.

I Wish I Would Have Known #11: Unable to add Licensed Users to Power Platform Environments.

 Dynamics 365 Enterprise licenses does not include general purpose Power Apps capabilities. Dynamics 365 Enterprise users will continue to be able to run apps and portals that extend and customize the licensed Dynamics 365 application, as long as those apps and portals are located in the same environment as their licensed Dynamics 365 application. Custom apps or portals outside of the Dynamics 365 environment will require a standalone Power Apps license. In short, If a user A has only dynamics 365 license applied, then A can be added only to environments which has at least one Dynamics 365 App installed. Read more here.

I Wish I Would Have Known #10: PowerAutomate Flows Maximum Run Duration.

Flow steps including pending approvals, will bed timed-out after 30 days. It is always good to know the duration limits of the platform. You can find the platform duration limits here.