Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Empty extracts are used for creating literally, pre-defined extracts ready for filling from an alternate source, typically, Tableau Server which usually:

  • has larger pipelines than users
  • is often physically located closer the data-server than an end-client so suffers very little network lag 
  • generally has a larger memory and greater processing power than an end desktop client

The empty extract is a method of defining the connection as you would normally but then instructing Tableau with the aid of a parameter to download non-existent data so that the field names and meta are generated, but no data is captured to the extract during the initial process. 

Instructions

...

  1. Select Extract Data from the context menu

...

  1. Press the Add... button beneath the filters box
  2. Add the "zEmptyExtract" field
  3. Select "T" or whatever value you chose to represent this
  4. CRUCIALLY now choose exclude to ensure only those fields that do not have the value of 'T' are brought through - all of the data in your source will be marked as 'T' so none of the fields will be transferred
  5. Press OK to add the filter
  6. Press Extract to begin the extraction - this will be complete in a split-second as no data will be transferred

...

Info

Here's a good 'un, using a parameter to highlight.

I know, create a bar chart, make a parameter, use a boolean output, stuff the pill onto the colour marks, and watch as each of your selected attributes instantly flashes up your chosen highlight colour

That wasn't so hard was it?

Now make a tree-map:

  1. Set marks to square
  2. Add Category and Sub-Category to the text in this order, to create a hierarchical tree-map
  3. Then add Sales to the size
  4. And finally, your discrete calculated attribute to the colours, exactly as you did in the earlier bar chart

But, oh dear, each time you select an item, Tableau moves the item out of sequence. Sure, it is being highlighted, but the sequence is not retained, why?

Well, this is all down to how your marks are laid-out. You see, when using the rows and columns, Tableau is able to use these to define the primary output, so bars and lines already have a pre-defined structure, any further attributes placed on the marks card, calculated or otherwise are only secondary to the layout.

But, when the rows and columns are not used, the marks card becomes Tableau's only source for determining layout, so all dimensions are used in the layout, with Tableau then splitting the final underlying table to include those items inside the boolean filter, and those that are out. So in the case of the hierarchical map, a further dimension has been added: Category, Sub-Category and boolean filter.

So how do we get around this?

By using a boolean output that Tableau will not use as part of the layout, by using a calculated measure:


Paste code macro
languagesql
Min(Iif([Sub Category] = p_SubCat,-1,1))

Instructions

  1. Create a parameter from the Sub Category dimension, call it p_SubCat
  2. Add an 'All' attribute too, move this to the top of the parameter list
  3. Create the above calculated field, call it something like highlight
  4. Create your treemap
  5. Place your highlight field onto the colours and set a corresponding value for the outputs
  6. Sit back and watch as adjusting your parameter hilights the selected without altering the layout


Info

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@ce3c1862
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel = "kb-how-to-article" and type = "page" and space = "TABLEAU"
labelskb-how-to-article

...