#Tableau Cloud86 discussing

We have a Tableau Cloud instance with users setup to authenticate using "Tableau with MFA".  So far all of the users have been using the Salesforce Authenticator app on their phones to complete the authentication process. 

For the first time we have a user contacting us because they "don't have access to an internet enabled mobile device to complete the authentication".  They are members of an Amish community with tech restrictions. 

Any suggestions on the best path of setting up an alternative method for them to authenticate?  Thanks 

Hello - I am not able to extract refreshes as the Jobs are failing immediately, One program completed success without any errors and rest of the programs are NOT.  It is connecting to the Tableau Bridge but it is failing.  We are live on Tableau Cloud today and none of the data sources are refreshing with the exception of one data source.  All these data sources are connected to Oracle Database.   

I can only do full refresh and no incremental refresh.

I tried looking into the documents couldn't find something easy to understand.

If I extract the data it creates a new .hyper file. Do I upload that. I am confused.

Will it then also refresh the new data which comes in.

Please suggest Thanks

I work for a school district, meaning most of my dashboards are not used throughout the summer. Since tableau automatically suspends any extract refreshes that are not accessed for over 32 days, this means I often get the notification that Tableau wants to stop refreshing my extracts to save resources. I also have several views that we need to look at incredibly frequently, but only seasonally (e.g. I need to be able to check students' test scores daily, but only in the months that they test). 

The reality is that I have no need to refresh these extracts daily year round, but I do need them refreshing daily for the relevant timeframes. Is there a way to schedule extracts so that they refresh daily for some time period (say October thru June, or just the month of January or something), and then stop refreshing until the the same time next year? 

I am a super beginner with Tableau, and we just implemented it into our Salesforce org. I am trying to connect the object FiscalYearSettings_Home which is a data stream coming into Tableau Cloud. I have it populating but it is not showing current year 2026 or next year 2027 which are custom Fiscal Calendars created in our org settings. It does populate all previous years.  

I have tried:

1. Refreshing the data stream
2. Rebuilding the data stream

Can someone please give me a pointer to get current year I really want to avoid a manual upload yearly of fiscal calendar and unfortunately, we do not follow a standard cadence of 4-4-5 etc. 

When I publish a workbook to Tableau Cloud, the headers render white instead of black. When I reopen the workbook in Tableau Desktop, the headers display correctly in black. The issue appears to be specific to the publish/rendering process on Tableau Cloud. 

Has anyone else experienced this? Is there a known fix or workaround that doesn't require me to just make text object headers?  

 Dynamic year selection on an OLAP cube — INDEX() breaks for members with different year-spans

Setup: Tableau Cloud, web authoring (no Desktop), on a multidimensional OLAP cube. On the cube I can't reference the year in a calc — [Year] = [p.An] returns "undefined field" — so I select the year positionally with a table calc: INDEX() = [p.An] - 2022 (filter = TRUE, Compute Using = Year). YoY via LOOKUP([Measure], -1).

Problem: This is fine for aggregate views, but in a product-level table the partition is per product and INDEX() is positional. Products that don't exist in every year (new / discontinued items) get shifted indices, so the filter picks the wrong year for them. Example: with p.An = 2025, three brand-new (2026-only) products appear showing their 2026 figures.

Question: What's the recommended way to do a fully dynamic, parameter-driven year selection on an OLAP cube (web authoring) for member-level tables

, robust to members with different year-spans — given I can't compare [Year] to a parameter in a calc? Is densification/domain padding or a specific table-calc pattern the way to go, or is a model-side fix the only option?