#Tableau37 debatiendo

Hi, @Blake Swan 

Thank you for checking.  

In your original calculation field Projected Carry From Prior Month, the formula for LOD Pro C Month 1 matches what is shown in the figure, and it appears to be calculating correctly. 

Could you provide some additional explanation on how you calculated the value you mentioned — “Month 1 the calc should show 24,422”  

@Glenn Smith

This one is almost always the browser blocking the extension rather than anything wrong with your steps - viz extensions load inside a sandboxed iframe served from an external host, so anything that blocks that iframe stops Sankey/Table from ever appearing. 

A few things to check, in order: 

- Launch the unit fresh from Trailhead and sign in to your Tableau Public account inside that playground window. Don't refresh or reopen the tab mid-unit - the playground resets and you lose the extension - so do the whole unit in one sitting. 

- When you pick the extension under Marks card > Add an Extension, watch for the permission prompt and click Allow/Open. Network-enabled extensions will not run until you grant that. 

- Try a clean Chrome window (or Incognito with third-party cookies allowed) and turn off ad-blockers / strict tracking protection for the session. That is the usual reason the extension silently fails to load. 

- Make sure JavaScript is enabled - viz extensions use the Tableau Extensions API JavaScript library, so a blocked script means no extension. 

If this helps, please mark it as the Best Answer so it helps the next person - thanks!

@Blake Swan

Hi, you may use:

SUM({ FIXED  [Charter Product Type],
    [Customer Name],
    [Customer Number],
    [Market Segment],
    [Product Type],
[Month Number In Relation To Current]:
SUM(
    IF [Month Number In Relation To Current] = 0
    THEN [Actual Demand]
    END
)
})
+
SUM({ SUM([Line Weekly Past Due Tons])
})

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, @SSMK A

I may still not fully understand what you’re trying to achieve, but are the values shown in the Sample diagram what you’re referring to? 

For checking purposes, I’ve displayed each value as well. 

Since the processing is done with an LOD calculation, please be aware that if you need any filter operations, you’ll have to use a Context Filter. 

<sample>

<calc>

@Kasumi Kikugawa unfortunately you will be constrained / limited by an internal character limit in Tableau.  Depending on the data source it is 255 to 1024 characters maximum.  There may be a workaround to extend that using a solution from Interworks: https://interworks.com/blog/tmccullough/2013/12/20/displaying-long-text-fields-tableau-excel or changing the DB/SQL Server type to a larger value: https://furtherrandomthunks.wordpress.com/2012/12/13/tableau-and-the-1k-string-limiting-with-sql-server/

Another option might be in the Tableau Exchange Gallery, using a Write Back extension in the dashboard.  There are several, but you'll need to explore with each developer as to any constraints or limitations:

  Those are probably your better options. 

Ref:

If this response answered your question, please mark it as an Accepted Answer? 

This way, others searching for similar solutions will find the answer faster in the future.

Best, Don Wise (Tableau Ambassador)

In CRM Analytics you do not actually 'connect' separate dashboards, the pattern is to build ONE dashboard and use Global Filters to slice it by region/object/etc. How you get there depends on whether your regional dashboards sit on the same dataset or different ones: 

If they are all on the same dataset (the easy case): 

Create a single new dashboard on that dataset, add the charts/widgets you want, then add Global Filters (the filter panel in the dashboard editor) on Region, Object, and any other fields. Widgets built on the same dataset facet together automatically, so one Region selection filters everything at once. That gives you the 'one global dashboard, filter by region' behaviour you are describing. 

If each region is a separate dataset: 

You first need them in one dataset, otherwise a single Region filter has nothing common to filter on. Use a Recipe (Data Prep) to UNION the regional datasets into one combined dataset, and if a 'Region' column is not already on each, add it in the recipe so every row is tagged with its region. Then build your single dashboard on that combined dataset and add the Global Filters as above. Since you tagged Dataset Recipe, this is likely your path. 

A couple of pointers: 

- Global Filters live in the dashboard's filter panel and apply to every widget bound to that dataset, pin them so they persist. 

- If you keep widgets from more than one dataset in the same dashboard they will not auto-facet, you connect them with bindings, or cleaner, unify into one dataset via the recipe so faceting just works. 

Net: do not try to link the existing dashboards, rebuild as one dashboard on a single (recipe-combined, if needed) dataset, then Global Filters give you the region/object slicing. 

If this helps, please mark it as the Best Answer so it helps the next person. Thanks :)

Hi Vaibhav, 

You won't need to touch all 200 devices individually. You'd configure the Tableau MCP connection once, centrally, and push it out to devices via your org's device-management solution. Each user still authenticates to Tableau individually, so they'll only see the content they're already authorized for. 

Also, for Tableau Cloud, Tableau is moving to a hosted Tableau MCP — no self-hosting or maintaining a server on your end. It uses OAuth 2.1 and is built for enterprise-scale deployment. 

So the flow becomes: 

Admin → Central MCP configuration → Claude users → OAuth → Tableau Cloud 

Not 200 separate setups — one centralized config, with individual auth and permissions still intact. 

Regards 

Rajneesh