Do you ever try to replace data in a Spotfire dxp only to find many of the visualizations no longer work?
At Ruths.ai, we create Spotfire templates as one of our main products. Often, people have to replace our source data with their own to utilize our templates. However, this can cause some complications when they match columns with different names than the ones in our source data. Ideally, people would like to keep their column names because the names have business implications. Yet, when that column name has been hard coded into a Spotfire expression, a visualization, calculated column, or data limiting expression could break.
Until now.
In this post, we will demonstrate how to use column properties to ensure that expressions will remain intact in a Spotfire dxp even after changing a column name when replacing data.
Jason is a Junior Data Scientist at Ruths.ai with a Master’s degree in Predictive Analytics and Data Science from Northwestern University. He has experience with a multitude of machine learning techniques such as Random Forest, Neural Nets, and Hidden Markov Models. With a previous Master’s in Creative Writing, Jason is a fervent believer in the Oxford comma.
