Support for Multiple Dashboard JSON Files

MK-R-J

Hi, support member!

In the Portal application, Dashboard currently managed with a single Dashboard.json.
When there are multiple teams developing applications, having to edit, add, and manage the contents within one Dashboard.json becomes cumbersome.
If possible, would it be feasible to load all files under variables/Portal?
variables/Portal
├ A-Dashboard.json (contains A-Dashboard)
├ B-Dashboard.json (contains B-1-Dashboard / B-2-Dashboard)
└ ...

Portal screen – Menu:

A-Dashboard
B-1-Dashboard
B-2-Dashboard

Lukas Giger

Hi MK-R-J,

Just to let you know, the entire Portal team is currently on holiday because of Tết. So, don't expect an answer from them any time soon. I will forward your question to them so they can take a look as soon as they are back.

Kind regards,
Lukas

MK-R-J

Lukas Giger

Thank you for your reply.
I understand that it will take some time to provide an answer.
That is not a problem for me.

Have a nice vacation!

lmluat-axonivy

Hi,
We understand your current situation.
Portal uses a single Portal.Dashboard JSON file to allow multiple public dashboards to be defined in one place by the admin of the application. This approach simplifies management, deployment and migration.
Using separate files is not a good approach at the moment, but we'll keep it under consideration.
Thank you

MK-R-J

lmluat-axonivy

Thank you for your reply!

In AxonIvy’s Portal, we understand that, from an operations and management perspective, it is preferable to have the Dashboard.json managed as a single file.

However, from the standpoint of application development, I believe that having it split into multiple files would make development easier.

Therefore, I would appreciate it if you could consider providing a feature that allows users to choose between a single-file approach and a multi-file approach for managing Dashboard.json.

Thank you!