Microsoft Dynamics 365
Business Central Team (administrator)
Thanks for the suggestion on more than one email. May I ask why you would need more than one email and is it for the actual contact on the customer/vendor card?
Jodi ChristiansenPM, Microsoft
Add-ons fills this common gab of having different recipients.
There is a need.
I think the easiest and best solution is that: Documents types (like shippig advice, invoice, order confirmation) and "job responsibility" on the contact cards must be linked. this can be defined on customer and shipping adress level. also users must be able to change default contact no for specific document on order level,.
using email adresses (single or multiple) on customer/vendor cards or document layout screen is totally unusable.
This is al little bit difficult.
You may use contacts, but this is half the truth, because the contact who placed the order is often not the one who gets the invoices or warehouse documents. There is also a gap if goods are shipped to different locations.
So the contact who ordered may not see the invoice (depends on company if central accounting gets invoice first or the location where the good arrived). It's als the same on Warehouse documents.
So we would need several e-mails per company (base, accounting, warehouse) by function and also the same in the ship-to adresses, and in also in all document- tables.
The same is also needed in Vendor, "Order- Address" and purchasing documents.
We just ran into this today, we need to be able to setup a email for sales order confirmations and a different email for shipment notifications and a different one for sales invoices. Also it does not appear if a primary contact is set it will use the contact email vs the customer email, or if you change a contact on a sales order the contact email should be the email when you chose to send a document.
Each customer can be linked to contact of type Company, and this company contact can be linked to multiple contacts of type Person. So you already have all needed relations and fields for you purpose, just need to use it.
This is an absolute must: customers want to receive quotes in purchaser roles, packing lists in warehouse and invoices in accounts.
However, for normalization reasons, I'd like to see it related to contacts and their roles, rather than just multiple email fields in the customer table.