I tried to importing a data source with 3 records.
Flexmonster is not showing the exact data which i passed in data source.
Please suggest any solution to resolve this issue.
For your reference I’m attaching the data source i passed along with the view of flexmonster for my data.
I tried with both default provided in a flexmonster live example and requirement based adjusted configurations from our end, still in both ways data view is not matching.
Kindly verify and provide any approach to solve this.
Thank you for reporting the issue.
We will research the possible reasons for this behavior and provide you with the results ETA May 03.
As a temporary workaround, we suggest using the number formatting to truncate the value to the desired number of decimals. Please see the JSFiddle we have prepared for reference: https://jsfiddle.net/flexmonster/dmq9obwk/.
We hope it works for you.
Please contact us in case other questions arise.
Thanks for the quick response.
I don’t think the suggested workaround solution will suit our requirements.
If you don’t mind could please provide the proper solution quicker, because May 03 is a long time to wait.
And currently we’re using version 2.8.10, and whenever a new version comes we cannot manually change the version number. Is there any alternative way to update the version automatically in package.json file?
Thank you for your feedback.
Could you please specify why the workaround with number formatting is not an option for your case? It would allow us to search for another applicable workaround.
Concerning the given ETA, I would like to inform you that our estimated bug fixing time is up to 6 weeks for the Standard support option. As much as we strive to meet our customers’ needs more promptly, our hands are tied by our road map. Considering that it is full for the upcoming weeks, unfortunately, we won’t be able to deliver the fix earlier than the estimated time.
As for updating to the latest version, please see our guide to learn all possible ways to update Flexmonster: Updating to the Latest Version.
We rely on your understanding. Please contact us in case other questions arise.
Percentage column data cannot restricted to 4 decimals due to vary in values, it comes with more than 4 decimals also, so we’re just displaying the data as it is.
And we cannot change that data type to “string” because by doing so text will align to different side.
And we’re dealing with several kinds of data (dynamic data), for that we made flexmonster as common tool to view and this Percentage column may/maynot come so we cannot restrict it for this data alone.
Regarding flexmonster update, in package.json file we’re mentioning version number. However i seen somewhere instead of mentioning specific number something like “^update” / “^recent” which always consider recent version number.
Is there any above kind of process is available?
Thank you for providing us with detailed information about the use case.
We did not manage to find a suitable temporary workaround for you. Still, we will notify you as soon as the issue is fixed.
Concerning updates, you can specify which update types your package can accept from dependencies in your package’s package.json file. For example, updating to the npm patch releases (our minor releases) can be allowed with a
"~2.8.30". Updating to the npm minor releases (our major releases) can be allowed with a
^ prefix also updates the version to the latest patch.
After the new Flexmosnter version is released, update your package using the
npm update command.
For more information, we suggest referring to the npm documentation to learn more about the versioning process: About semantic versioning | npm Docs (npmjs.com).
We hope it helps.
Thanks for information. I will refer to NPM documentation and conclude.
Please try to provide the updated release a little quickly for the above mentioned decimal places issue.
Thank you for your feedback.
Concerning the update, please note that minor versions are released bi-weekly and cannot be rescheduled. The fix is planned for the nearest available minor release according to our road map. Therefore, we won’t be able to deliver the fix earlier than the estimated time.
Our team relies on your understanding.
Do not hesitate to contact us in case other questions arise.