Hi @brandon4,I see - that makes sense. Unfortunately as Dawid says, there isn’t a way to bring table calculations ahead of measures in the plotting order. The two ways around it would be to either (1) rewrite the measures as table calculations which,...

Hi @dingo, thanks - that makes sense. @IanT makes a good suggestion for this in that case!

Hi @brandon4 ,As a workaround, you could add in some table calculations that exactly match the measures that you’ve already brought in, and then hide the original measures from your visualisation. Then you can move your trailing 12 month average tabl...

Hi @dingo ,Are users going to be doing this from an Explore? If so, it should be possible to achieve this through the Explore filters. Clicking on the + button on the right-hand-side of a filter adds an additional line on that filter with OR logic, e...

Hi @matthewc ,It sounds like you could achieve this by first creating a measure to calculate the first visit date of an account, e.g. (update according to your dimension names): measure: first_visit_date { type: date sql: MIN(${visit_date}) ;; }And t...