This is one of the limitation in editable grids. Currently, it supports only pagination, no record count or selected record count.
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.
From my experience, it’s better not to give delete permission to end users, upvote here, if you agree.
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.
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.
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.
Knowing the limitations of each UI will help you to save some precious time .
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…
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.
It totally depends on your plugin style: In case for early-bound, I like using LINQ because it’s strongly typed and It helps development speed. Certain benchmark test have proved that Fetchxml is slightly faster than QueryExpression.
As per Microsoft official docs, there is no visible performance difference but just a personal preference of the developer.