#Tableau Cloud토론 중인 항목 72개

@Suryavamshi Sirigadhi

 When working with Bridge, what I recommend you is to use Published Data Sources.  Working with workbook embedded datasources take longer to refresh (the last time I tried it took like 10x more time). Why? when you are using published data sources, the extract is created in the machine (e.g the ec2), therefore the extract is created in the machine and the info travels really fast between your redshift and your bridge client.  However, when refreshing workbook embedded datasources, the extract is created in Tableau Cloud. Therefore, all the info travels through the internet to Tableau Cloud, and then Tableau Cloud creates the extract.  Thus, the transfer speed redshift->Tableau Bridge->Tableau Cloud is not as good as in your VPC.

The first thing you should take a look is make sure everything is correctly set up for your Bridge Client.  Thus, I recommend: 

a. Go to Settings->Bridge Tab and make sure your Bridge client is Connected. 

b. Make sure your  <our-cluster>.<our-region>.

redshift.amazonaws.com

 is in the allow list of the bridge pool, and that the bridge client is in the allowed pool. If you are using a local ip instead to connect from the bridge to the redshift make sure to include that also in the allowlist. 

c. Verify your Bridge Client machine can use ports 80 and 443 for incomming outgoing connections to Tableau Cloud ips (

https://help.tableau.com/current/pro/desktop/en-us/publish_tableau_online_ip_authorization.htm

). If using Tableau Bridge on Windows, make sure it is configured to run as service (not as application) 

https://help.tableau.com/current/online/en-us/to_bridge_site_settings_win.htm

c. Go to Explore, create button, new datasource.  Use as server the local ip, or the hostname identifier your bridge uses to connect to redshift. 

d. If you can connect to your Redshift, then the Bridge is working correctly. 

 Now, some steps at the workbook: 

e. Go to your workbook, datasources tab.  Edit the connection and make sure to use as host/server the hostname your bridge uses to connect to Redshift (that is also in the allowlist of the settings->bridge tab). Review other parameters as password if needed. 

f. Go to the Extract refreshes tab, delete all schedules. 

g. Create new schedules, and try to refresh. 

If this does not resolve the question, go to the jobs section, hover over the job, and take a screenshot so we can take a look of the error. 

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 

You can do the Union in your first Custom SQL script itself as shown below 

SELECT A,B,C 

FROM XYZ 

WHERE Condition1  

UNION ALL 

SELECT A,B,C 

FROM XYZ 

WHERE Condition2 

UNION ALL 

SELECT A,B,C 

FROM XYZ 

WHERE Condition3  

 The crosstab export only pulls data from a single worksheet's grid — those text sheets you added as visual headers have no data behind them, so they don't make it into the export. 

What works is putting the header text into the actual data sheet as a calculated field. Something like: 

'Main Header Name' 

Drop it on Rows above your dimensions, same for the sub-headers. Then they're part of the data structure and will export. 

If you need merged cells or visual formatting though, the export won't preserve that — you'd have to format in Excel after. 

@Nicole Chang

From what I see the LWC component does not have a checkbox to enable the oda (on demand access) access or to pass the oda groups claim.  These JWT claims are needed so you can give access to the ODA access:

You may confirm with Salesforce support creating a case: 

Take into account ODA (On demand access) is only available for Tableau Cloud tenants with Usage Based Licensing or the newly introduced Capacity Based Licensing 

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

@Himal Singh

If you want to embed without authentication and keep data in Tableau Cloud, this site may help you. 

But each viewer needs a Tableau Cloud license. 

If you want truly public access with no license, Tableau Public is better.

 @Rajashekar Atmakuri

As Mr.Diego mentioned, it would be helpful if you could share the exact error message first, but here are a few possible reasons why this might be happening:  

As explained in the documentation below, when you change the owner of a workbook on Tableau Cloud, the embedded credentials used to connect to the data source are cleared/lost. This could be causing the data source connection to fail.   

If this is the case, you should be able to resolve the issue by editing the data source connection and re-embedding the credentials (the Oracle ID and password).  

While this might be less likely, if you are using two or more Oracle databases located on different networks, you will need to set up a dedicated Tableau Bridge server for each network/pool.  

Hi @Wiwit Setyaningsih

I'll reiterate both yours and @Gohar Clients thoughts on the compute by - definitely on the right track. Here's where I can take things by working on that and a small tweak and additional calc: Workbook re-attached.

First thing you'll see is a new calc: YoY (Latest Year  Only)

IF LAST()=0THEN [YoY]END

(NB: I also renamed your "Calculation 3" to YoY). 

The new calc just says "only return a value for the last year* in the view". We do have to tell Tableau that we care about the year for this part of the calc. And what we end up with is a nested table calc where the compute by for one part is different to the other! 

Right click and edit the table calculation pill on Rows:

First up I'm working on the "Latest Year Only" calc as you can see in the top drop down. And I tell it to compute by specific dimensions and year only. So the latest year should be the last (LAST()=0) in the window. 

Now I change the drop down to the "YoY" calc and tell this to compute by specific dimensions again, but this time Year and Month (in that order)

NB: Show calculation assistance is quite handy here as I can check that I am indeed seeing values 13-24 in the window. Now you might be thinking "hang on, how did my lookup -1 work in that case?!?"  and you'd be right! I also changed the lookup to be a lookup by -12 so now we're looking back to the month 12 months ago. 

The lack of an ELSE in the second calc is what supresses the previous year from showing ... it's still available to the calc as we've "filtered" using a table calc so that happens late in the order of operations ... and those are the "nulls" shown by the >12 nulls indicator. 

Finally I CTRL+click and drag the pill from Rows onto Mark Text too so that I don't need to repeat the nested compute by there. 

Let me know if this helps!  

Compute by is often fiendish enough without (a) nesting; and (b) your great workaround for side-by-side without a discreet pill on Columns! 

Ta, Steve