1. Create a provider to an empty DB.
2. Create KPI to that DB.
3. Fill DB while the application is running.
4. Edit KPI again. You'll see the KPI still shows a message indicating there's no data.

Note that if previous data existed in the DB this would be hardly noticeable, since usually data is not relevant for KPI composition. In view mode everything works as expected.

The underlying reason is the edit KPI is using the global dataset manager instead of the per-session one.

The fix is to initialize properly the thread local settings in the edit kpi jsps.