Comments
Not sure what the status is on this from but here are some of my own observations as the planned cross dock partially works as detailed in scenario 1, this should be on the roadmap to fix. Scenario 1. Purchase order is created Sales order created Automatic Released to WH runs (including Planned Cross dock)Load is created and planned crossdocking is created Now a voyage is created for the PO PO invoice postedVoyage line status is GITAt this point you will notice that 2 GIT orders are created, 1 for the planned cross dock amount and 1 for the remaining inventory.Receiving the 2 individual GIT orders results in crossdocking work created as per usual . Scenario 2. Purchase order created Voyage created Sales order created Automatic Release to WH run with cross docking No planned crossdocking created.
Evidently, it is not a programming error. It is a functionality error. BC cannot allow tracking of products by Package No. and not allow recording physical inventories of those same products.Obviously, just by logic, all products of Inventory Type should be inventoriable by all BC enabled procedures. Do we agree?I hope Microsoft will evaluate the problem and resolve this error as soon as possible.
I'm new to Business Central, I was for years involved in other ERP systems. In a world where we talk of usability and user experience of the product all the time, it is strange to see the "tell me" has no intelligence being built in to show a list of search values that users entered before. A very simple list of "last 5 search values" could already do miracles.So I fully agree with this request, which seems not risky and brings added value.
When you use the tell-me function, an empty search widget is shown. It happens quite a lot that you have to re-enter a search value that you already specified before.Just supporting a list of "the last 5 search items" seems a feature with low risk and added value on the usability side of the product.
We need the unload event to make sure that the ProgressIndicator gets closed when the user navigates away. We want to register a postSave handler that opens a ProgressIndicator, do some asynchronuous task, and then close the progress indicator. The above works only when the user selects "Save"the form is autosaved, It does NOT work correctly when the user selects Save & CloseSave & Newthe "The postSave handler doesn't support waiting on a Promise. Hence, the code of the postSave handler will be broken off halfway the async logic. The ProgressIndicator is never closed.If we would have an Unload event handler we could mitigate the above.