Slice versus Virtual Column Performance

There are many ways to skin a cat.  One question that comes up for me fairly frequently is using Slices vs. Virtual Columns to evaluate expressions that result in true/false against an entire table when I want to re-use that expression. 

For example, if I want to run a data action for a subset of a table that matches some expression, I can put that expression directly in the "Only if this condition is true" field.  But if I want to re-use the same expression in multiple data actions and other places across an app, it can be cumbersome to maintain.  Alternatively, I can create a virtual column that evaluates the expression and just stick my [Virtual Column] in the "Only if this condition is true" field.  Or I can put the expression into a slice and limit the data action to the slice.  Both solutions clog up other parts of the management screen with unnecessary options, but is one faster?

1 18 1,222
18 REPLIES 18
Top Labels in this Space