Encountered some issues with integrating CUSTOM DATA SOURCE.

Closed
peng.w asked on November 15, 2023

1. Our system operates in a multi-tenant, multi-database mode. Different tenants may be in different databases, but the index is specified with a database connection string that can only query reports within a single database. It cannot retrieve reports from different databases based on different tenants.
2. The columns of the report are returned by the interface. How should multi-language support be configured?
3. In the demo, the API fields provided are all queried from the script. What operations are supported for the fields, whether filters and value filters are enabled, and what aggregation operations are supported – all these are hard-coded in the demo. How can these configurations be made more flexible?
Only after resolving these issues can we use Flexmonster Pivot Table.

1 answer

Public
Solomiia Andrusiv Solomiia Andrusiv Flexmonster November 16, 2023

Hello!
 
Thank you for reaching out to us.
 
Please find our comments on your questions below.
 
1. Our system operates in a multi-tenant, multi-database mode. Different tenants may be in different databases, but the index is specified with a database connection string that can only query reports within a single database. It cannot retrieve reports from different databases based on different tenants.
As a first step, our team wants to ensure that you are testing Flexmonster Data Server as a data source to connect to the databases. If so, we recommend specifying different indexes in the report.dataSource for different tenants. For that, you'll need to have all these indexes created separately in the Data Server. We want to kindly remind you that all the indexes in the Data Server are stored in the RAM of the machine where it is installed.
 
2. The interface returns the columns of the report. How should multi-language support be configured?
In Flexmonster, it is possible to specify the localization object, which contains all the labels in the necessary language. The localization object is configured as a part of the Flexmonster's report object. You can use one of our predefined localization files as well as create your own using our as a template.
Please look through our localization docs for more details: https://www.flexmonster.com/doc/localizing-component/.
Here is also our localization demo for visualization: https://www.flexmonster.com/demos/js/localization/. Please note that Flexmonster does not translate the data, only the labels.
 
3. In the demo, the API fields provided are all queried from the script. What operations are supported for the fields, whether filters and value filters are enabled, and what aggregation operations are supported – all these are hard-coded in the demo. How can these configurations be made more flexible?
You are right that all the options in Flexmonster are saved into the report JSON object. The report can be configured via the code as well as via the UI.
If you are interested in customizing the report, please look through our docs about configuring the report and let us know if there are any further questions: https://www.flexmonster.com/doc/getting-started-with-report/.
 
Here is also the YouTupe video, which shows how the changes in Flexmonster UI and report JSON object are related: https://youtu.be/GC4C7XLjccc?si=DfqcAuW5qk8-LZT6.
 
Hope you will find our answers helpful. Feel free to ask if any further questions arise.
 
Kind regards,
Solomiia

This question is now closed