on
RE:
There is a third limitation to the unopened filter. It doesn't refer to work items but to accounts. So once I complete the first step of a sequence the status remains opened even though I haven't touched the next step yet. So you can only filter on unopened first steps, but not on any "unopened" steps after that.
RE:
2501210050004017, An issue was raised in this case. The customer's suggestion was to display an error message showing the current user permissions and the required permissions, making it clear what needs to be done next.
RE:
https://releaseplans.microsoft.com/?app=Microsoft+365+Copilot+for+Sales&planID=99537884-cffc-ee11-a1fe-6045bdec599f
RE:
and it looks like it's coming in March 2025
RE:
This should get a lot more votes! This is essential for Call center operations.
RE:
Yes, sorely needs a checkbox somewhere - having the default tab change (especially to hidden pages) when you save is a pain.
RE:
Yes, same problem here, new functionality make us create hundreds of security groups in order to restrict access to specific companies.
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.