#Tableau Next10 personnes en discutent

Good morning - you are asking about several separate different Tableau funamental functions - I recommend you see the series I wrote for New to Tableau users https://jimdehner.com/bgs-beyond-getting-started-the-path-to-understanding-tableau/   - it is a 13 part (yoiu can pick and choose among the topics)  it is also on Youtube - see the playlist https://www.youtube.com/playlist?list=PLBKGe-fkLXxt5gycYDP_F-Y7MHj0GczJp  and then attend the Tableau Newbie User Group - https://usergroups.tableau.com/tableau-newbies-user-group/  - our theme this year was the "Road to Certification" you can pick up any misses session from the recording link at that site and sign up for our next meeting on October 6th

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.