From my experience, it’s better not to give delete permission to end users, upvote here, if you agree.
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.
I Wish I Would Have Known #9: Delete Button not Available for Business Rules in PowerApps Maker Portal
Not sure if I am missing something but, I couldn’t find the delete button in the PowerApps maker portal whereas, it is available in the classic UI.
I Wish I Would Have Known #8: Changing Yes/No labels in new UI.
Knowing the limitations of each UI will help you to save some precious time .
I Wish I Would Have Known #7: Email Tracking in D365 using duplicate email address
If you are using email tracking and your system has records that share the same email address then, emails will be tracked to all records that uses the same email. You need to consider this when designing your solution…
I Wish I Would Have Known #6: PowerAutomate Nesting Depth Limit
This is one place where it becomes important to design your flows the right way straight from the beginning. Even when your flow is still quite small. More details.
I Wish I Would Have Known #5: PowerAutomate Flow Expiration Limits
There is an automated FLOW turn-off (expiry) policy based on license type and FLOW condition, read more details here.
I Wish I Would Have Known #4: N:N Events in CDS connector.
Currently, CDS connector doesn’t have events for N:N association and disassociation.
View Idea status in Power Automate Ideas portal.
I Wish I Would Have Known #3: Quick Create Forms
Although you can define multiple quick create forms, only one quick create form can be used by everyone. The form everyone will use is set using the form order. Quick create forms cannot be assigned to security roles and they do not provide the capability for the user to switch forms.