#Tableau Server68 discussing

I have a Data-Driven Alert set to "Once - the first time it's true", watching a % Usage measure against an 80% threshold. The underlying calculation is tied to a rolling 12-month contract period (Aug 1–Jul 31) that resets automatically each year via TODAY()-based calculated fields — so % Usage climbs from 0% at the start of each contract year, and may or may not cross 80% before the year ends. 

Example scenario: 

• Contract Year 1: Aug 2026–Jul 2027. Usage crosses 80% in March 2027 → alert fires, one email sent.
• Aug 2027: new contract year begins, % Usage resets to ~0% (condition goes back to false).
• Contract Year 2: usage climbs again and crosses 80% in April 2028.

Question: In Year 2, once the condition goes false (Aug 2027) and then becomes true again (April 2028), will the alert fire again? Or does "Once - the first time it's true" mean the alert only ever sends a single email for the lifetime of that alert, regardless of the condition later resetting and re-triggering? 

I haven't been able to find documentation that's explicit about whether "Once" re-arms on a false→true transition, or whether it's a one-shot for the alert's entire existence. Has anyone tested this across a reset cycle, or does Tableau document this behavior anywhere? Trying to decide whether I need to manually recreate the alert each year or whether it'll keep working unattended. 

Tableau version: 2024.2.4 

I am experiencing an issue with a scheduled extract refresh on Tableau Server.

Setup:

• Workbook is saved as .twb.
• An Excel data source is joined with our Finance DataMart.
• The Excel file is connected using a UNC path: 

\\afcu-nas1\Vol1

The workbook publishes successfully and can be accessed by users.

Error:

Plain Text

1

Connectionless Failure (status code = 10000)

2

3

One or more connections in this data source need attention:

4

AZ Financial Daily Dash - FRB: Unable to connect to the file

5

"FAKEPATH-0bb8dbj1xzpc3f15h22kp1cqe5lv".

6

7

Check that the file exists and that you have sufficient access privileges for it.

Show more lines

Could you please help us understand:

• Why Tableau is attempting to access a FAKEPATH instead of the configured UNC path?
• Whether additional server permissions or configuration are required for scheduled refreshes against an Excel file on a network share?
• Any recommended steps to resolve this issue and enable automated refreshes?

#Trailhead Challenges  #Tableau Server

We do not have Admin access to our Tableau Server, but we have access to PostgreSQL DB workgroup schema. 

We have a need to monitor LDAP groups, users and Site Limits. 

We have created custom data model for the data (screenshot attached), but results do not match with details presented on Tableau Server (supporting group with Admin access is sharing latest Site Limits numbers) and some of the users do not have names displayed. 

Please let me know if our model is using proper objects. 

Is there any documentation for the workgroup schema tables how to connect them? 

We start with users: 

- id 

- site_id 

- site_role_id 

joined group_users via

= group_users.user_id for: 

- group_id 

joined groups via group_users.group_id =

for: 

- name (group name) 

joined hist_users via

= hist_users.user_id for: 

- name (user name) 

joined site_roles via users.site_role_id = site_roles.id for: 

- display_name (site role name) 

joined sites via users.site_id =

for:  

- name (site name) 

Viz 1 

Rows 

site_role_id, display_name, countdistinct (user_id) 

we have number of users for each site role. We can add here role_name, we can add user_name, but there are NULL values for user_name from hist_users.  Why there are NULL for user_name? Are they past users? Never logged in? 

Viz 2 

We would like to find number of Site Limits for each license type. 

In sites table there are three columns named 'Tier Basic User Capacity', 'Tier Author Capacity', 'Tier Interactor Capacity'. Are them the ones to preset set Site Limits? If no, where can I found proper numbers? 

Hello Everyone,  

I published a very big dashboard with 17 dashboards and more than 10 data sources inside. 

the goal of this is to be able to extract all the dashboards as a PDF at once. 

So when the processing is ended, nothing happen. I guess the pdf should be in my windows download but nothing there. 

Does anyone knows what to do to get my 17 dashboards downloaded ? 

thanks a lot for you help 

Antoine 

Environment: Tableau Cloud, REST API 3.29, tableauserverclient (Python), Snowflake connection with authentication='oauth', oauth-config-id='default', server-oauth='server-custom'. 

ISSUE 

We publish workbooks via REST API/PAT in a CI/CD pipeline. We're trying to reproduce a connection state that Tableau Desktop can produce, but the REST API can't. 

Desktop-published state (Data Sources tab shows "Not embedded in connection"): 

auth_type='oauth' username='<user>' embed_password=False 

Our pipeline's state (REST API publish): 

auth_type='oauth' username='' embed_password=False 

The Desktop state results in viewers being prompted for their own credentials. Ours results in every viewer getting BadOAuthCredentials, since there's no username hint at all. 

WHAT WE TRIED 

Using Server.workbooks.update_connection() (PUT /workbooks/{id}/connections/{connectionId}), we tested every combination: 

1. embed_password=True + username -> credential embeds, all viewers connect silently as that one identity (no prompt). 

2. embed_password=False + blank username -> every viewer gets BadOAuthCredentials. 

3. embed_password=False + non-empty username (trying to match Desktop) -> the server silently discards the username; a follow-up GET always returns username=''. No error is returned, it just reverts. 

4. Re-embedding (embed_password=True) via update_connection without supplying a password fails outright with 404020: Resource Not Found ... This may be due to incorrect or missing credentials. There's no way to flip an OAuth connection back to embedded through this endpoint without a real credential, and OAuth connections have no password-style credential the API can supply. 

We confirmed #3 fails identically whether attempted via connections=[ConnectionCredentials(...)] at publish time, or via a separate post-publish update_connection call. Same result both ways. 

QUESTIONS 

1. Is there any documented REST API mechanism (any endpoint, any API version) to set an OAuth connection to embedPassword=false while preserving a non-empty userName hint, matching what Desktop produces? 

2. Is that "not embedded + username hint" state inherently tied to an interactive/vizportal-authenticated session (i.e. genuinely unreachable via PAT/REST), or is there an undocumented parameter/flow we're missing? 

3. Is per-viewer OAuth prompting for a Snowflake connection with oauth-config-id='default' expected to work at all when the workbook was published via REST API/PAT, or is this a Desktop-only capability? 

Happy to share full request/response payloads if that helps with diagnosis. 

#OAuth  #Tableau APIs & Embedding

#Tableau Cloud  #Tableau Server