14
We email a Confirmation Order for every sales order by specifying the Send To Email address in the DOCUMENT LAYOUTS for each customer. For most customers, this works exactly as expected and Confirmation Orders go to the address specified.

However, we also have several “child” customer accounts with a separate “parent” Bill-to Customer No. (usually individual stores that belong to a larger chain). These child accounts place their orders with us directly and want to receive their own Confirmation Orders, so we specify the child’s email address in the child’s DOCUMENT LAYOUTS just like we would for a non-child customer record (one that does not have a Bill-to Customer No. specified).

Unfortunately, BC doesn’t look to see if there is a destination specified for the child customer, and instead sends the Confirmation Order to the Send To Email specified in the parent’s DOCUMENT LAYOUTS settings.

It seems to us that BC should look at the child DOCUMENT LAYOUTS first to see if there is a destination specified. If it sees one, it should use that, and if it does not see one, it should look to the parent DOCUMENT LAYOUTS. The existing logic that bypasses the child altogether may be sound for invoices (because the bill should obviously go to the parent), but it doesn’t work for situations like this where the child needs to receive a report that the parent doesn’t.

It also seems to us that our proposed logic – first look at the child record and then at the parent record – would provide the flexibility to accommodate any customer scenario: If the Confirmation Order should go to the child, specify a destination on the child, and if it should go to the parent, specify a destination on the parent but not on the child. Similarly, if an Invoice should go to the parent, specify a destination on the parent and not on the child, and if it should go to the child, specify a destination on the child.

Thank you for your consideration!
STATUS DETAILS
Needs Votes
Ideas Administrator

Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future.

Best regards,
Business Central Team