Power Platform Governance and Administration

In certain scenarios the robots (via RPA) have to delete the value which has been put into a lookup field because of some automation steps.

Its hard to delete the lookup values which are already pre-filled due to the dynamics position of “cross” (X). This is because the only way to delete the selected lookup value is to “find” the cross (X) and click on it as hitting backspace to remove the value is not possible. RPA is using the visual component which uses an anchor point to count the pixels where the click has to be made. The distance between the anchor point and the “cross” is dynamic and depends on the length of lookup value.

So if Platform as OOTB capability can provides the provision (or configuration) to fix the position of "Cross" (X) in lookup fields value say the first position OR a button in every lookup field which did a “clear selection” would already help a lot.

It might be a good idea to allow customers to turn on a "locked for editing" setting in dynamics that would apply to the form editor. Currently, this is the situation

1. Person A opens Form A to edit it
2. Person B opens Form A to edit it while Person A still has the form open
3. Person A saves and closes the form
4. Person B saves and closes the form after person A

What happens is that all of Person A's changes are lost/overwritten by Person B's changes.

Adding the ability to "lock" a form for editing would allow users to deconflict that issue. You would have to also add the ability to "overwrite" that lock or be able to turn the lock off if there was some type of connectivity issue or a say User A forgot to save and close out the editing form

We have dashboards and need to look at discrete time periods in past not movable each day you look. Last 2 Months needs to be last 2 full months up top previous month end. So currently in Jan you see, some of Jan, All of Dec and some of Nov for last 2 months. Last 2 months in Jan needs to be all of Dec and Nov

Most people when reporting looking at last 2 months would look at point up to a month-end because it is constantly moving otherwise and no use for KPIs.

This needs to be added even if you call it "Previous X months".

You could then keep the "Last" to be that movable feast for which I cannot see much use, considering you can already use the previous 30 days previous 60 days etc.

Is this in the pipeline?

Many thanks

John

Hello, I would like to suggest that Microsoft add Angolan currency (Kwanza) in Microsoft Dynamics 365 packages.

It would be great if you could print out a service request from within the Customer Service Hub. Currently, you're only able to print screen which does not allow you to view the entire service request as a whole.

In Category master, we have OOB translation provision for "Title" field, can we have similar for "Description" field too

In Interactive Dashboard, if we have any Chart on Category field, while changing the language by user, that is reflecting in respective language, BUT normal Dashboard it is not translating.

one of our Customer is having an error once he tries to saved a new virtual entity data source. Customer needs to store on this form several fields to access to his external service .

Error while saving new datasource The length of the 'connectiondefinition' attribute of the 'entitydatasource' entity exceeded the maximum allowed length of '2000'.

This a limitation as of now and The product group is working on increasing this limit and it would be great if this is done so that if there are any other customers they can avoid this scenario .

The single valued property in this audit API https://docs.microsoft.com/en-us/dynamics365/customer-engagement/web-api/audit?view=dynamics-ce-odata-9#single-valued-navigation-properties

does not seem to be working for the expand parameter now and as mentioned by the support this seems to be a product behavior henceforth. 

Please update the document to reflect that the userid fields are not supported as single value navigation properties to clear the discrepancies.

Currently DataVerse search does not index the contents of email messages and appointment details, only the subject line. This limits the usability of searching these entities significantly as clients are expecting to be able to search for email messages based on the contents of that email, not just the subject.