2.0.0 vs 2.1.0 -- different initial loading behavior

[MattVoda]

Hi Keshia,

Happy Halloween! So today I did some deep testing of v2.0.0 and v2.1.0. We're using DDP to pull in a new most-recent data date, from an extract, on dashboard load. To test it, I've followed this process:

• publish identical dashboard versions using DDP 2.0 and 2.1 to our Tableau server with the most-recent date displayed prominently
• update the most-recent date (in our database) that DDP is watching for
• run an extract for the most-recent date datasource, to include the database change
• refresh each dashboard, hoping DDP has caught the new most-recent date and has set the parameter accordingly on-load

I also made sub-versions with and without 'reset values on load' -- I'm not sure how this setting is intended to be used so I wanted to see if it changed anything.

It seems that 2.0 will pick up this sort of data change, but 2.1 will not - at least not on dashboard-load. Can you reassure me that this behaving as intended? Does only 2.0 check for / populate new values on-load? Looks like 2.1 supports other hooks for checking, like parameter change, so perhaps the focus has shifted there. If so, just wanna mention that we find the immediate-check very useful and have built it to be the beating heart of our dashboards!

--Matt

[KeshiaRose]

Hi Matt,

You should be using the "Automatically reset values on dashboard load" option. This will set the dropdown to whatever is at the top of the list on load. When you set that option does it work for you? My testing shows it is working correctly. Were you not using this option before?

Take care, Keshia

[KeshiaRose]

Closing this, please re-open if you are still dealing with this issue.