Whenever I try to Run Optimizer from the Server menu, I get this error:
#Tableau Desktop & Web Authoring
That error looks like something worth checking on the Tableau side, especially since it happens directly when launching Run Optimizer. Hopefully one of the replies can identify whether it’s a version issue or a problem with the workbook setup.
Hello,
Our company uses a reporting calendar which starts on different dates each year (although always on a Monday); also, although most years have 52 weeks / 364 days, there are occasionally 53 weeks / 371 days in a year.
In our database, we have two date-related tables, the first one maps each calendar date to a reporting period (day, week, month, quarter, year):
The second one maps each calendar date to the corresponding reporting period's start and end date, including the dates for the year-on-year comparisons:
Combining both tables into one shouldn't be a problem, but once done, I am not sure how to configure the custom calendar in Pulse so that data can be displayed correctly.
The above date logic has already been incorporated into a view for the sales data, however in the Tableau dashboards, I have created custom calculations with parameters in order to show the sales - the problem is this just sets values outside of the reporting period to zero, meaning when I do the same in Pulse, the graph will start from the 1st of January, but the first of January until the start of the reporting year will just be a line with zero data, and then the last 3 or so months of the reporting year will get missed (since they are in the next calendar year).
The main questions are:
1. Does Tableau Pulse support a reporting calendar of varying lengths? When CY is 52 weeks, and LY was 53 weeks, the YoY comparison would be CY 1-52 vs LY 2-53; when CY is 53 weeks, and LY was 52 weeks, the YoY comparison would be CY 1-53 vs LY 1-52 + CY 1 (so week 1 gets double counted). So, it's not always just a simple comparison of Week 1 with Week 1 of prior year.
2. Does Tableau Pulse support reporting calendars which start on different dates each year, e.g. 2026-03-30 vs 2025-03-31?
If yes to both, how do I configure it so Tableau Pulse knows which date ranges to use? The key is that there is always a 364 day difference between CY and LY comparisons.
#Tableau Pulse
@Alex Rogers Pulse can take a custom calendar, including a 53-week one. It will not do that shifting week-1-versus-week-2 comparison by itself.
The calendar has to live in the data source, with the calendar fields in the same table, related to the sales data if they sit apart. Each date needs a day of year, week of year, month of year, and quarter of year. Those numbers start at 1 and step by 1, with no gaps. A week is 7 days. If week 53 is short, week 1 of the next year has to finish that 7-day week. Pulse checks this when you set the calendar on the metric, and it shows the first error it hits.
Fiscal year start on the data source is the simpler case. A Monday that moves every year, plus a mix of 52 and 53 week years, is the custom calendar table, not Fiscal Year Start.
Comparing current weeks 1-52 with last year's weeks 2-53, or double-counting week 1 when the lengths flip, is not a built-in Pulse comparison. Pulse compares periods on the calendar you gave it. If the comparison date is not the same week number last year, put that comparison date on the row. Zeroing out-of-period days is why the line still starts in January.
Hi, @haruto nakamura
It appears that you may have accidentally posted a response intended for a different question. I would appreciate it if you could check and delete it.
What is best way to get the measures sorted how I want them sorted in the Legend?
#Tableau Desktop & Web Authoring
select one of the measures in the legend, then drag & drop in the placement you desire. It's likely as simple as that. See if that works?
Example: I want ms moved up to top:
Obviously these are dimensions, but should work for measures as well.
If this response answered your question, please mark it as an Accepted Answer?
This way, others searching for similar solutions will find the answer faster in the future.
Best, Don Wise (Tableau Ambassador)
Hi! I’m trying to embed a Tableau Cloud dashboard in Salesforce so that users can view the dashboard without having to authenticate separately with Tableau.
From what I understand, using Tableau Embedding + Tableau View requires SSO configuration with a dedicated user account, which I don’t currently have available.
Is there a way to configure authentication using an external application or Tableau Connected App so that users can access the embedded Tableau dashboard without having to reauthenticate with Tableau Cloud?
Any guidance on the recommended approach would be greatly appreciated. Thank you!
#CRM Analytics #Tableau Cloud #Salesforce Admin #Analytics
Diego, that OAuth 2.0 trust connected app is the path I'd point Kathy to for the standard Tableau LWC. Once Tableau Embedding is set up in Salesforce and Enable Single Sign-On is on, the component handles the handshake. She doesn't need a separate token service for that route.
Kathy, the trusted URL and the site ID get the viz onto the page. Each person still needs their own Tableau Cloud user with access to the workbook. The connected app doesn't create those users.
Databases can store datetime in local time or UTC - the designer of the database makes that decision.
Our microsoft sql database stores datetime in UTC. The users want to see datetime in local time. How do i tell tableau that this particular sql server stores datetime in UTC?
Tableau server 2025.3.3
#Tableau Server
you guessed it :)
You can read the related idea and contribute but that doesn't look very good for the roadmap:
https://ideas.salesforce.com/s/idea/a0BHp000016KoeNMAS/timezone-conversion-supportHi, folks.
We've installed Tableau Server 2026.2.2 and properly configured the guest account for one of our sites. We're not able to get a direct URL or the embed code to allow a guest user to access a dashboard without being prompted to authenticate.
Does anyone have a working guest-enabled URL in 2026.2.2 they can share?
Is anyone else having this problem?
Thank you,
Joe
#Tableau Server
if you are good experienced with Guest account approach, meaning add Enabling, then Guest permissions and using the share button to get the link, then it could be a specific bug, though I didn't find anything on the Salesforce Issue Tracker.
I would be you, I would at least look at the Vizportal logs to understand what is happening with the Guest session authentication.
Make also your tests with an Incognito browser window and check also the browser Dev Tools Network traffic related requests / responses.
And worse case open a Tableau Support case.
Published Dashboards currently using the Biztory Dynamic Date Parameter dashboard extension to dynamically set default date parameter values when users open a dashboard in a browser.
During a Tableau Server upgrade to a newer version, what happens to existing dashboard extensions?
Specifically:
Has anyone successfully upgraded Tableau Server while using this extension (or similar dashboard extensions) at scale?
#Salesforce Developer #Reports & Dashboards #Tableau Server #Salesforce Admin
Hi, Dashboard Extension configurations are saved in the workbooks, not directly in Tableau Server. Thus:
Yes, it should be. The Extension's configuration is saved in the workbooks.
2. Are externally hosted extensions automatically preserved, or do they need to be reconfigured/retrusted after the upgrade?
Automatically preserved, the config is saved. If the config is not saved, it would be a Tableau Server error. However, in the worst case, whitelist the extensions is an easy and fast process.
3. Is there any risk that the extension settings could be lost, requiring us to edit and republish all 500+ dashboards to redefine the dynamic default dates?
Probably, the greatest risk is not related with Tableau Server. Maybe the greatest risk is with Biztory stopping the hosting, or Biztory problems with hosting the extension.
4. Are there any recommended validation steps before or after the upgrade for dashboards that use extensions?
As always, when you perform a Tableau Server upgrade the best you can do is to use a blue green upgrade. That way:a. Your current release keeps working
b. You install, restore a backup and test the new Tableau Server exhaustively, and make sure everythings works as expected.
c. If everything is ok, you restore the newest backup from your "old" production environment into the new one, you modify NAT/Network to point to your new install, and you have a really small downtime.
If this post resolves the question, would you be so kind to "Accept this Answer"?. This will help other users find the same answer/resolution and help community keep track of answered questions. Thank you.
Regards,
Diego Martinez
Tableau Visionary and Tableau Ambassador
Hello all,
I have (Recently upgraded the servers to version 2026.2.1) Linux server and using tnsnames.ors files for Oracle DB connections. Also has the 'ojdbc11.jar' driver file placed at /opt/tableau/tableau_driver/jdbc location.
(Note: Other data extracts or refreshes works normally. only issue with this recently created flow which outputs multiple files)
I see one of the prep flows on the server is failing with ERROR: "
Output step error message: [FailedToConnectExternalResourceError] - Unable to connect to DataSource_Name on DataSource_Name. Check that the data source is available, or edit the connection and enter your credentials again
"
When I check connection from the panel 'Test Connection' works and shows successful, but at the runtime this flow fails.
I have tnsfiles.ora with proper DB connection names and have placed the 'oracle.properties' file with the string 'oracle.net.tns_admin=/etc' within at locations:
1. /var/opt/tableau/tableau_server/data/tabsvc/flowminerva/Datasources/oracle.properties
2./var/opt/tableau/tableau_server/data/tabsvc/minerva/Datasources/oracle.properties
3./var/opt/tableau/tableau_server/data/tabsvc/vizqlserver/Datasources/oracle.properties
also, just now added the file at -
4. /var/opt/tableau/tableau_server/data/tabsvc/flowprocessor/Datasources/oracle.properties
Any idea what can I check for?
Thank you!
Hi Vikas,
Test Connection and the flow run are not the same session. Test Connection uses you. A Prep flow on Tableau Server runs with the credentials embedded on the flow, under the server account that executes flows. Other extracts can keep working while this flow doesn't, if this one is the only place those credentials aren't embedded.
The message you pasted is on the output step: unable to connect to that data source. That's the output connection, not automatically the Oracle input. A flow that writes several files has an output connection of its own, and that's the one I'd open first.
On the Oracle side, the process that actually runs the flow has to see the JDBC driver and oracle.properties. Dropping the file under flowprocessor while that process is already up doesn't always get picked up. Restart the flow services after the file is in place, then run this one flow again.
I wouldn't call this a tnsnames problem until the output step still can't connect when you run it as the same account the server uses. I also don't have a published defect for 2026.2.1 that matches this, so I won't invent one.
The summary of my problem is that I am using Measure Names as a filter on multiple sheets and I would like to apply the same filter across the multiple sheets.
As it is known, this option is unavailable for Measure Values.
I do not see pivoting the data as an option, as my measures have varying formats. I also cannot implement a parameter, as I want to be able to select many measures at once. Also, I would like the solution to be adaptable to data and workbook updates if new measures are added.
I am open to additional suggestions and solutions.
I am using Tableau version 2025.3.
#Tableau Desktop & Web Authoring
I can see why the usual workarounds wouldn’t fit here, especially with different measure formats. Being able to apply the same Measure Names filter across selected worksheets would make this much easier to manage. Hopefully there’s a clean solution that doesn’t require changing the underlying data.
