Dataverse Schema Question

(0) Share

Report

Posted on by crham

342

While working on preparing for data import into Field Service 365 and studying the CDM Schema, I see that:

Accounts table has address fields

Contacts table has address fields

Address table exists and has address fields and relationship with Accounts/Contacts

What is the purpose of this Address table???

I'd prefer all address to be stored in this address table and then reference the account or contact. However I notice that when I create a new Account or Customer, the address information is stored in that table instead. So again what is the purpose of the Address table?

Is it possible to force D365 to only store addresses in the Address table?

All responses (7)

Answers (1)

crham 342 on at

Like (0)

Report

RE: Dataverse Schema Question

I'm open to suggestions as we're in the middle of implementation right now.

My concern with adding Locations in the section you mention is that it cannot be moved to a different account should there be a divorce or home sale.
Gene Glenn 125 on at

Like (0)

Report

RE: Dataverse Schema Question

Seems the Asset and Location is where you would add "House Location" and the Company/Account would have the current information for communication billing.

Likely this is obvious;) Feel free to share your final solution;)
crham 342 on at

Like (0)

Report

RE: Dataverse Schema Question

Thanks.

Our need is that the residence effectively is a functional location for purposes of all work, assets, etc. The Account for that functional location (for communication, billing, etc.) can change (i.e. divorce, homeowners selling to new customer, etc.).
Gene Glenn 125 on at

Like (0)

Report

RE: Dataverse Schema Question

Not sure if this is OOTB, but a change to the Company/account Address (in our Env.) will update all Contact Address, ie Contacts with "Use Company/Account Address =Yes". Not exactly sure on your functional address usage/needs. We use the Company/Account as the "Business/Billing" address which works for a large percentage (is also Business Address) of Companies/Accounts in our D365. If a billing account has a PO Box, then we must set every Contact to "Use Company/Account Address = No", then Contacts have the physical location/address of the business (this is more work), and possibly also another alternate Working from home address. I assume you may need too review Assets and Locations, we have not used this other then "1st" one. Seems you would only use it as needed. Hope that helps.
crham 342 on at

Like (0)

Report

RE: Dataverse Schema Question

Leah your links and info were great, and the perfect response. Thank you.

Gene Thanks for sharing. Haven't even noticed that setting yet. Now I'm going to have to find out what that setting really does do.

Since we work mostly in residential, most of our contacts would have this set to Yes. I'm assuming one feature is that a change to the account would update the contact address.

Would be nice if we could have another question: Is Account Address also the Functional Location? That would save me from having to create hundreds of Functional addresses all that duplicate the Account Address. NOTE: We use Functional Location because the potential for changing of ownership of the residence.
Gene Glenn 125 on at

Like (0)

Report

RE: Dataverse Schema Question

Just a little input on the usage of the Address tables from a "User/Usage" perspective. We typically have the Company/ Account with the proper Address and each Contact set to "Use Company (Account) Address=Yes" in most cases. I believe this is OOTB functionality.

If a Contact has an alternate Address, then the Contact is set to "Use Company (Account) Address=No.

I'm not sure which tables are actually used if set to = Yes vs. No.

.
Verified answer

Community Member Microsoft Employee on at

Like (0)

Report

RE: Dataverse Schema Question

Hi crham,

The Address table is one of those special entities in CRM. It stores address and shipping information for accounts and contacts.

There is logic between the Address table and the address fields that are stored in Contact or Account entity. There is basically a lookup control and address fields in the Account/Contact entity which point to the Address table.

Every time you create a new account or contact, the system creates two address records which are related in a parental relationship with the customer record: One address record containing the information populated in the address1 fields of the customer record, and a second address record containing the information populated in the address2 fields of the customer record. Every time you modify the address within the customer record, it updates the related address record and vice-versa.

Despite the fact that you see both address1 and address2 fields on the contact form the addresses are not actually stored on that entity. All the addresses are stored in the customer address entity. The fields you see on account and contact are really pointers to these records.

You can refer following link for more details about the Address table:

Dynamics CRM: The importance of the Address entity - Pedro Innecco Pedro Innecco

CloudThing | The Problems With Addresses In Microsoft Dynamics 365 - CloudThing