Skip to content
D365 Reference

LogisticsPostalAddress

mainShared across companiesDate-effective

The shared postal address master — one date-effective row per address version; order headers, lines, and invoices reference it by RecId through DeliveryPostalAddress-style fields

Module: Global Address BookNo company partition

Fields

17 fields

KeyFieldEDTDescriptionTypeLengthFlags
RecIdRecIdThe 64-bit surrogate key order headers, lines, invoices, and shipments reference through DeliveryPostalAddress-style fieldsint64
AddressThe full formatted address as a single text blockstring
StreetStreet portion of the addressstring
StreetNumberStreet or house numberstring
BuildingComplimentBuilding, suite, or floor detail supplementing the streetstring
PostBoxPost-office box, when the address is a PO boxstring
CityCity namestring
CountyCounty code within the statestring
StateState or province codestring
ZipCodePostal / ZIP codestring
CountryRegionIdCountry or region code — the only always-populated componentstring10
DistrictNameDistrict name, where the country's address format uses districtsstring
LatitudeLatitude coordinate of the address, when geocodedreal
LongitudeLongitude coordinate of the address, when geocodedreal
LocationRecIdRecId of the parent location in LogisticsLocation that groups this address with its contact infoint64
TimeZoneTime zone assigned to the addressenum
IsPrivateWhether the address is marked private (restricted to the owning party)enum

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading LogisticsPostalAddresson Databricks — enums are decoded, 1900-01-01 dates are wrapped to NULL, and the DataAreaId anchor is in place. Set your Unity Catalog location, company, and filter values below; they’re substituted into the SQL and the copy button.

Query parameters
-- ============================================================
-- Table  : LogisticsPostalAddress The shared postal address master — one date-effective row per address version; order headers, lines, and invoices reference it by RecId through DeliveryPostalAddress-style fields
-- Purpose: Column-selected read of LogisticsPostalAddress — auto-generated from field metadata
-- Grain  : One row per recid (surrogate key)
-- Notes  : Auto-generated skeleton for Synapse Link / Fabric Link-landed F&O data (lowercase column names). Enums decoded inline where verified; datetimes stored in UTC; 1900-01-01 dates are sentinels mapped to NULL. System/audit columns omitted — see the quirks guide.
-- ============================================================
SELECT
  l.recid AS "The 64-bit surrogate key order headers, lines, invoices, and shipments reference through DeliveryPostalAddress-style fields",
  l.address AS "The full formatted address as a single text block",
  l.street AS "Street portion of the address",
  l.streetnumber AS "Street or house number",
  l.buildingcompliment AS "Building, suite, or floor detail supplementing the street",
  l.postbox AS "Post-office box, when the address is a PO box",
  l.city AS "City name",
  l.county AS "County code within the state",
  l.state AS "State or province code",
  l.zipcode AS "Postal / ZIP code",
  l.countryregionid AS "Country or region code — the only always-populated component",
  l.districtname AS "District name, where the country's address format uses districts",
  l.latitude AS "Latitude coordinate of the address, when geocoded",
  l.longitude AS "Longitude coordinate of the address, when geocoded",
  l.location AS "RecId of the parent location in LogisticsLocation that groups this address with its contact info",
  l.timezone AS "Time zone assigned to the address",  -- enum: decode l.timezone via GlobalOptionsetMetadata join — see quirks guide #enums
  l.isprivate AS "Whether the address is marked private (restricted to the owning party)"  -- enum: decode l.isprivate via GlobalOptionsetMetadata join — see quirks guide #enums
FROM <catalog>.<schema>.logisticspostaladdress l
;

2 parameters not filled: <catalog>, <schema>

Relationships

1-hop neighbors — click a table to navigate there. RecId and InventDim edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • SalesTableLogisticsPostalAddressRecId ref · N:1
    ON salestable.deliverypostaladdress = logisticspostaladdress.recid
  • SalesLineLogisticsPostalAddressRecId ref · N:1
    ON salesline.deliverypostaladdress = logisticspostaladdress.recid
  • CustInvoiceJourLogisticsPostalAddressRecId ref · N:1
    ON custinvoicejour.deliverypostaladdress = logisticspostaladdress.recid
  • CustInvoiceJourLogisticsPostalAddressRecId ref · N:1
    ON custinvoicejour.invoicepostaladdress = logisticspostaladdress.recid
  • CustPackingSlipJourLogisticsPostalAddressRecId ref · N:1
    ON custpackingslipjour.deliverypostaladdress = logisticspostaladdress.recid

Data Entities That Expose This Table

No clean standalone address export entity — addresses surface denormalized on customer/vendor entities. Land the raw table to resolve DeliveryPostalAddress / InvoicePostalAddress RecId references.