mariobutler Member

I'm still getting the same behavior as of today. I'm also waiting to see if an update fixes this, because having to create variables over and over for each dataset and card would definitely be brutal.

I always save beast modes to the dataset because we only have a few people building cards in our organization. In the past, when I've created a new beast mode, all of the variables that'd I previously created (doesn't matter the origin) were available to me to use, and now none of them show up.

Yes, that'd be a great addition. But having to add the variable for each card now makes dashboard building much more tedious.

To add to this, variables that I've previously created over the last 2 years do not appear in new datasets at all.

The input datasets are only about 53k rows total, and the output is only 200 rows. I've run the 100k preview and 5M just for fun, and both are green checkmarks all the way through. We've had 2 magic ETLs with this behavior in the last 3 days, and we've never seen it before, so it seems like a backend error. Went ahead and…

The preview is running perfectly, which would indicate no structural or configuration issues. I am the owner of each input dataset. Also, it already ran successfully 40 times up until today, and I did not change anything.

There's an issue I'm facing with the relative date filters. I can change the configuration of it on the card level, but then that configuration is not applied to the rest of the cards on my app page or dashboard. I have to go to each card individually and save that configuration over whatever the default date variable was…