Giving back to the community what I have learned
Category: I Wish I Would Have Known
With this deprecation, XRM object won’t be available in HTML web resources. This will mainly affect the HTML web resource as part of the SiteMap, parent.Xrm.* also won’t work. Read more here
You can enter a user’s email address and see the list of published apps in your environment and all the access, license, and security information specific to that user. This can be very useful in troubleshooting why a user cannot see a specific app in your environment. The tool can be accessed from the admin center or via direct URL.
https://<org>.crm.dynamics.com/WebResources/msdyn_AppAccessChecker.html
Hope this helps..
Though it’s possible to control using logic, it’s nice to have this property out of the box. Please up vote here
A single default environment is automatically created by Power Apps for each tenant and shared by all users in that tenant. Whenever a new user signs up for Power Apps, they’re automatically added to the Maker role of the default environment. The default environment is created in the region closest to the default region of the Azure AD tenant. Read more
If a connector is not listing standard details like Time zone, Languages, User details, etc. Please check all required graph API permissions are added for the current user. You can find the required permission details here.
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.
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
Always consider the connector limitations when you design a Power platform solution. Read more about the teams connector limitation here.
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.
nijos.dev 