#Reports & Dashboards토론 중인 항목 99개

Hi everyone,

I would appreciate some architectural guidance on a Salesforce security requirement.

We need to restrict Sales users from exporting or extracting company-wide financial/reporting data, while they must continue using Salesforce normally, including the Salesforce Mobile App.

Our initial approach was to remove the API Enabled

permission from their corresponding Permission Set Group to prevent API-based extraction tools such as Data Loader or spreadsheet connectors. 

Howeever, I would like to confirm with you, if API Enabled is also required for the Salesforce Mobile App, which Sales users need to use.

Therefore, my questions are:

1. Is removing API Enabled an appropriate approach for preventing data extraction in this scenario, or would this have unintended consequences beyond the intended restriction?
2. What would be the recommended Salesforce architecture to restrict API-based data extraction for Inside Sales while keeping access to the Salesforce Mobile App?
3. Would API Access Control / Connected App allowlisting be a better approach, for example allowing Salesforce Mobile while restricting other API clients?
4. Are there other Salesforce permissions or security controls that should be considered specifically for preventing report/data export without disabling API access entirely?

The business requirement is specifically to restrict data extraction

, not to prevent Sales users from using Salesforce Mobile or other approved Salesforce functionality. 

The focus is on:

• Reports: No creating, editing, cloning, or exporting.
• Dashboards: No access to restricted Turnover dashboards.
• Subscriptions: Prevent receiving Reports/Dashboards via email.
• List Views: Prevent export/print as an extraction method.
• Folder Sharing: Prevent indirect access to restricted Reports/Dashboards.

Any guidance or documentation from Salesforce would be greatly appreciated. 

Hi everyone,

I need some architectural advice on the best way to handle report and data access for a global team without turning role management into a maintenance nightmare.

• We have report folders separated by countries: Country A Reports, Country B Reports, and Country C Reports.
• In our Role Hierarchy, we have local roles at the bottom (e.g., Sales Rep Country A, Sales Rep Country B) and a high-level corporate role at the top called Global Management.

The Business Requirement:

Product manager users in their Country or Regional Level role complained not being able to access reports with data related to other countries, so we moved them to the

. They require full visibility to access records (Accounts, Opportunities) globally, but they also need to open and view the reports inside the local folders of Country A, Country B, and Country C. 

The challenge:

We noticed that when we move a user from a local country role up to the

role to give them global record visibility, they immediately lose access to some of the regional reports they could see before, or the reports show up completely empty for them. 

My Questions:

1. How can we avoid constantly shifting users from one role to another just so they can see cross-country reports while maintaining access to their respective records? What is the cleanest architecture to decouple record visibility from report folder visibility?
2. What is the Best Practice in Salesforce to solve this? Should we keep these global users in a specific role and grant them report folder access via a Public Group or a specific Permission Set?
3. Why do some reports return empty or give errors to a user right after they are moved to a higher role in the hierarchy? Is it because of dynamic filters in the reports (like "My Team's Records" or "My Role" filters) that break when their branch changes?

Thank you so much for your help! 

APAC Command Centre — a business performance dashboard with drill-down views across Product Performance, Customer Cost/Value, and Operations & Shipping, tracking gross profit, margin, and return rate trends.

Spotify Analysis — an end-to-end music streaming analytics build. Raw data cleaned and joined in Alteryx (900K+ play events, dedup, date/boolean standardization, a custom macro), visualized across an Executive Overview and Content Performance dashboard with parameter-driven Top-N views and a custom dark theme.

Would appreciate feedback on:

• Visual design — readability, contrast, anything that feels off
• Chart choices — anywhere you'd have visualized something differently
• Navigation/drill-down flow — intuitive, or confusing anywhere?
• Anything that reads as unfinished — direct critique welcome

Links below — thanks to anyone who takes a look! 

APAC Command Centre -

Spotify Analysis -

Bug: Radial/Sankey chart in Show Me corrupts workbook (Error D2E8DA72) even after Undo

Summary: 

Clicking on the Radial or Sankey chart type in the "Show Me" panel — even briefly, and even if immediately undone — permanently corrupts the workbook file. Saving and reopening the file afterward fails with Error Code D2E8DA72. 

Environment: 

- Tableau Desktop, Professional Edition 

- Version 2026.2.0 (20262.26.0603.1643) 

- Windows 

Steps to Reproduce: 

1. Open any workbook (new or existing) in Tableau Desktop 2026.2.0 

2. Select a worksheet and open the "Show Me" panel 

3. Click on the Radial (or Sankey) chart type once 

4. Immediately press Ctrl+Z (Undo) 

5. Save the workbook as a packaged .twbx file 

6. Close Tableau Desktop 

7. Reopen the same .twbx file 

Expected Result: 

The workbook should open normally, since the chart type was undone and never appears on any sheet. 

Actual Result: 

Tableau fails to load the workbook with the following error: 

Error Code: D2E8DA72 

Error: no declaration found for element 'worksheet-extension' 

Error: attribute 'extension-version' is not declared for element 'worksheet-extension' 

Error: attribute 'id' is not declared for element 'worksheet-extension' 

Error: element 'worksheet-extension' is not allowed for content model '(document-format-change-manifest,(dashboard-extension),resources?)' 

Root Cause (as far as I can diagnose): 

Even though the chart action is undone and never persists visibly in the workbook, Tableau still writes a <referenced-extensions> manifest block into the underlying .twb XML the moment the chart type is clicked. This manifest references the built-in extension (e.g. com.tableau.extension.radial) but appears to be incompatible with the workbook's own internal file-format version, causing Tableau's own XML validator to reject the file on the next load. This happens even in a workbook that never uses the chart on any actual sheet. 

Workaround (manual): 

1. Rename the .twbx file to .zip 

2. Extract the zip 

3. Open the .twb file in a text editor 

4. Search for "referenced-extensions" 

5. Delete the entire block from <referenced-extensions> to </referenced-extensions> 

6. Save the .twb file 

7. Re-zip the .twb file along with the Data folder 

8. Rename the new zip back to .twbx 

The file then opens normally with no loss of dashboard content. 

Impact: 

This is a significant reliability risk since: 

- It occurs with no warning at the time the chart is clicked or undone 

- It can silently corrupt a file that appears completely fine until the next reopen 

- It could affect students/professionals submitting workbooks for grading or review, since a file that worked when last saved may fail to open for the recipient 

I'm happy to share the exact corrupted and fixed .twb/.twbx files if useful for reproducing or debugging this on your end.