Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes! Register now.

Reply
cheid_4838
Helper IV
Helper IV

Export Underlying Data is not exporting all columns

I have a matrix visual (below) that is summarizing purchase orders by driver manager.  When I or anyone else goes to export underlying data within the workspace app all the fields show up, but the PO Amount which is in the same table as PO Qty and Rate.  Why would one field not show up in the underlying data, but others from the same table do?  I have never encountered something like this before.   I have one relationship that is many to many, but the other two are many to one.  Could that be causing the issue? Thanks.

 

cheid_4838_1-1756913012436.png

 

1 ACCEPTED SOLUTION
anilgavhane
Resolver III
Resolver III

@cheid_4838  Possbile reasons
: Column Is Hidden in the Data Model

  • If PO Amount is marked as hidden in the model (even if used in visuals), it won’t show up in the export.
  • Fix: Open Power BI Desktop → Model view → Check if PO Amount is hidden. If so, unhide it.

2. Column Is a Measure, Not a Raw Field

  • If PO Amount is a DAX measure rather than a column, it won’t appear in the “underlying data” export—only in “summarized data.”
  • Fix: Use “Export summarized data” instead, or create a calculated column if appropriate.

3. Data Type Limitations

  • Power BI sometimes excludes non-text columns from underlying data exports unless they’re directly used in the visual.
  • Fix: Try converting PO Amount to text (if feasible) or ensure it’s explicitly referenced in the visual.

4. Many-to-Many Relationship Complexity

  • Many-to-many relationships can cause ambiguous filter contexts, which may lead Power BI to exclude certain fields during export.
  • Fix: Try simplifying the relationship or use DAX to clarify the context (e.g., TREATAS, USERELATIONSHIP).

5. Field Not Directly Used in the Visual

  • Only fields used in the visual or directly related to it are included in the export.
  • Fix: Add PO Amount to the matrix—even if hidden visually—to force inclusion.

View solution in original post

4 REPLIES 4
v-lgarikapat
Community Support
Community Support

Hi @cheid_4838 ,

Thanks for reaching out to the Microsoft fabric community forum.

@Shahid12523 , @anilgavhane , 

Thanks for your prompt response

@cheid_4838 

I wanted to follow up and confirm whether you’ve had the opportunity to review the information provided by  @Shahid12523 , @anilgavhane  If you have any questions or need further clarification, please don’t hesitate to reach out.

 

We truly appreciate your continued engagement and thank you for being an active and valued member of the community.

If you're still experiencing any challenges, please don’t hesitate to reach out  we’d be more than happy to assist you further.

 

We look forward to hearing from you.

 

Best regards,
Lakshmi

Hi @cheid_4838 ,

 

We’d like to confirm whether your issue has been successfully resolved. If you still have any questions or need further assistance, please don’t hesitate to reach out. We’re more than happy to continue supporting you.

We appreciate your engagement and thank you for being an active part of the community.


Best Regards,
Lakshmi.

Shahid12523
Community Champion
Community Champion

PO Amount likely isn’t exporting because it’s a DAX measure, not a raw column. Power BI only exports fields directly used in the visual and skips calculated measures unless explicitly included. Also check if it’s hidden in the model, or affected by many-to-many relationships.


Fixes:
- Add PO Amount directly to the visual.
- Use a table visual to test export.
- Ensure it’s not hidden in the model.

Shahed Shaikh
anilgavhane
Resolver III
Resolver III

@cheid_4838  Possbile reasons
: Column Is Hidden in the Data Model

  • If PO Amount is marked as hidden in the model (even if used in visuals), it won’t show up in the export.
  • Fix: Open Power BI Desktop → Model view → Check if PO Amount is hidden. If so, unhide it.

2. Column Is a Measure, Not a Raw Field

  • If PO Amount is a DAX measure rather than a column, it won’t appear in the “underlying data” export—only in “summarized data.”
  • Fix: Use “Export summarized data” instead, or create a calculated column if appropriate.

3. Data Type Limitations

  • Power BI sometimes excludes non-text columns from underlying data exports unless they’re directly used in the visual.
  • Fix: Try converting PO Amount to text (if feasible) or ensure it’s explicitly referenced in the visual.

4. Many-to-Many Relationship Complexity

  • Many-to-many relationships can cause ambiguous filter contexts, which may lead Power BI to exclude certain fields during export.
  • Fix: Try simplifying the relationship or use DAX to clarify the context (e.g., TREATAS, USERELATIONSHIP).

5. Field Not Directly Used in the Visual

  • Only fields used in the visual or directly related to it are included in the export.
  • Fix: Add PO Amount to the matrix—even if hidden visually—to force inclusion.

Helpful resources

Announcements
September Power BI Update Carousel

Power BI Monthly Update - September 2025

Check out the September 2025 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors
Top Kudoed Authors