Topics created by AlexGoris-KasparSolutions

If I apply this setting to the docx file generated by the jsreport report, the table is fixed and starts on the first page.

i've tried to follow these steps using the output docx of your playground, but i don't get the same result as you, the table always stays at the second page, any clue if there is another way to do it?

GIF that shows what i am doing: https://jumpshare.com/s/YfZouzTWwR03XfeRArCK

Thank you for sharing your workaround. I've included it in the documentation.

Thanks for all the great feeback @bjrmatos!

I indeed overlooked the group permissions. This completely fixes that point I made.

The feature to be able to map users to groups works perfectly, and combined with the group permissions, eliminates a lot of situations where the team would previously had needed admin access (and having to resort to using the shared credentials), like adding a new request under a specific group, or granting a new user access.

Thanks again, it's so nice to use a product which ticks all the boxes :)

But are you sure that it's broken? Because I do see (development) in the license modal when looking in studio

Because of the bug, the server thinks it runs in the production, but the studio thinks it runs in the development.

Just for my information, is there any restrictions in the API when this license verification fails?

I believe you mean when the parallel usage check fails. There are no limitations. Just the warnings you see. Everything runs the same.

Perfect - that's worked.

Looks all good as far as I can see.
What are the jsreport logs saying when you try to login?
I would try intercepting the access token returned by keycloak so you can inspect it for the username claim