Ken, thanks for pointing that out! I hadn't noticed it before, but now that I know about it I will use it alot. Usually, I either edit out unwanted fields in Excel prior to connecting, or I hide unused fields after I get the viz built. Now we can filter out unneeded fields at the data connection level.
A handy new tool, thanks Tableau.
UPDATE: OK, that didn't work the way I thought it would. It's not eliminating fields in the data, but filtering records base on field filters. In other words instead of putting a field on the filter shelf, you can filter the data source then you won't have to put a filter or global filter on each sheet.
sometimes Oracle - sometimes Netezza
It sounds to me like you are attempting to store your data model inside the extract, using some type of Custom SQL. Is this true? Would it not be easier to to create a view in your database, then extract off of that. In that case, you could change the view to any specification you would like, and all you have to do is refresh your extract and it will pull again. Does this help or am I misunderstanding?
A few issues with that - on the Netezza side - I only have read permissions - so I can't create a view.
I just link to tables and pull, and sometimes need new fields that were added to the tables, or need to join to entirely new tables. And I will want to rename the new field (get rid of CAPS and "_"), maybe put it into a hierarchy, etc. So - can't get away from having 'model' changes.
So - still trying to figure out what the 'Edit Data Source Filter' is for - how is that differ from when I add filters via 'Extract Data'.
I too am looking for the answer to this.
What is the "Edit Data Source Filter", and is it related to the filters used when extracting data? I can't seem to find any documentation on this.
Were currently on 8.0.0, if that helps.
Your link just takes me back to my post?
Sorry Ken, I pasted the wrong link - I've updated it, try again.