Comments
Greatly disagree. Currently, (BC 18.2) if you have PARENT / CHILD setup (Bill-To / Sell-To) the options on the PARENT customer account prevail and the CHILD settings are ignored. This is so even if the PARENT email is blank.
Same occurs if you try using the doc layout settings - PARENT email setting prevails over CHILD.
This means indicated a base logic that a PARENT only ever has one child. So that is useless if the PARENT has a chain of stores/kitchens etc etc - with each child location wanting copies of documents so they can track inventory & costs - but parent head office paying all bills.
We have the same problem with our clients.
It seems that the default logic is that if you have the BILL-TO customer activated for a child, BC assumes parent email settings prevail. This even extends if the email settings on the PARENT are blank - the email tries to send to a blank address.
It also makes no difference if you use document layouts on the CHILD to try and override - the PARENT email settings prevails.
That logic is flawed because it assumes a 1-to-1 relationship of parent to child. This doesnt for customers with several locations - eg customer chain - where CHILD needs a copy of documents, but the PARENT pays the invoice & needs a combined statement.
Ultimately - you should be able to nominate for each document type - whether to use the PARENT or CHILD email settings.
We get this question very often and we are located in Canada. We have clients where they want to issue multiple prepayment invoices on a Sales Order. The first prepayment could be for 5%, then 10%, etc. It would solve the issue of having to create a manual Sales Invoice for each prepayment and then deducting the prepayment invoices manually from the sales order.
This is becoming a very common request. When there is a PO for non-inventory Items, you would expect the costs to be accrued when the PO is received and not invoiced (i.e. DR. Expense CR. Accrual). However, for non-inventory Items, when the PO is just received it doesn't post anything in Business Central. This isn't accurate because there could be subcontractors that have performed the work but the final invoice has not been sent yet (hence accruals). It's a manual process to figure out which PO lines has non-inventory items at month end that has been received and not invoiced and ask users to book a journal entry to accrue for the amounts. If this can be done for inventory items why can't it be done for non-inventory items?
This functionality was part of a code package that Microsoft purchased from Blue Horseshoe a few years back and was included in the rollout schedule. Not sure why it was removed, but as it was an add on ISV that many customers had up until it was sold, many clients upgrading from 2012 R3 used this functionality and are now having issues getting onto D365 as it is not yet available. Is there a timeframe on when this will be back in the release schedule?
An issue we have observed is the app using online data even when the data bandwidth available is exceptionaly low, but offline data is available. If offline data is available then in my opinion it should be used to keep response speeds high for users regardless of data bandwidth available at that moment.