0
Category:
STATUS DETAILS

Comments

Export for emissions are timing out , we are trying to export emission with filter anything above 30k record is really slow and times out.

Category:

This was requested under Bug 906344. The PG suggested to create an idea for this functionality.

Category:

Do you have an update on this or are there good workarounds to solve this issue in the meantime?

Category:

This is a highly valuable suggestion. Acknowledging the inevitability of SQL disconnections in a SaaS environment, as outlined in the Dynamics 365 documentation, it's clear that the current behavior of batch jobs failing upon brief connection losses to Microsoft SQL Server significantly disrupts business operations. The introduction of a system that notifies administrators of such disconnections, along with their duration, represents a critical improvement. It would not only enhance transparency but also mitigate confusion and frustration by providing clear explanations for the errors users encounter. Implementing this feature would significantly improve the user experience and operational efficiency, supporting our continuous commitment to service excellence.

Category:

Pay no mind to my last comment.


I was unaware that in newer versions of BC, both install-navapp and start-navappdataupgrade both have a -syncMode switch (meaning you don't need to first run sync-navapp first).


If install/upgrade fails, the schema sync will also roll back

Category:

That's unfortunate that it was declined but I'm not surprised.


That said, I think Microsoft needs to re-think how extensions are synched and upgraded.


Currently if you successfully sync-navapp but start-navappdataupgrade fails, it leaves the app in an unusable state!


I think there should be a way to somehow batch both sync-navapp and start-navappdataupgrade into a single transaction.


If sync-navapp succeeds but start-navappdataupgrade fails, everything should be rolled back including the schema sync.


Unfortunately that doesn't happen currently and because it this, it leaves the app in a useless uninstalled + unupgraded state.



Category:

This can be configured but not using standard methods. Neil Parkhurst has a blog article here https://neilparkhurst.com/2023/11/11/omnichannel-for-customer-service-identify-customers/ where he outlines the steps to patch your Workstream with the revised conditional logic. These are the same steps you are given if you go through support.

Category:

Is MSFT going to do this idea this century?.

Category:

Allowing a template as suggested here would allow for a separate no series to be used for Shopify orders (especially if the company has multiple shops ). We need to be able to assign a no. Series to sales invoices that differs from what is assigned in the SR setup page.

Category:

This says completed, but I do not see this field in the admin center.

Category:

  • 1
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 500