on
RE:
I agree this is needed and should be treated as a bug because the behavior is different between Adjust out and Adjust In.Last year, I even created a case (2405240010000218) to call out this issue. Below is the response I received from the product group:Thank you for bringing this to our attention. We understand how frustrating it can be when something doesn’t work the way you expect it to. Upon further investigation, we have determined that while this is a bug, it doesn’t meet the level required for us to fix at this time. We evaluate this based on factors such as the impact to the overall business process, or the availability of a valid workaround.
RE:
An alternate approach would be to default the qty to assemble to the quantity ordered creating demand for all the components, printing the pick ticket and the user would update the qty to ship based on what was picked. For warehouse management, default the qty to assemble to the quantity ordered and when the warehouse pick is created to create the pick for the components to build full assemblies. Currently, the pick may suggest to pick only 1 of two components or pick an insufficient qty of one component while suggesting to pick the full quantity of another. Thus, one can end up with partially built assemblies. The printed warehouse pick should also list the item being made and its description rather than just the components.
RE:
in BC 25 it is possible to filter on a flowfield, however, searching is still not working.
RE:
It is unfortunate that this idea is marked as "completed", as it is only partially implemented. While project details (project number, task number, planning line) can be added to PO lines, this is not enough to create a strong link between projects and POs.If project details are on PO lines, purchased items are posted directly as project costs. However, if purchases need to be posted to a balance account first, the project details must be removed, causing the PO to lose its connection to the project it came from. This makes it hard for Procurement to get an overview of which projects their POs relate to.Adding the project number in the PO header would improve visibility and enable functionality like setting an approver based on the project (often the Project Manager).Also, the requisition worksheet is a great tool for handling overall project demand instead of purchasing per project, but when using it, the project-PO link is lost entirely.In summary, while some progress has been made, there is still no solid link between projects and POs in Business Central. This impacts visibility, reporting, and approval workflows. A better integration is needed to fully solve this issue.
RE:
SYSOUTGOINGEMAILDATA is in the TOP5 of largest table in FnO. Time for Clean up !
RE:
This functionality is an essential requirement, as without it, the accrual calculations will not yield accurate results. It is critical that the accrual process accounts for various scenarios, such as changes to the working calendar mid-period and the calculation of arrears, to ensure precision and compliance with countries / states / organization policies/legislations.
RE:
I would like to emphasize that this can be accomplished through warehouse app, but cannot be done through browser ("Transfer" journal or any other form)
RE:
Yes please :-)
RE:
This would be extremely helpful. This is a huge problem, when you are unable to split the order or quotation. We have this regularly because the customer wants one construction site in one quotation / order.
RE:
We need this ASAP! Some of our customers deppend on this feature to keep core functionalities and integrations and without it they need to stay On-Prem instead of embracing the future.