web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

D365FO Power BI error: 'DELIVERYPOSTALADDRESS' column invalid but exists in AM

(4) ShareShare
ReportReport
Posted on by 11
Underlying Error: QueryUserError
Activity ID: fff19193-d9cf-40bd-8d20-5c9ef8010e49
Correlation ID: 277c0830-e1d7-50d7-148d-9c6588feace1
Request ID: 27185444-44ec-41ad-828e-128d5807a90f
Time: Mon Aug 25 2025 08:47:26 GMT+0000
Service version: 13.0.26507.41
Client version: 2508.2.25475-train
Cluster URI: https://WABI-WEST-EUROPE-E-PRIMARY-redirect.analysis.windows.net
Error fetching data for this visual
Invalid column name 'DELIVERYPOSTALADDRESS'. The exception was raised by the IDbCommand interface.
 
 
What’s happening:

A field named "DeliveryPostalAddress" is present in my Aggregate Measurement and exposed to the report, but at runtime the visual fails with Invalid column name.
 

Repro (short):

 

  1. Add DeliveryPostalAddress to AM → Build + DB Sync.

  2. Full Entity store refresh.

  3. Publish/Refresh Power BI dataset.

  4. Open visual → error above.

 

What I checked/tried:

  • Full build + DB sync after adding the field.

  • Full Entity store refresh (not incremental).

  • Re-publish the PBIX / refresh dataset in Service.

  • Field appears in AM designer and in the model.

  • Still get Invalid column name 'DELIVERYPOSTALADDRESS'.


  •  
Question:

Where can this mismatch come from? The AM/perspective show the field, but AxDW seems to lack the physical column at query time. Is there a known gap with address joins (DELIVERYPOSTALADDRESS/LOGISTICSPOSTALADDRESS) or an extra step to force the column into AxDW?
Categories:
I have the same question (0)
  • Suggested answer
    Ramesh Kumar Profile Picture
    7,527 Super User 2025 Season 2 on at
    our Power BI visual is hitting AxDW (Entity store) and the SQL view it queries does not have a column called DELIVERYPOSTALADDRESS, even though your Aggregate Measurement (AM) metadata shows it. That mismatch usually happens when the field was added to the AM but not actually materialized into the underlying aggregate view that gets published to AxDW, or when the field is a display/computed X++ method that doesn’t translate to SQL.
     
    Thanks
    Ramesh
     
    If this was helpful, please check the "Does this answer your question?" box and mark it as verified.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 660 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 549 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 307 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans