0
Category:
STATUS DETAILS

Comments

Anyway, until Version: AU Business Central 22.1 (Platform 22.0.57436.0 + Application 22.1.55890.56216), the bug is not solved yet.

Category:

Alternatively, please support exporting to data lake in Parquet file format. Most 3rd party replication services infer name and data type from the data file and do not leverage the associated jscon schema file. This is causing them to create fields with incorrect names and data types.

Category:

That is so true. The same goes for SharePoint as well.

Category:

This should absolutely be a feature of Business Central, as it is in Finance and Supply Chain. It is a bit frustrating to think that a customer will use stockkeeping units exactly as intended and there is no way to possibly run an independent cost roll for the variant, or produce the variant at it's own standard cost that does match the item. This also applies to other cost environments besides standard. For example, in a FIFO environment the variant should be creating it's own item ledger entries and having it's own cost capitalized and expensed out correctly, rather than blending item ledger entries and cost for all variants of an item.

Category:

TRUTH!

Category:

Our Event Managers are very much interested or in other words they desperately need this so that they can report event stats to their leaders.

Category:

This is the first comment from every client, when I demo a list page in F&O. Most items have multiple units setup and it is not clear which is being used on a form or report. This is a common enhancement we make to the system.

Category:

We have this issue as well with several clients. Another common example is pack size conversions. Let's say you have a primary item in the plan group that is called out on the formula in eaches and the alternate item's base inventory unit is eaches. The pack sizes of the two items differ and we twice as much of the secondary item as the first. MRP will short the planned production order by half of what's needed for the alternate item.

Category:

This is a mandatory functional requirement in companies that have used palletizing in the production or purchase of goods. It took more than 2 months to develop the functionality, and the customer is dissatisfied with the fact that he paid extra for the the basic functionality that was not in the system standard.

Category:

Has there been any information about when this might be implemented?

Category:

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