Power Platform Governance and Administration

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 .

This suggestion revolves around the automatic lookup "name" field resolution. I'm posting it under "customer service", but it's really about the broader Dynamics 365 CRM system logic.

How the platform works:

-----------------------

Every time an entity is opened (i.e. 'Retrieve' operation) or when multiple records are searched (view, advanced find, etc. i.e., 'RetrieveMultiple' operation) all the lookup names are resolved again. Even though in the CRM DB there are columns for both the lookup record id and name, the platform will always resolve those lookup names again.

This is understandable as the name may have changed in the interim, so it would be appropriate to show the latest information to the user rather than show them the old value that was populated when the parent record was saved. This is really useful as I've used this behavior multiple times when I wanted to translate lookup names for multilingual environments where each user wanted to see the values in their own language by creating the necessary retrieve and retrievemultiple plugins.

Issue Description:

------------------

Quite often the primary name of some configuration entities will really never change or very rarely change. Having an extra retrieve operation for those entities is an overkill that simply takes extra processing time and makes the user experience much slower. The worst part though, is when those lookups point to virtual entities. Each time they are resolved this is a call to another system to fetch their latest name. I have retail customers that have 5-10 lookups on the case and phone call entities in order to link the case to the ERP records the case is for. Each time the case is reasssigned or during resolution or even when an irrelevant field is updated, those lookups are again getting resolved resulting in extremely slow system response times for the end user. The names of those entities are really the order number, order line number, loan number, coupon number, etc. Names that are really impossible to change, yet they have to get resolved again on every operation on the parent entity. If all of them are populated that's 10 calls to an external system to get the data. Not to mention that if you add them in a view then that's 25-250 records that need to get resolved so that's another call to the external system.

Suggested Improvement:

----------------------

The ideal way to address this would be to have the automatic lookup name resolution on the entity level as a configuration. Just another checkbox to configure the desired behavior per entity. For entities were the implementer knows this is fixed data that never changes they can elect to turn this off and speed up the system. This doesn't need to be done only for virtual entities, it can be done for all entities in CRM. This would be the best way to address it. That way the issue for never changing lookup resolution can be addressed, especially for customers that heavily use virtual entities.

I would take it one step further for rarely updated ones as well and if the automatic resolution is disabled for one entity, then at the level of the parent record form show an icon next to the lookup to update the latest name. Similar to the behavior of roll-up or calculated fields.

The system performance improvement for virtual entity lookups will be massive if this is done.

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.

Business need: Export of charts from the dashboards to PDF or XLSX file. Now users don't have this possibility and only workaround of this missing feature is creating screenshots.

The reset should follow the same process as delete. With the UX and the retention of recovery points for 7 days, therefore, enabling a reset environment to be recovered even if a different organization name is needed when performing the recovery.

You can recover a recently deleted environment (within 7 days of deletion), by using the Microsoft Power Platform admin center or the Power Apps cmdlet Recover-AdminPowerAppEnvironment.

https://docs.microsoft.com/en-us/power-platform/admin/recover-environment

Removing a recovery point to free space should require a secondary action and not be linked to reset.

The confirmation of a reset should require the environment to be typed the same as delete, which follows ux experience elsewhere in Azure when destructive actions are performed.

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.

In the current design, there are few gaps between currency symbols and numbers, which makes it very difficult to see.

I want end users and administrators to be able to freely change the gap.

This is what many end users want.

Content in Timeline in Description field should be translated as per User Language. Example:

Case Title: XXX

Case Number: YYY

Case Status: New

Then "Case Title", "Case Number" & "Case Status" should be translated as per User Language 

We should have provision to update/set the Escalated On field in Case, either through UI or Code.

Hi,

We have been enhancing Microsoft Office on regular basis, even then eventually the end user has to do it manually.

The idea is to use voice based commands to perform tasks in Ms Office, specially MS Excel.

Like, Calculate the average of column A, Create a Pivot Chart, Apply Vlookup, Create graph.

This would save lot of time and make the product futuristic.

Regards

Smithesh