Mustaque Ehiya

Option to set the trigger condition based on related tables. Currently only the primary table can be set with conditions and cannot include related tables.

We have to add a conditional step and check the related table conditions and if not met, cancelling the flow run, instead if this can be validated at the trigger state, it will save a lot of Cancelled Runs and unneeded API calls.

In Power automate, we dont have any option to set the trigger condition based on related tables. Currently we have option only to set against the base table.

For existing flows, we have to add a block to check the conditions and if not met, cancelling the flows. With the option set in the trigger itself, a lot of cancelled runs and unneeded api calls can be avoided.

Currently we dont have any option to view the API usage by different Application users / Service Principal Accounts.

Having an option to view the list for usage greater than a certain usage (eg - maybe 10 or 20k calls/day) will help the team to monitor the usage and split the API calls accordingly among multiple accounts instead of relying on one account until it fails maxing out.

Currently, the admin should access each environment individually and apply the Version upgrade for each app. Admin should have option to synch and upgrade a D365 App to a single version across all environments in the tenant.

Currently, if there are any in-progress solution imports, we get an error and cannot start another import. Instead, Users should have the option to import the solutions anytime without any failures and the solutions should be imported sequentially and asynchronously.

This will avoid failures in ADO pipeline automated deployments. Also, we don't have to set a maximum duration for solution import as even with the same solution, the import time varies in the same instance or different environments.

Currently GUID is displaying under "Top Workflows by Failures" section. Instead, it should display the system job name.