Giving back to the community what I have learned
Tag: Nijo Joseph Raju
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.
‘GetTable’ failed with status code ‘Unauthorized’
Recently, one of our business users had left the firm, and handed over the canvas apps he was developing to his colleagues. There was one canvas app with flows that update SharePoint list. He had shared the app .zip file with the team and told, it’s a completed app and just needs to import to the target environment after creating the SharePoint list. So, the team didn’t bother much to collect further details about the source tenant where this was developed. He had created the app on a trail tenant which was tied with his account and was lost as soon as he left the firm.
But, the business users were unable to import the app and came to us with the below error.
Flow save failed with code
'DynamicOperationRequestClientFailure' and message
'The dynamic operation request to API 'sharepointonline' operation 'GetTable' failed with status code 'Unauthorized'.
This may indicate invalid input parameters.
Error response: { "error_description": "Exception of type 'Microsoft.IdentityModel.Tokens.AudienceUriValidationFailedException' was thrown." }'.
The issue here was the SharePoint site dependency. The definition.js files of the Power Automate flows had references to the old site and the current user does not have access to the original site, hence the flow was failing with error ‘Unauthorized’ even though, SharePoint connection was created in the target environment.
The fix was to edit the definition.js file and replace the SharePoint URL and List ID with the new site information. The definition.js file is in the exported zip file. We had to replace all the occurrence of the URL, list ID (defined under table) and view ID, and saved the definition.js file and copied it to the zip file. Importing the updated zip file worked.
{"dataset":"https://***.sharepoint.com/","table":"d2**826-e05a-4972-be****8","view":"**-27f2-4ace-a289-ef41a**"}This is a known issue when moving PowerApps/ Power Automate to a new tenant. This behaviour is not consistent as some flows were imported with no errors and others were rejected due to Unauthorized exception on GetTable().
One way to avoid this issue, is to use variables instead of directly selecting the SharePoint site, list and view in the SharePoint actions inside your flow.
Another option is to use environment variables in your flow. This will also help us avoid direct SharePoint references in your flow.
Hope this helps.
If you know any alternate option to handle this, please let us know in the comments.
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.
Changing an environment type to sandbox will immediately reduce backup retention to 7 days. If you do not need backups (restore points) older than 7 days, then you can safely switch the type. If you think you may need restore points older than 7 days, it is recommended that you keep the environment as production and consider restoring to a different environment of type sandbox. Read more on the official docs here.
Sometimes, the most useful things may go unnoticed, this FLOW template can provide a list of new apps, flows, and connectors that have been introduced into your tenant within a configurable window. This is very useful when you are an admin and have to do some house keeping activities in the tenant.
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.
nijos.dev 