#Tableau Desktop & Web Authoring193 人正在讨论

Hello everyone, 

I searched the community first, but I could not find a matching thread. I would appreciate any guidance. 

When I publish a workbook from Tableau Desktop to Tableau Cloud on my Mac, Tableau Desktop closes immediately. There is no error dialog. The same Tableau Cloud site works when publishing from another computer. 

- Apple MacBook Pro, Apple M5 Max 

- macOS 26.5.2 

- Tableau Desktop (Apple silicon) 

- Versions checked: 2025.3, 2026.1, 2026.2, 2026.2.1 

- Same behavior on all of these versions 

1. Open a workbook in Tableau Desktop 

2. Sign in to Tableau Cloud successfully 

3. Choose Publish Workbook 

4. Tableau Desktop closes right away with no message 

5. A diagnostic report file (.dmp) is created 

- Memory access exception 

- Signal 10 (SIGBUS) 

- Example product build: 20262.26.0708.1337 

- Architecture: arm64 

- Example correlation id: 099AF1D8AFE440838F45AF86D5D2F0DE 

- Cloud sign-in completes 

- The app stops before a publish-workbook command is written 

- There is no normal close-log entry 

From the related protocol service log 

- AdminTask pipe closed, exiting 

1. Checked multiple Desktop versions listed above 

2. Tried a Redshift workbook 

3. Tried a text-file-only workbook 

4. Confirmed publishing works from another PC with the same Cloud site 

5. On this Mac, Publish Data Source as extract can succeed 

6. On this Mac, Publish Data Source with a live connection also closes unexpectedly 

7. Collected diagnostic report files and matching logs 

1. Has anyone seen Publish Workbook close unexpectedly on Apple silicon / recent macOS? 

2. Which files are most useful to share for review? 

3. Is there a temporary workaround for Publish Workbook? 

Thank you very much for any help. 

Hi!,

I'm trying to build a Current vs. Prior variance table in Tableau, but I'm struggling with the setup of the Current and Prior columns. The packaged workbook is attached. 

Users can select one or more Current Terms (example: 202611, 202615), and I have a mapping file that determines the corresponding Prior Terms

(Term - 100). 

My mapping table contains:

• Current Term
• Prior Term

I'm unsure of the best approach to structure the calculations so that Tableau returns:

• Current Value
• Prior Value
• Variance
• % Variance 
  I first tried using calculations like:

{ FIXED [Term]-100, [Metric], [Group], [Type] :
    SUM([Value])
}

but since Term is a string and users can select multiple terms, this approach became difficult to maintain. 

I also experimented with creating Current and Prior calculated fields and using FIXED LOD expressions, but either:

• • Prior returned the same value as Current,
  • Prior returned NULL,
  • or the calculations stopped working when multiple current terms were selected.
• #Tableau Desktop & Web Authoring

Hi Team, 

Requirement: Display data dynamically based on the selected Period Type parameter

• Day
  • When the user selects Day in the Period Type parameter, the Order Date parameter should display all available dates.
  • The most recent available date should be selected by default.
• Week
  • When the user selects Week, the Order Date parameter should display only the Monday date of each available week (e.g., 27-Jul-2026, 20-Jul-2026, 13-Jul-2026).
  • Upon selecting a week, the report should display data for the entire Monday-to-Sunday period corresponding to that week.
• Month
  • When the user selects Month, the Order Date parameter should display all available months.
  • The latest available month (e.g., Jul-2026) should be selected by default.
• Quarter
  • When the user selects Quarter, the Order Date parameter should display all available quarters.
  • The latest available quarter (e.g., 2026-Q3) should be selected by default.
• Custom Dates
  • When the user selects Custom Dates, the following parameters should be displayed: 
    • Start Date
    • End Date
  • Report data should be filtered based on the chosen date range.
• Lifetime
  • When the user selects Lifetime, all available data should be displayed without applying any date filters.
• #Tableau Agent

#Tableau Desktop & Web Authoring  #Tableau Server  #Tableau Cloud  #Tableau Public  #Tableau  #Tableau Prep  #Tableau Community Updates

Hi all,

I'm in the process of setting up a custom financial calendar for use in Tableau Pulse and running into a specific issue when trying to apply it to a metric.

I’ve built a calendar table that follows Tableau’s documented requirements for Pulse custom calendars. The financial year starts on 1 March, and the table includes all required fields: "Reference date", "Day of year", "Week of year", "Month of year", "Month name", "Quarter", and "Year". The calendar spans from March 2021 through February 2025, with every single day represented and no missing values. All fields are within the same table.

I’m using the Sample Superstore dataset to test this. I’ve created a relationship between "Reference date" in the calendar and "Order Date" in the Superstore data.

In the Pulse metric builder, the custom calendar fields appear correctly, and I’m able to select them when setting the calendar for the metric. However, when I click "Apply", I get a 400 Bad Request error. The configuration fails at that point and the calendar isn’t applied.

Despite this failure, I can still proceed to build the metric — but only by continuing without the custom calendar. This highlights that the calendar itself is the issue, not the metric logic or data structure. Pulse allows the metric to be built, but not with the custom calendar attached.

I’ve double-checked that:

• All required fields are present and properly typed
• Every day is included across all years, with no gaps or duplicates
• No filters are applied to the calendar table
• The relationship between calendar and fact data is recognised and working in Tableau Desktop

If anyone has successfully applied a custom calendar in Tableau Pulse without encountering this issue, I’d really appreciate hearing how that was achieved.

I'm encountering a few issues with the keyboard accessibility of my Tableau dashboards: 

Tab-order issues:

1. Articles (like this one) that describe how to change the tab order of dashboard objects usually suggest assigning a very high tab order number to 'ornamental' dashboard objects that shouldn't ever receive focus. However, I've found that those objects simply end up receiving the focus after the higher priority objects do, so eventually the user will be focused on some object that's supposed to just be ornamental.  How do I take some objects out of the tab order altogether?  What does NOT work: Setting the Zone ID to 0 or a negative number in the XML file causes an error that won't allow the workbook to open in Tableau. Commenting out the zone section related to the object in the XML file removes the object from the dashboard altogether. That commented XML section is also deleted upon saving the workbook, so you'll have to recreate the dashboard item if you want to reinstate it.
2. When clicked, the Download buttons on my dashboards invoke a pop-up window, but do not return the focus to the same button after the pop-up is closed.  How do I ensure that the focus order stays intact after the button is pushed?

Tooltip issues:

1. When keyboard tabs are used to focus on a dashboard element, the tooltip associated with that element isn't triggered. That means that keyboard users lack key information that is available to mouse users. How do I display tooltip content associated with a dashboard element to a keyboard user?
2. When tooltips are triggered, they sometimes obscure other content. Is there a setting that would allow users to close tooltips by pressing the Escape key, for instance?

Page navigation:

1. I found the suggestions in this thread (Pagination of dashboard views) very helpful for implementing paged views in a dashboard. That workaround relies on using shape charts as buttons combined with dashboard actions to navigate through paged content, but I'm not sure that those dashboard actions can be triggered by a keyboard. Is there a setting I should be using that would allow keyboard users to 'Click' an embedded shape chart? Or is an alternative approach to page navigation now available?

 I'd appreciate any insights into how to address these issues. Thanks in advance!