Dynamics Community Forum Thread Details

Default purpose on Address

Subra is right that you can assign multiple purposes to a single address, but the statement that it always requires customization is not fully accurate in D365 Finance & Operations.
There is OOB configuration available that controls how the default address purpose is assigned.
✅ Standard setup option (recommended)
You can influence the defaulting behavior via Address and contact information purpose setup:
Path:
Organization administration → Global address book → Address and contact information purpose setup
What you can do there:

Locate the Purpose (e.g., Invoice, Business, etc.)
Maintain priority/order of purposes
Set Invoice as the highest priority (or default where applicable)
Ensure the Customer party type uses this setup

In many implementations, the system assigns the highest priority purpose as the default when a new address is created, unless overridden by existing role logic.

⚠️ Important limitation

The system still allows Business to be assigned if it is explicitly configured as a default role in your data setup.
Defaulting behavior can vary slightly depending on version and whether dual-write / party model configurations are in place.

🔧 If OOB is not sufficient
If the business requirement is strict (e.g., always force “Invoice” regardless of configuration or user action), then customization is required:

Extend DirPartyLocationRoleService
Or handle address creation via event handlers on party/location role assignment
Override role assignment logic for Customer entity

👍 Recommendation
Start with purpose priority configuration first, because in most cases it solves the issue without customization. Only go to extension if:

multiple purposes conflict
users manually override behavior
strict compliance rule is required

==============================================
In Dynamics 365 Finance & Operations (Party model / Global Address Book), “address purpose” is not stored directly on the customer table. It is part of the party-location role framework.

🔎 Core tables/entities behind Address Purpose

1. LogisticsLocationRole

Table: LogisticsLocationRole
Entity: LogisticsLocationRoleEntity
This is the definition of purposes (roles) like:
- Business
- Invoice
- Delivery
- etc.

👉 This is the master list of “purposes”.

2. DirPartyLocationRole

Table: DirPartyLocationRole
Entity: DirPartyLocationRoleEntity
This is the assignment layer:
- Links Party (Customer/Vendor) + Location (Address) + Role (Purpose)

👉 This is where an address is actually marked as “Invoice” or “Business”.

3. DirPartyLocation

Table: DirPartyLocation
Entity: DirPartyLocationEntity
Links:
- Party ↔ Location

👉 This is the base relationship between customer and address.

4. Supporting table (less direct but important)

LogisticsLocation

Table: LogisticsLocation
Entity: LogisticsLocationEntity
Stores the actual physical address record.

🧠 How it works together (flow)

When you set an address purpose:

Customer (DirPartyTable)
↓
DirPartyLocation (Party ↔ Address link)
↓
DirPartyLocationRole (Purpose assignment)
↓
LogisticsLocationRole (Purpose definition like Invoice/Business)

⚠️ Key takeaway
There is no “default purpose field” on customer address itself.
The “default” behavior you see in UI comes from: