In a trade environment, our customers often have multiple locations, buildings, project sites, configurations, installations etc. which are used somewhere in the business process. A contractor in building and construction industry requires that goods are shipped to the building site or project location, and invoices are split per specific building site or project.
In standard there is no existing entity which can be linked to specific sales orders or quotations or connect specific documents to it or use them for the setup of specific price and discount agreements via customer object specific trade agreements or retail affiliations.
Customer Sites enables the specification of multiple objects per customer, and use these objects in various transactions and documents.
Note
Sales and marketing > Customer object > All customer objects
Customer objects are all customer related specific sites (locations, projects etc). A customer object is always connected to a specific customer. Customer objects can be used in sales orders and sales quotations, which make it possible to trace back all related transactions.
Sales and marketing > Customer object > All customer objects > Tab: Customer object
When a new customer object is created, a relation with a party ID must be specified.
Per customer object one or more additional business relations can be registered. Also other relations and documents for that specific customer object can be connected. With the field Relation type, it is possible to indicate what kind of role this relation has in relation to the customer object.
E.g. a relation can have the role of an architect in relation to this customer object, but he can have a completely different role (e.g. advisor) in relation to another object. The relation selected on creation of the object is marked as Primary.
When the business relation is connected to the customer object during creation, a new address record is created and the address values (street, county, country) of the primary address of the business relation is copied and used as customer object address, with purpose "Business". The address book of the customer is inherited to the customer object. The idea is that you manually create a delivery address for this specific customer object as the goods often needs to be shipped to that address instead of the customers default address.
Besides the information on the customer object, it is possible to record all relations that play, or have played an active role at the customer object. It is also possible to connect all active contacts. On the Related information on the right pane, the roles to which a customer object is attached can be viewed.
It is possible to create a parent-child relation between customer objects. This hierarchy is shown as a tree structure in the first fast tab.
When the Enable Customer object pricing parameter is enabled it will be possible to use the Customer object within sales and purchase trade agreements. The menu items to access these trade agreements will appear on the purchase tab of the customer object.
And when the parameter Enable Default find next is enabled the field Find next on the customer object can be used to control the default value of find next in the trade agreements when a customer object is selected.
Sales and marketing > Customer object > All customer objects > Tab: Sell
From the customer object, it is possible to create:
Also the information related to the customer object is visible:
Sales and marketing > Customer object > All customer objects > Tab: Purchase
From the customer object, it is possible to go to all the purchase orders of this object.
When a relation is added to the object and the relation has the role of vendor within the company, the menu item Create purchase order becomes active and creates a purchase order for this object and vendor.
When a purchase order is created from a sales order the customer object will be transferred to the purchase order header.
Sales and marketing > Relationships > Opportunities > All opportunities
When selecting a source type Customer object and a customer object ID on an opportunity, the addresses of the customer object are linked to the opportunity (upon save). When the link with between the opportunity and the customer object is removed, the addresses of the (relation) name are shown again.
On a lead you can also link the customer object, but in this case no addresses are linked or inherited, like it does not do for customers either.
Common > Common > Global address book
A customer object is also created as a party in the global address book and it gets the role Customer object. This enables you also to filter on the role customer object in the grid of the global address book.
Sales and marketing > Customers > All customers > Fast tab: Sales order defaults
Often there is an agreement with customers that all invoicing must be project specific. Non-specific invoices will not be paid. On the customer form the checkmark “Customer object is mandatory” controls whether you have to select a customer object during order creation:
When set to yes, the user must select a customer object on creation of a sales order.
Retail > Customers > Affiliations
Sales and marketing > Customers > All customers > Tab: Retail > Button: Affiliations
Within the retail module of standard Microsoft Dynamics 365 for Finance and Operations affiliations are used to apply retail prices and discounts on a retail sales order (both on Pos and call center orders). Affiliations are inherited form a customer to the sales order and can be manually overridden.
To make it possible to setup customer object specific retail prices and discounts our solution supports the setup of affiliations on a customer object.
When a customer object is added to the call center sales order, the affiliations of the customer object are inherited to the sales order and combined with the affiliations set on the customer.
When the parameter “Ignore customer affiliations” on the customer object is enabled, the affiliations of the customer are not applied on the order when a customer object is added to the sales order. When the object is removed from the order the affiliations of the customer are added.
Retail > Customers > Customer service
Via de button All customer objects on the tab Customer, the customer objects for the selected customer (primairy or related) will be shown.
Accounts receivable > Setup > Accounts receivable parameters
Field | Description |
Initialize delivery address from customer object | When set to Yes, the Delivery address will be inherited from the selected Customer object to the order. |
Extended contact lookup |
When set to Yes, additional filters are available on the lookup field Contact for delivery. The additional filters are:
|
Sales and marketing > Setup > Distribution > Terms of delivery
If the "Terms of the delivery" specify that "Sales tax address" is “Delivery”. The standard Microsoft Dynamics 365 for Finance and Operations functionality will inherit the sales tax from the delivery address.
Sales and marketing > Setup > Sales management > Source types
In sales and marketing, Sources types are used for Leads and opportunities. When opening of the Source Types form, the system-defined sources types will be generated automatically. The user can add manual source types.
Customer object is a system generated source type, which enables you to link a customer object to a lead or an opportunity.
Question: | Why does the message 'RegisterOverrideMethod was called twice for the same object for method ‘lookup’. mean? |
Answer: | As part of the Delivery contact feature an extended contact lookup parameter is introduced. In the lookup of the Contact for delivery field additional filters have been added by using an RegisterOverrideMethod. The disadvantage of this method is, that it can only be used by one solution in the system. If another solution uses the same method, the following error message will be shown: RegisterOverrideMethod was called twice for the same object for method ‘lookup’. You can only override a method once per instance. |
Feature | Introduced in version |
---|---|
|
10041.24082800 |
Feature | Introduced in version |
---|---|
|
10040.24052300 |
Feature | Introduced in version |
---|---|
|
10038.62.810 |
Feature | Introduced in version |
---|---|
|
10036.60.100 |
Feature | Introduced in version |
---|---|
|
10034.58.723 |
Feature | Introduced in version |
---|---|
|
10032.56.722 |
Feature | Introduced in version |
---|---|
|
10030.54.721 |
Feature | Introduced in version |
---|---|
|
10029.53.304 |
Feature | Introduced in version |
---|---|
|
10029.53.720 |
Feature | Introduced in version |
---|---|
|
10028.52.710 |
Feature | Introduced in version |
---|---|
|
10017.41.701 |
Feature | Introduced in version |
---|---|
|
10017.41.700 |
Feature | Introduced in version |
---|---|
|
10014.38.622 |
Feature | Introduced in version |
---|---|
|
1010.34.621 |
Feature | Introduced in version |
---|---|
|
1007.31.620 |
Feature | Introduced in version |
---|---|
|
1002.26.200 DYSRetail |
Feature | Introduced in version |
---|---|
|
1002.26.600 |
Feature | Introduced in version |
---|---|
|
1000.24.500 |
Feature | Introduced in version |
---|---|
|
DYSRetail 8.120.100 |
Feature | Introduced in version |
---|---|
|
PBP 8.120.800 |
Feature | Introduced in version |
---|---|
|
8.120.400 |
Feature | Introduced in version |
---|---|
|
8.015.300 |
Feature | Introduced in version |
---|---|
|
7.312.200 |
Feature | Introduced in version |
---|---|
|
720.780.101 |
Feature | Introduced in version |
---|---|
|
710.730.100 |