Comments
Two main reasons why this is a must:I believe it should be possible for the external warehouse to plan and schedule its transports (load building) & prioritize stock needs. Our customer, wants to reserve its stock as close in time as possible to releasing the load to the warehouse. The main reason for this is that often, inventory adjustment journals are booked in the external warehouse (due to people that are 'shopping' in the warehouse because of urgent item needs) & later on these inventory updates are pushed towards the sales entity. When stock is already reserved in the WOM entity & sales entity, shopping will become impossible, thereby affecting business massively since the most urgent stock needs can only be fulfilled after dereservation of the stock (cumbersome task). In my opinion, reserving stock on the sales order is more dangereous than reserving it on the outbound shipment order since there exist a time delay between the transactions executed in the WOM and updates being pushed to the sales entity. Hence it could be that you reserve stock in the sales entity that is already being 'shopped' in the WOM.
Hi, there is an Aged balance view for customer credit group. Would like to understand a little more in this topic.We have started "Office Hours for AR" recently, would be great if the requestors can join, so that we can take it forward from there. RegardsRussa SahaPM, Credit & CollectionsD365 F&O, Microsoft
We’re experiencing the same issue when sending email from a shared mailbox via the Microsoft 365 (Graph) connector. Emails triggered by a Job Queue are still stored in the Sent Items of the user running the job.Currently, Business Central does not provide a setting to control the saveToSentItems behavior.It would be very helpful to have an option to disable this or ensure emails are only stored in the shared mailbox.
That feature is a must have for my clients.Full LP Picking is not possible if you have locations with more than one LP on it (Bulk Locations).Right now we are helping ourselves with virtual locations to ensure that only 1 LP per Location exists.But there is always the risk to lose LPs during the pick process.
The idea was good. The implementation, unfortunately, was not. Many functions don't look at the inventory data card but always use the bill of materials from the item card. Microsoft needs to improve this and ensure that all calculations that rely on a bill of materials use the correct one for the location.