Liquid error: Value cannot be null.
Parameter name: key
Microsoft Dynamics 365
Thank you for your suggestion. We will consider this functionality for a future release. Best regards, Prashanth GanapathyRaj, PM, Dynamics CRM R&D Team. This posting is provided "AS IS" with no warranties, and confers no rights.
We agree. Switching from Classic interface to the Unified User Interface will be extremely tough for us without the Print Preview feature that is currently on the Classic interface.
I agree. Users would like to see "Today at [time]" or "Yesterday at [time]", not just "Today" or "Yesterday". Time of the activity is much more relevant for recent activities, but it's only shown for older activities.
agree, we are missing this, too , especially in Accounts
Michael is right, the mail merge function is essential for some customers. Please provide an equivalent alternative.
Thank you for your feedback. This is not a common use case, and we are not planning to consider this at this point.
We currently have a need for this as well. We have an "assigned to" field for tasks and our users can't assign a task to someone else. The only option they have is to change the owner which then pops up an error message. We've been told by Microsoft it is working as designed but for us without the "assigned to" field the quick create is useless because they have to go to the main form to reassign.
Wow! Obscure but important find! This is definitely not sensible behaviour at all. I agree that the common understanding of using lock pricing is to ensure that the price for each line item won't change or be recalculated between creating the Order and Fulfilling it. The message that Orders generally can't be editing once fulfilled (other than to be cancelled) is generally accepted, and is clearly be the right way for this to work. If several years passed before someone introduced a duplicate and then merged the records, the pricing would be vastly different. Having said that, even a penny / cent out is deeply wrong. I'd be interested to know if this is also reproduced on Quotes and Invoices, and how this impacts customers using integration to their financial system - do they end up with loads of unreconciled invoices which no longer match the payments made against them? Hopefully the finance / ERP system is better at locking records so they don't get updated.