Tableau Feed

Hi, @Andrzej Polachow

Thank you for reaching out. Using the technique I shared earlier, it's also possible to create multiple representations as shown in the attachment.  

Please take a look. (The sample is kept simple for demonstration purposes.) 

<sample>

@Rajneesh Sharma

Please note there is a ban on AI generated answers on the Tableau community forums. 

Please read carefully the following guideline:

There is also no added value to paraphrase somebody's else answer.

@Patrik Melichercik the outline feature really only outlines the borders of a geography.  The datavis.blog

has a set of examples of what can be done with the fairly new OUTLINE() function if that's what you're asking for.  There are limitations. 

What you're trying to do, which is now the first that I'm seeing it mentioned in the thread, is more of a drill-down process Region --> Country --> State/Province which is an entirely different concept and process.  They can be complicated, and not always work as intended.  You can look at

as well. 

Insofar as user-friendliness, this for me is more of a training issue than anything.  A notation in the dashboard would suffice to tell the user how to use the dashboard, and still get the functionality you're looking for.  They'll just need to hit the ESC key once/twice to exit out of a polygon that has been selected. 

I don't currently see a method of using 'on select' at this point without a greater level of involvement and likely some type of additional layering which may or may not break things due to too many competing actions, whether filter action, highlight action, parameter action and so on. 

Sorry that we weren't able to help.  Maybe those additional links will help point the way for you.  Best, Don

 hi

Tableau Next is different from CRM Analytics in this area. It doesn't currently provide a dashboard JSON editor/viewer equivalent to the CRM Analytics dashboard JSON.

For metadata and deployment, Tableau Next uses Salesforce metadata/deployment capabilities and Tableau Next APIs, depending on the component.

So if the goal is to programmatically inspect or migrate dashboards, I would recommend using the supported Tableau Next metadata/API mechanisms rather than looking for a single dashboard JSON file like CRM Analytics.

 hi

For Tableau Next, migration between orgs depends on the component and the features currently supported.

For the Semantic Model, check whether it can be moved using the available Salesforce/Metadata deployment mechanisms.

For Visualizations and Dashboards, the recommended approach is to use the supported Tableau Next deployment/migration tools rather than manually recreating them. Also ensure that the target org has the required data connections and permissions configured first.

If you're migrating multiple components, I would recommend checking the current Tableau Next deployment/metadata support matrix, as not every component may be directly deployable between orgs.

hi

This appears to be a current limitation in Tableau Next.

If nested containers and floating layouts aren't supported, you won't be able to reproduce the same dashboard layout behavior as in Tableau Desktop.

For now, the practical workaround would be to use the available layout/container structure and arrange the sheets sequentially rather than overlaying them. Hopefully, future releases will add support for nested containers and floating objects.

@Divya Jayachandra

Hi, when you initially buy a creator license, you should be asked if you are going to use Tableau Server or Tableau Cloud.  A creator license can only be used for Tableau Server OR Tableau Cloud. It can't be used to activate at the same time Tableau Server and Tableau Cloud. 

If you want to activate Tableau Server, you would need to buy another creator license, and therefore make sure to ask the Tableau Account Manager/Tableau-Salesforce partner it is a new install, and you need it for Tableau Server. 

Once you have enabled Tableau Cloud or you have installed Tableau Server, you can activate Tableau Desktop and Tableau Prep Builder using LBLM 

On the other hand, if you are looking for the tenant portal in Tableau Cloud (Tableau Cloud Manager), your user needs to be configured as a Cloud Administrator: 

If you are a Cloud administrator, once you have signed in into your Tableau Cloud site, you will find a site selector in the upper left corner, just below the tableau, and the option to sign into the Cloud Manager will be enabled.  

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 

 hi

This usually happens when the new SQL/data source doesn't expose a field that the existing workbook expects. The error specifically mentions __measure__2, which suggests a measure used by the workbook is missing or has changed after replacing the data source.

I would check:

• Compare the old and new data source fields, especially measures and data types.
• Check calculated fields that reference the removed/renamed measure.
• Recreate or replace the affected field in the worksheet.
• If possible, use Replace Data Source and verify the field mappings.

If the field exists but the error remains, try removing and re-adding the affected measure/calculation to the view. The workbook may still contain an invalid field reference from the old SQL.

 hi,

That setting is related to including Tableau user information in generated SQL, but it doesn't necessarily mean BigQuery will show a visible query tag.

I would first verify that the configuration was applied successfully with:

tsm configuration get -k native_api.UserInfoInGeneratedSQLEnabled

Then apply pending changes/restart Tableau Server if required.

Also check the actual generated SQL/job details rather than expecting a separate BigQuery tag field. If the setting is enabled but no user information appears in the generated SQL, I’d check the Tableau Server version and BigQuery connector/version compatibility.

 Hi,

Yes, scheduled extract refresh should pick up new CSV files when the data source is configured as a folder connection.

However, make sure the published data source retains the folder-based connection and that the new files have the same structure/schema as the existing files.

If it works when refreshed from Desktop but not through the scheduled refresh, I would check the Tableau Server/Backgrounder account permissions to the folder first. The account performing the refresh must have access to the folder and its new files.

Also check the extract refresh job logs for any file-access or path-related errors.