#Tableau Cloud64 debatiendo

 Hi,

The issue is that manually added sheets/text objects in a dashboard are layout elements, not part of the underlying worksheet data, so they generally won't appear in the downloaded Excel/CSV.

A better approach is to create the headers/sub-headers as fields within the worksheet itself (for example using calculated fields or a hierarchy) and format them in the view.

If the exact dashboard layout must be preserved in Excel, another option is to use PDF/PowerPoint export rather than Excel/CSV, since Excel/CSV exports the underlying worksheet data rather than the complete dashboard layout.

So for Excel, the headers need to be part of the worksheet/data structure rather than separate dashboard objects.

 Hi,

If the Bridge connection is healthy and the extract can be created successfully from the Cloud workbook editor, then Bridge itself appears to be configured correctly.

I would first check the scheduled refresh configuration and Bridge pool assignment for the published data source/workbook. Also verify that the published data source is actually configured to use the same Bridge pool and connection credentials.

Desktop inside the VPC should not necessarily be required just because Redshift is private—Tableau Bridge is designed to allow Tableau Cloud to access private-network data sources.

If you can share the remaining part of the error/job details from the failed scheduled refresh, it would help identify whether this is a Bridge routing, authentication, or extract-refresh configuration issue.

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  

@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