- Are you tired of rework in Spotfire?
- Are you frustrated with inserting columns over and over again after you replace a table?
Once again you’ve had to replace a data table and lost all of your inserted columns. How do you keep this from happening and avoid rework?
Solution Description: Rather than having a DXP file with a single table with columns inserted from many other tables, architect the DXP to include all data tables that will be used in the analysis, reinsert one of the tables (the master table if you will) and then insert all necessary columns, as shown in the model below.
How/Why It Works: If/when you have to replace a table, replace the component table(s) rather than the master, and the components will continue to feed the master. The master table is where columns are inserted, and it is never replaced, which means no lost columns.
Pros: If you have to replace a table, you won’t lose any of the inserted columns, which eliminates or reduces rework. It also makes troubleshooting errors easier.
Cons: Creates larger DXPs because you have more tables. There will still be errors if you lose a column from the component table that is used to join to the master table.
Other Notes: You can see in the Edit menu, Data Table properties, Source Information tab (of any table that has inserted columns), that the way Spotfire builds tables with inserted columns is to specify which columns to ignore, rather than which columns to insert. Therefore, if new columns are added to the tables you are inserting columns from, those will also be added to the master table. You can always exclude them in a transformation when the table is replaced. Lastly, when replacing tables, if a column name changes and it is used to join, you MUST match the old column to the new column when presented with the dialog showing the differences between the old table and the new table.
Guest Spotfire blogger residing in Whitefish, MT. Working for SM Energy’s Advanced Analytics and Emerging Technology team!