Persisting Data

[gerrybartley]

I'm currently migrating a large project from Dashboard 1 to Dashboard 2. I've noticed when I navigate from a page and back again, dropdown control has lost it's selected value, and chart and gauge controls don't maintain their values. This is different behaviour to Dashboard 1. Is this the expected behaviour? If so how do I refresh the data without the user having to make a selection again?

regards Gerry

[joepavitt]

Hi Gerry - that's not expected behaviour, and not something I can reproduce here.

The only thing I can think of is that you've setup authentication/client data with Dashboard? Do you have any of the following ticked for the respective chart types? If so, that will prevent persistence of the data in our central store.

[gerrybartley]

Ok. I understand now. I have Include client Data ticked and also ui-dropdown, ui-chart and ui-gauge. However, this was the main reason I wanted to migrate to the new dashboard, so that control selection wouldn't update for all users. So I guess I need to use ui-event or other means to set a default selection when the user migrates to the page to trigger my Database query.

Appreciate the quick response

[joepavitt]

@gerrybartley

. So I guess I need to use ui-event or other means to set a default selection when the user migrates to the page to trigger my Database query.

Exactly that! Thee two core design patterns detailed here may help the understanding too.

We can't store data for every individual automatically server-side, it just can't scale to store it in memory and too many variations to consider for any unique identifiers for a given users, so we need to leave it to the NR users to cover it.

The database/ui-event combo is exactly what we'd recommend though

[gerrybartley]

Hi Joe
That should work for my main use case which is non-interactive screens scrolling between different pages displaying current metrics for different areas of the factory. Keep up the good work

regards