Skip to main content
Tópicos#Tableau Server

#Tableau Server69 discutindo

Faça uma pergunta...
Arvid Carlander
1 de set., 08:29
Minified React error #185

Creating a new workbook with a datasource with connection to MS SQL using the Tableau server GUI works fine but when clicking the "Data Source" tab the page initially loads ok but then there is a delay followed by "Unexpected Error" 

 

The error message is: 

Session ID: 71705F88A636490B90F1B1EF0D85F7C4-1:1 

Uncaught Error: Minified React error #185; visit

https://reactjs.org/docs/error-decoder.html?invariant=185

for the full message or use the non-minified dev environment for full errors and additional helpful warnings. 

 

The additional information when following the link is: 

Upon opening the above URL, here is the message ---

"Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops." 

 

I have restarted the browser, restarted tableau server, and started from scratch with a new workbook and datasource. 

 

We have many workbooks and datasources connecting to this sql server and they worked fine yesterday. 

 

All datasources to this MS SQL server are affected. 

 

 

 

Tableau Server Version: 2025.3.3 (20253.26.0206.0336) 64-bit Windows 

 

#Tableau Server

2 respostas
  1. Arvid Carlander
    Hoje, 08:03

    Hi @Emeric LE SAULNIER DE SAINT JOUAN

    , 

     

    Thanks för your reply. Yes, it is strange. The list you gave me is very useful but following each thread without some assistance is impractical so I have raised a support case  #474501097. If anything of general value comes  out of this I will post it here.

Escrever uma resposta...
0/9000
Harald Egner
Ontem 13:59
ERROR: could not open file "base/16393/20469": No such file or directory

How can we repair one index data entry in the database? 

We get "An unexpected error occured" trying to delete a user or even saving workbooks. the log analytics via CoPilot leads us to an corrupted index entry.

 Is there any way to fix this issue directly without restore the whole database?

#Tableau Server

1 resposta
  1. Emeric LE SAULNIER DE SAINT JOUAN (M2)
    2 de set., 19:52

    Hi @Harald Egner

     

    I assume you have a database object corruption but you are not sharing much information or context. 

    If you want to connect to the Tableau Postgres database and do whatever you want at your own risk as an admin superuser, the db username is "tblwgadmin" and the password can be retrieved through the following tsm command:

    tsm configuration get -k pgsql.adminpassword
Escrever uma resposta...
0/9000
Jim Dehner - Tableau Visionary HoF (Retired na Market Analytics LLC) publicou em Newbie Tableau User Group Desktop
10 de ago., 14:29

Hey 🛑 Tableau #datafam#datafam and Salesforce  #Tableau_next#Tableau_next

 users -  

 Want to level-up your mapping game or not certain which chat type to use with your data? Help is on the way at our September 2nd virtual meeting - you just need to save a spot at 

https://lnkd.in/gkb5kNXS

 and we'll see you there -- 

All are welcome 

#Tableau Cloud #Tableau Server #Tableau Public 

 

Hey 🛑 Tableau and Salesforce users - Want to level-up your mapping game or not certain which chat type to use with your data?

1 comentário
Escrever um comentário...
0/9000
Krzysztof Wascinski (Nokia)
31 de ago., 07:50
Extend password policy with history

My company security team audited the Tableau and found, that specific password policy is not possible to be configured: 

 

New passwords checked against the history of the last 5 passwords and rejected if there is a match

 

Can we request to add such password history check feature in Tableau Server Cloud?  

Extend password policy with history

 

 

 

#Tableau Server

2 respostas
  1. DIEGO FERNANDO MARTINEZ RODRIGUEZ (Modux)
    Ontem 13:24

    @Krzysztof Wascinski

     

    Hi, unfortunatelly not possible with local auth, you will need to use an external Idp (SAML). 

     

    I suggest you to create an idea for this: 

    https://help.salesforce.com/s/cases

     

     

    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 

Escrever uma resposta...
0/9000
Vincent Thomas
Ontem 13:15
MFA with Local authentication

Hi, 

We setup the Tableau Server 2026 with Local authentication, and in the process of hosting the site externally, for security reasons, we need to have MFA for the login process. I don't see an option for MFA. This project is for external customers, who are not in our domain, and will not be added to the domain. 

 

What options do we have for MFA or any additional security options than just username + password. 

 

#Tableau Server  #MFA

2 respostas
  1. Emeric LE SAULNIER DE SAINT JOUAN (M2)
    Ontem 19:36

    Just an additional comment on the Identity Pool part as it is easy to mix up things. 

    Identity Pool is a pair of 1) an identity store and 2) an identity provider. 

    identity store can be local or AD/LDAD, and identity provider always and only OIDC. 

    But the Identity Pool identity store is constrained by your original identity store defined during Tableau Server installation. 

    If identity store local then Identity Pool identity store can only be local (same or new) 

    If identity store AD/LDAP then Identity Pool identity store can only be  AD/LDAP (same!) 

    It is pretty cool but tedious to configure as there is no tsm command or GUI to configure it. it is all through REST API calls only. 

    Then your Tableau login page will have an additional button, for example External users. 

    The internal users can continue to use Local authentication or SAML, it is totally independant.

    Just an additional comment on the Identity Pool part as it is easy to mix up things. Identity Pool is a pair of 1) an identity store and 2) an identity provider.

    It was a very good idea from Tableau, but Tableau didn't further develop this feature since 3 years. 

Escrever uma resposta...
0/9000
Demet Akbas
18 de ago., 14:20
Error executing subquery id: "36165" Fehlercode: 1B885FB3

Hello everyone, 

 

since I replaced my data source with a new SQL, I keep getting this error message: 

 

Aktion konnte nicht ausgeführt werden 

Error executing subquery id: "36165" 

Fehlercode: 1B885FB3 

Logical Query missing field [__measure__2] from joinOp. This is an invalid query.

 

What's causing this? Can you help me? 

 

Thank u so much! 

 

#Tableau Server

3 respostas
  1. Demet Akbas
    1 de set., 10:28

    the problem is resolved! thank u! There was an issue with the SQL.

Escrever uma resposta...
0/9000
Géraud de Larquier
27 de ago., 08:38
Header values visible in Desktop but not on Server

Hello, 

 

My question on the topic detailed below is : is this the expected behavior on Tableau Server or is there something to investigate? 

  

On Tableau Desktop, when you have a table with lots of values, the header values are always on sight even if the number of underlining rows is much higher than the number of rows you can see immediately. To illustrate, you can see

Austria here even if the formatting is in the Middle, and that the middle of that row is much lower in the sheet :Header values visible in Desktop but not on Server

 

When publishing on server, no matter what the formatting is, the behavior is not the same. I.e. it will only show the value if you are viewing the top, middle or bottom of that row's results depending on your formatting choice : 

image.png

 

 

#Tableau Server

2 respostas
  1. Zach Leber (Tableau Community Ambassador)
    27 de ago., 17:49

    Unfortunately that has always been a limitation of Server/Cloud text tables. I prefer Desktop's behavior. You would need to add a unique hidden column like customer ID to the left of country to get it to appear on every row. But that prevents convenient selection by country.Unfortunately that has always been a limitation of Server/Cloud text tables. I prefer Desktop's behavior.

     

     

Escrever uma resposta...
0/9000
mabin kwon
26 de jun., 08:21
Dashboard Image Download REST API With Set Filter

I am using the Tableau MCP get-view-image Tool. Is there a way to download an image with a set filter applied when using a set as a filter on a dashboard? It appears that there is no way to apply a set filter using the REST API View Filter, so I am asking if there is a workaround.   

2 respostas
  1. Alex John
    22 de ago., 19:36

    Hey, I ran into the same thing. The REST API view filters (and the MCP tool that uses them) only work with regular fields, not sets. One workaround that worked for me was to filter on the underlying field that the set is built from and just pass the member values. If that doesn’t fit, creating a custom view with the set already applied and downloading that image is another option. Hope that helps. 

Escrever uma resposta...
0/9000
Tableau Community Forums Member (Inactive) (Member of the Tableau Community Forums na Salesforce)
10 de jan. de 2017, 20:14
How interpret the 'device_type' field in the '_views_stats' Postgres Workgroups view?

I've converted my Tableau Repository info into a Tableau Data Source for our analysts to use (Collect Data with the Tableau Server Repository), but I'm confused about how the 'device_type' field is calculated. The data dictionary is here: Workgroups Database.

 

It shows about half of the views to be accesses by a user/device type of 'Tablet', which can't be true since only perhaps 3% of our users use a tablet or phone to view our visuals.

 

Can anyone help with the interpretation/calculation of this field?

 

Thanks!

 

Andy

6 respostas
  1. Tableau Community Forums Member (Inactive) (Salesforce)
    13 de jan. de 2017, 19:33

    Hi Andy!

     

    From what I understand from the documentation, the "device_type" is not what type of device is viewing the dashboard, it's for what type of dashboard was being presented to the client. The explanation for "device_type" is "DSD device type detected" - "DSD" stands for "device-specific dashboard" - this is the type of dashboard layout created in Tableau Desktop. I do not believe this field will track what device was viewing the page, it will only show what dashboard was offered to the user. you can read more about Device Specific Dashboards here: Design dashboards that shine on any device in Tableau 10 | Tableau Software

     

    Hope this helps!

Escrever uma resposta...
0/9000
Nigel Smith
29 de jul., 11:37
Emedding Tableau dashboad in Sharepoint page - Sign in to Tableau Server

Hi,  

I'm trying to embed a Tableau Dashboard into a Sharepoint page. I have ironed out connection and permissions issues and all is now working well.. expcept.. when somebody first lands on the Sharepoint page instead of seeing the dashboard they see a "Sign in to Tableau" server message / button. If they press this, the dashboard is then displayed, without the need for them to enter any further credetials. So its not a huge issue, but also not a great user experience. Does anybody know a way I can prevent the Tableau sign in page stage please? 

 

#Tableau Server

5 respostas
  1. Carter Gray
    27 de ago., 04:45

    This sounds like an authentication/session issue. Check your Tableau SSO or Connected Apps configuration, and also make sure browser third-party cookies aren’t blocking the Tableau session. Since clicking “Sign in” immediately works without credentials, the user is likely already authenticated, but Tableau isn’t recognizing the session on initial load. 

Escrever uma resposta...
0/9000