Ok, great thanks, I will try it out very soon
lundeberg
@lundeberg
Posts made by lundeberg
-
RE: JS-report Studio - Reports menu item from settings menu vs GET//odata/reports
-
RE: JS-report Studio - Reports menu item from settings menu vs GET//odata/reports
Thanks Jan!
Short-term I have no issue to use fs-store, however long-term I am interested to see that postgres-store works as well -
RE: JS-report Studio - Reports menu item from settings menu vs GET//odata/reports
Hi again! I am using Postgres store and fs store. I did an export, reconfigure my dev server to use fs store and imported the setup. Now it works, so the issue is definitely connected to Postgres store!
Please note that scheduling does not work in Postgres store neither, so I guess I should use fs store until the bugs are fixed in Postgres store. One issue that seem to be the same regardless of store is that I cannot schedule reports using the time fields (grayed out and cannot be filled), but the expression field is working but is not as user friendly. Is this a know issue
-
RE: JS-report Studio - Reports menu item from settings menu vs GET//odata/reports
Thanks for the very fast response!
I am using macOs and doing F5 does not seems to refresh the reports page in neither Firefox nor Safari. I tried to clear all caches in Safari with no difference in response -
JS-report Studio - Reports menu item from settings menu vs GET//odata/reports
Hi!
Choosing the "reports menu" item from settings menu in JS report studio , does not show any data in the web browser, but the api callGET http://x.0.y.z:5488/odata/reports for the same user gets, what I believe is the same information that should be shown above.
Am I missing something or is this a known issue?
Regards
Micke