Gregg Hoang

Hello team,

At the moment, conversations which are associated with cases do not automatically close when the cases are closed, unless the associated case record is deleted, according to this document: https://learn.microsoft.com/en-us/dynamics365/customer-service/administer/auto-close-conversation-powerapps

Please help implement the option to automatically close conversations when cases are closed.

Hello team,

I'm creating this idea thread in order to request for a dedicated limit on number of rows that an user can Export to Excel file.

As far as I know, the limit is roughly 500k rows of records, and this limit can be changed dynamically at times depending on the load of the server, which can sometimes cause some customers fail to export data if the request is not finished within 4 minutes.

This idea thread is also created in hope to increase the number of records that the user can exported by any means necessary without having to return error. If possible, we can try to have the export be done at a latter time so the system can support a much larger request ( e.g: Asking the user to return after 7 days if the number of records are too large, so the server can take its time to do the records )

Hello team,

At the moment, date & time format for exported Dataverse tables on Azure Synapse Link have 3 different formats for the following columns

• SinkCreatedOn & SinkModifiedOn | M/d/yyyy H:mm:ss tt
• CreatedOn | yyyy-MM-dd'T'HH:mm:ss.sssssssXXX
• All other datetime columns | yyyy-MM-dd'T'HH:mm:ss'Z'

This would cause date & time management for them hard to manage. Therefore, I'm creating this Idea in order to request to make all 3 formats to be consistent. Thank you for your help.

Information gathered from: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/export-data-lake-faq#what-date-and-time-formats-can-be-expected-in-exported-dataverse-tables