RE:
I Agree, this should be a must, I understand schema should be same in source and destination environment, but it is just that.
RE:
Would love to hear an update on this one, we've got multiple use cases for it.
RE:
Totally agree too. I still do not understand how it is possible for line items to appear in ascending order within the CRM but change to descending order when exporting to a Word or PDF document. In conversations with Microsoft Support, they told me that they use the following expression:entityExpression.Order.AddOrder("sequencenumber", Xrm.Sdk.Query.OrderType.Descending);I fail to understand why this cannot be configured to Ascending to resolve the issue, when in the .Net documentation it's says that they can do it. I am attaching the link so you can check what I am referring to: https://learn.microsoft.com/en-us/dotnet/api/microsoft.xrm.sdk.query.ordertype?view=dataverse-sdk-latestI do not understand why, if the option for Ascending order exists in the documentation, we are consistently told that it is not possible.
RE:
Also for the mirrored Azure Cosmos DB for NoSQL Entra Authentication would be relevant.
RE:
Using Entra ID authentication instead of token based auth would be a good enhancement, agree.
RE:
Localisation in such a market is the most significant selling point for Dynamics universally, it should be recognised for Greece as well.
RE:
This is what keeps us from using Fabric - customer wants a backup of lakehouse and also the retention period should be more than 30 days
RE:
We all need sometimes something like this. It is a great proposal. Thank you Bojan!
RE:
Agree with both, very much needed. It would be nice if they could make Web.contents API Key support work in the headers as well as in the URL
RE:
This will be quite valuable for some users, particularly in Japan where this visual functionality is in high demand.