0
Category:
STATUS DETAILS

Comments

Actually a custom-build a solution for each project to log incoming requests, responses, and error messages adds significant overhead. A standard feature for this would greatly enhance monitoring and troubleshooting capabilities for integrations in D365 F&O.

Category:

It would be highly beneficial to have the ability to select and settle transactions across all related customers at the time of payment. This enhancement would significantly streamline payment processing and settlement for organizations managing parent-child customer structures. Please consider this feature for future updates!

Category:

Sales order workflow would be incredibly useful

Category:

Our idea is to add a validation (feedback) log when a view/workspace has been pushed to (multiple) users.

Category:

I completely agree! Controlling modes of delivery by customer, address, or hierarchy is essential for B2B eCommerce. It aligns with customer-specific logistics needs, reduces confusion, and streamlines the ordering process. Showing only agreed delivery modes and enabling selection for new addresses would greatly enhance usability. This is a valuable improvement for the roadmap!

Category:

There is alittle bit of a "Feature" in the functionality.When a Gift card is sold in Shopify on its own sales order, the order never makes it into BC because it is instantly fulfilled. Therefore the Sale of the gift card is never recorded or posted to the liability account for gift cards. Therefore when the reconciliation is done against the resulting sale there is nothing to balance this up against.

Category:

The performance of looping through the table "Table Relations Metadata" must be improved too.https://www.yammer.com/dynamicsnavdev/threads/3083002047127552

Category:

Good idea!

Category:

Please disregard

Category:

This is a large issue within our company and we use a 4-4-5 fiscal calendar too. Our work around is to use the 15th of each month as that always falls within the proper fiscal period for us.But that requires our team only using the batch posting and hanging the posting date for every single leasing batch posting. It is quite easy to miss and then requires rework to correct. This causes other troubles: validating the leasing schedules requires transforming to the right fiscal period as well. The Short-term/long-term journals must be manually updated with the right date after entry.

Category:

  • 1
  • 486
  • 487
  • 488
  • 489
  • 490
  • 491
  • 492
  • 493
  • 494
  • 500