This page has an error. You might just need to refresh it.
Unable to find an action for 612;a: {"id":"612;a","state":"SUCCESS","returnValue":{"Id":"0054T000001NHMqQAO","Name":"Tableau Community Forums Site Guest User","FirstName":"Tableau Community Forums","LastName":"Site Guest User"},"error":[]}
I need to create a role in Tableau Cloud that can assign licenses but cannot view flows and published data sources. Does anyone know if this is possible? Thanks.
I am using tabcmd in Alteryx to publish a data source on a Tableau Cloud server. It runs successfully but is putting the data source in a folder other than the one I specify. I am using the correct version of tabcmd.
publish "\\tabnalafileshare.roche.com\tabnala\BASE\Compensation and Data Excellence\MDM\Customer Hierarchy\Extracts\Workflow Extracts\Customer_Hierarchy_Reporting_GlobalSpace.hyper" -s https://us-west-2b.online.tableau.com --site tabnalacloud --token-name "Alteryx" --token-value "S/gKzIAbTciaHeSvFBvccw==:5pnbER239MHUXH0zNo277qvG8rWevpIz" --overwrite --parent-project-path "Global Space" --project "CDE_MDM" -r "Business - Data Sources" -n "Customer_Hierarchy_Reporting_GlobalSpace" --overwrite --no-certcheck
Tableau Desktop login to Tableau Cloud won't stop redirecting to an SSO login
I have an account that I use to access multiple Tableau Cloud sites. One of those sites is set up to use Okta SSO. I connected to this site and clicked Remember Me, then logged in.
Now when I try to access a different non-SSO site, I can't - Tableau Desktop _always_ redirects the login page to the SSO Okta login (which won't allow me access the 2nd site).
I have tried:
* Uninstalling and reinstalling Tableau Desktop
* Clearing all Saved Server Logins from the Help menu
* Clearing all cookies from my web browser
I'm stuck now, unable to access the 2nd site - I can only do so from an earlier version of Tableau Desktop
Using the Embedded API and On Demand Access, can we set up row level security based on USERNAME() and entitlement tables?
We are using the Embedded API to display Tableau dashboards in a web portal. Our row level security is based on the username mapped to a customer ID in an entitlement table, so the user can only see their personal data.
For On-Demand Access (ODA), it looks like we don't have to provision users on our Tableau Server. Rather, access will be controlled on the web portal side, and the web portal can send user attributes to Tableau via the token.
With ODA are we still able to use our entitlement tables for RLS? Will it be secure? It's critical that our customers can not see other user's data.
Right now, our plan is:
Set up the connected app using Direct Trust
Set up Tableau Groups for ODA
Updated the token to enable ODA and Groups, and then pass an username() attribute to Tableau
Set up the entitlement table with username and Customer ID
Created a relationship to the main dataset using Customer ID
Created a security filter lower([Customer]) = lower(USERATTRIBUTE("Username")) and set to TRUE
Published Tableau data source and connect the embedded workbooks to that data source
For testing, we have my personal email hardcoded in the token under the "sub" as we needed a provisioned user to test the connection to our Tableau site. Can that be removed once everything is set up?
So, I have not tested if this restriction still is active (you may test it). So, I recommend you to make three tests with:
a. Published data source (it may fail) which contains the lower([Customer]) = lower(USERATTRIBUTE("Username")) inside the data source in the data source filters section. (so you publish the datasource with this data source filter) -> It should not work.
b. A workbook connected to a published datasource, that has the relationship to your entitlement table but not the datasource filter published in the datasource. Instead, create the calc at the workbook level (lower([Customer]) = lower(USERATTRIBUTE("Username"))) and add it as a datasource filter from the workbook. -> It may work.
c. Test with an embedded data source in the workbook (so the relationship model belongs to the workbook) and create the user filter calc within the workbook and apply as a datasource filter -> This should work.
For testing, we have my personal email hardcoded in the token under the "sub" as we needed a provisioned user to test the connection to our Tableau site. Can that be removed once everything is set up?
It seems you may be using a Tableau Cloud site that does not have ODA and Usage Based Licensing activated, so I guess you are testing on this site without ODA and that is why you need to use the sub clause with an existing user. When moving to the ODA Tableau Cloud site, I recommend you to use still the sub JWT attribute, but with the username of the not provisioned user. If I remember, you may use USERATTRIBUTE("sub"). If the sub attribute is not accesible with userattribute, you may add another attribute to the JWT with the username.
e.g USERATTRIBUTE("username")
Also, you would need to pass the https://tableau.com/oda attribute in the JWT with the true value. (it can only be used with sites with ODA activated and usage based licensing).
If this post resolves the question, would you be so kind to "Select as Best"?. This will help other users find the same answer/resolution and help community keep track of answered questions. Thank you.
How to configure the OAuth provider when connect Tableau Cloud to AWS Athena using OAuth authentication?
I’m currently in the process of connecting Tableau Cloud to AWS Athena using OAuth authentication. I’ve managed to gather all the necessary information except for the OAuth Provider, which shows as "OAuth is not configured."
Could anyone guide me on what specific information I need to configure the OAuth Provider for this setup in Tableau Cloud?
Any help or guidance on how to properly configure this in Tableau Cloud would be greatly appreciated!
Hi all, I am so confused with this error. I created a calculation in Tableau Prep as follows: { PARTITION[ConcatField]:{ ORDERBY [ConcatField]:ROW_NUMBER()} } .... Read more in Details
Hi all,
I am so confused with this error.
I created a calculation (RN) in Tableau Prep as follows: { PARTITION[ConcatField]:{ ORDERBY [ConcatField]:ROW_NUMBER()} }.
I can run the flow, and everything looks good without error on local desktop Tableau Prep. However, I can't run the flow as it occurs an error saying that invalid RN field (screenshot attached below) when I published this flow to Tableau Cloud.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.