0
Category:
STATUS DETAILS

Comments

This is one of the most apparent limitations of Business Central at the moment. Please implement hierarchal filtering and reporting.

Category:

we too are facing the same issue. Will need a solution!

Category:

Hi ,Is there any update on the status of your review? Me as an SA had this request on different projects and had to do customisation to accomadate this request. It would be a great addition to have FinDim added to warehouse level and not only have it on Site level.

Category:

We kindly request to add the field of Total amount / Net amount in all purchase order list page as it is too harder to run a mass report that contains all PO details along with purchase order value. This effort will make every D365 clients' life easier.

Category:

totally agree, i was just searching the same, and we have it on incoming and outgoing invoices

Category:

PR Created date (Accounting date) is 10/10/2025. PR approved on 01/01/2206. PO Unbale to cannot convertable, error message is "Purchase requisition line was pre-encumbered in a fiscal year that is different from the accounting date of the purchase order. Hence, purchase order cannot be created." "Purchase order year-end process" Is this kind of process there for PR?

Category:

Not only purchase order line sequencing。 but also production order/Batch order, after we firmed all orders in the day. all orders has no convention or By criterial to assign the number which is definitely a chaos to business users for production. Like we have 100 productions order for 10 products. but for 1 product, it behaved be sequenced one after one in MRP engine. and no Planning Optimization, the numbers jumped to another product without any rule.I guess it's because of Planning Optimization, it used more CPU/memory to get the orders firmed and used non-sequenced numbers..I fully support this.

Category:

Definitely a helpful idea instead of having to create 1 work template and location directive per 'To warehouse' would love to see this implemented.

Category:

Positioned as a marketing and engagement platform, how is it possible that basic polling features aren't available in CI-J? Using the Forms for this purpose is yet another cumbersome layer that immediately reduces participation rates by the extra steps recipients must take to engage.

Category:

Reporting on analytics should be user-friendly, requiring very little manual work. As CI-J is positioned as a marketing platform, it is incomprehensible that this task is so cumbersome.

Category:

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 500