Problem & Motivation
Recently I’ve faced a challenge of finding fully customizable and easy-to-integrate web components which can se...
For further actions, you may consider blocking this person and/or reporting abuse
Thank you for the feedback and sharing your thoughts about Google Charts from the professional point of view, it was interesting to know about such limitations.
Maybe you could tell about experience with other charting libraries that are suitable for Angular and don't have such drawbacks?
Great article, thanks!
Thank you! I'm glad you've read it and appreciated. Hope you'll like this kind of visualization :)
Hello Nika! Your article is great and very complete, but it seems like the flexmonster license is expired so I couldn't get deeper into the codesandbox example :(
Hi! Thank you for your feedback!
I've changed the trial key in the demo, please check it out :)
On average, how long did it take to develop this reporting module?. I am working on creating one with a NOSQL approach
As you see, the front-end part of the application is quite easy to set up: you can create a dashboard in less than an hour.
The true complexity hides in the logic of your project, namely how the data is transferred between the back end and front end. The time of implementation may vary from several days to weeks.
If you're creating a reporting module with the MongoDB database as a data source, I'd recommend you try the server-side connector released by the Pivot Table team. The only thing you need to do is to install this connector at your data layer. Its advantage is that it pre-processes the data from the database on the server side and sends already aggregated data to the component on your front end. Thus, if you have a lot of data, this saves your resources from being exhausted by client-side calculations.