#Tableau Next16 debatiendo

I’ve run into similar layout limitations where having more control over how different elements are positioned would make the design much easier. Nested containers would definitely be useful for organizing complex layouts, while a floating option could help when you need to layer or position elements more freely.

I’ve been working on the online presence of a local handyman business too, and I’ve noticed that having a clean, well-organized layout makes a big difference in how users interact with a site. This is one example I’ve been working with: https://www.thehandybrosco.com/

Hopefully, these layout options get added in a future update, especially for dashboards that need more flexible positioning.

Hi @Fiona Crocker,

This is expected behavior in Salesforce Data Cloud.

Data Kits don’t reliably overwrite existing components, so redeployments may show "success" but not apply changes.

Try:

• Deleting or versioning the existing component
• Deploying with a new name
• Ensuring all dependencies are included

They work best for initial deploys, not updates 👍 

If you find this helpful feel free to mark it as Best Answer !!!! 😊 

Thanks and Regards.

@Fiona Crocker

Hi, you may create a double axis chart (synchronized axis) and use the Range option to simulate a reference line:

Range Option basically is used to create like a gannt chart, where you can set the size of the bar (In this example I used AVG(-1000), however I recommend some kind of calculated field. Why? If the value is small the bar/line will not be rendered, if it is really big, it will look like a bar, not like a line) 

Thus, this is a workaround!! The right solution is to create the idea like you have done. 

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

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 Ansar,

With continuous fields, Tableau creates an axis rather than a discrete header. You can still customize the title by right-clicking/double-clicking the axis and selecting Edit Axis, then changing the text in the Title field.

If you're referring to the worksheet/chart title at the top of the visualization, that can also be edited independently through Edit Title. Tableau supports editing worksheet titles regardless of whether the fields in the view are continuous or discrete. 

So you don't necessarily need to convert the continuous field to discrete just to change the title. If you're unable to see the Edit Axis or Edit Title option in Tableau Next specifically, please share a screenshot of the visualization and the options you're seeing, as the Tableau Next interface may differ from Tableau Desktop/Cloud.

Hi, 

Are you looking for something like the attachment? Please take a look. 

The idea is to create parameters with ON/OFF values and then set up corresponding fields that switch OFF/ON in response, allowing you to control visibility through parameter actions. A dedicated sheet is prepared for the checkbox, where ON and OFF are represented using shapes. Please see the details below. 

This was implemented using only standard features. The display switching is handled by configuring a DZV. 

<sample>

 <parameter>

<calc>

<dashboard action>

 <check box sheet settings> 

Using the “off‑on” field from the checkbox sheet, the display switching is achieved through a parameter action. 

-Configuration for the checked state. Please pay attention to the shape and color.

*Sorry if the square shape is a bit confusing, but the checkbox frame itself is represented using borders.”

-Configuration for the unchecked state. Please pay attention to the shape and color.

<Dashboard DZV settings>