Tag: Microsoft

I Wish I Would Have Known #27: Add Spacers in Modern Model Driven App Designer

Image: To add spacer switch back to the classic editor and add.

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.

I Wish I Would Have Known #26: Web API “RetrieveAllEntities” Function

Strip 26: Web API “RetrieveAllEntities” Function

The Web Api method “RetrieveAllEntities” function can be a bit confusing as it was not included in the early versions and will give you errors, if you have the older end point hardcoded in your code.

GET {{webapiurl}}RetrieveAllEntities(EntityFilters=Microsoft.Dynamics.CRM.EntityFilters'Entity', RetrieveAsIfPublished=true)

This function should be used with caution and appropriate filters, since it can return a huge amount of data. Read mode about the function here

I Wish I Would Have Known #25: Teams Connector, API Limits.

Always consider the connector limitations when you design a Power platform solution. Read more about the teams connector limitation here.

I Wish I Would Have Known #24: Bypass User Consent Pop-up

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.

I Wish I Would Have Known #21: Add new Area to Sitemap in Modern Model-Driven App Designer.

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:
- URLs
- Business process flows
- Charts
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.

I Wish I Would Have Known #12: Privilege Error while Converting an Existing Appointment into Recurring Appointment.

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.