How to use different separator for flex monster compressor data rather than default comma separator

Hello, Manoranjan,

Thank you for writing to us.

If you are compressing the data from the database, Flexmonster Compressor does not need any fieldSeparators specified. In case you want to compress CSV file that contains ‘~’ as a separator, it can be specified as a second argument:

InputStream compressFile(String fileName, char delimiter)

Alternatively, for strings in CSV format and streams:

InputStream compressString(String string, char delimiter)
InputStream compressStream(InputStream inputStream, char delimiter)

Please let us know if it helps.

Regards,
Tanya

Hello, Manoranjan,
 
Thank you for your reply and for sharing a code sample.
It helped us a lot to understand the problem with preformatted numbers better and reproduce it on our side.
 

As a result, we noticed that the issue occurs when the decimal separator is ",".

Our team is currently working on a solution to this issue and the fix will be available in the minor release with the ETA May 6th.

 
We kindly advise passing raw (not preformatted) data to Flexmonster Compressor. 

Please note that raw number data can be formatted on the client side in Flexmonster via the thousandsSeparator and decimalSeparator option in the formats parameter.
This can be achieved the following way:

"formats": [
             {
               "name": "2sfou03a",

               /* SET DESIRED SEPARATOR FOR THOUSANDS */
               "thousandsSeparator": ",",

               /* SET DESIRED SEPARATOR FOR DECIMALS */
               "decimalSeparator": ".",

               "decimalPlaces": 2,
               "currencySymbol": "$",
               "positiveCurrencyFormat": "$1",
               "nullValue": "",
               "textAlign": "right",
               "isPercent": false
             }
]

 
 
We have prepared a few JSFiddle examples for illustration:
 
1) In this JSFiddle example, it is shown how the number format can be predefined in Flexmonster via the formats parameter.
2) In this JSFiddle example, you can see how the number format can be changed during runtime.
 
Could you please provide more information on how and where you get your data? It would greatly help us.
 
Please let us know if passing raw data would work for you.
 
We are looking forward to hearing from you.

Best Regards,
Vera

Hello, Manoranjan,
 
We are glad to inform you that the issue with compressing numbers with comma as decimal separator in Java is fixed.
The fix is available on our website in the minor release 2.7.5 of Flexmonster.
You are welcome to update the component.
 
Please let us know if everything works fine for you.
 
Best Regards,
Vera

Hello, Manoranjan,
 

We would like to note that Flexmonster Data Compressor also needs to be updated.
Here is a link to how it is done: https://www.flexmonster.com/doc/updating-to-the-latest-version/#!compressor

Best Regards,
Vera

Hello, Manoranjan,

Thank you for writing to us.

There are a couple of things we'd ask you to check in order to fix this issue.

1. We have noticed that the screenshot called flexmonster_op.png pictures the Data Compressor with version 2.312. Our team kindly suggests updating the Data Compressor to the latest version.
2. The second point is how your OCSV output looks like. Your CSV file has ~ as separators:

   +Customername~Order Year
   Atelier graphique~"2,003"

   Such a file should be compressed by specifying this custom separator:

   InputStream inputStream = Compressor.compressFile(destPath,'~');

   The response from the Data Compressor should look the following way:

   ___ocsv2___2.7.6/2.213
   +Customername,+Order Year
   Atelier graphique,2%d%003

   Please note that ~ is replaced with , in this response. However, the comma inside "2,003" is represented as %d%. This allows Flexmonster to interpret this comma as comma displayed on the grid, not the field separator.

   We suggest making sure your OCSV response looks the same as shown above.

Please let us know if the issue is resolved.

Regards,
Tanya

Hello, Manoranjan,
 
Thank you for writing to us and for providing a screenshot for illustration.
 
We have managed to reproduce the issue on our end.
 
The problem is that the ~ in the ocsv output were supposed to be changed by the Data Compressor to ,.
 
Our development team is working on a solution to the problem and the fix will be available in the minor release with the ETA 18th of June.
 
One more suggestion we recommend applying right now is adding the data types to the CSV data you pass to the Data Compressor.
This means that your CSV header should contain types.

Header without types:
Customername~Order Year~Sale Price

Header with types:
+Customername~+Order Year~-Sale Price
 
Feel free to contact us in case any questions arise.
 
Best Regards,
Vera

Hello,  Manoranjan,
 
Thank you for writing to us.
 
At the moment the custom delimiter is being ignored (that is why the OCSV output is not correct). The fix which is currently in progress should resolve this issue.
 
Please note that adding the types to your CSV header is also a necessary step towards fixing the issue.
 
You are welcome to contact us in case of any questions.
 
Best Regards,
Vera

Hello, Manoranjan,

We are glad to announce that the issue with setting custom delimiter for compressing CSV files was fixed.

This is available in the 2.7.8 version of Flexmonster: https://www.flexmonster.com/release-notes/

You are welcome to update the component: https://www.flexmonster.com/doc/updating-to-the-latest-version/ 

A kind reminder is to update Flexmonster Data Compressor also: https://www.flexmonster.com/doc/updating-to-the-latest-version/#!compressor 

Please let us know if everything works fine.

We are looking forward to hearing from you.

Best Regards,

Vera

Hello, Manoranjan,
 
 
Thank you for writing to us and providing test data to understand the problem better.
 
We would like to point out that the - data type prefix specifies that the type of data provided in the specified column will be of type value (number).
In order for it to be recognized as a dimension (string), the + data prefix needs to be added to the column name instead.
 
Please change the data type prefix for the Order Year in the CSV header from - to +:

...,+Order Year,...

After this, Order Year data should be displayed in Flexmonster as desired. 
 
 
Please let us know if this works.
 
 
We are looking forward to hearing from you.
 
 
Best Regards,
Vera

Hello, Manoranjan,

 
It seems there may be some sort of misunderstanding so let's clarify some points.
 
As we understand, Order Year values must be of type number.
Values, such as Sale Price, must be displayed in Flexmonster on the grid with , as the thousands separator.
 
Could you please confirm whether the Order Year values must also be displayed in Flexmonster on the grid with , as the thousands separator?
 
 
Please note that Flexmonster Data Compressor needs to be given raw data without number formatting, otherwise the results can be unexpected.
 
The recommended approach is to pass data without number formatting: 

+Customername, -Order Year, -Sale Price, +Status, -Customernumber
Atelier graphique, 2003, 3138.46, Shipped, 103
Atelier graphique, 2003, 5282.64, Shipped, 103

And then apply number formatting with Flexmonster.
 
We would like to bring to your attention that Flexmonster provides the ability to set number formatting, such as thousands separators.
This means applying custom number formatting rules can be done on the client side. 
 
For example, you can pass the 4515905.51 Sale Price value to Flexmonster. Then you can specify the formats parameter in Flexmonster the following way: 

"formats": [
     {
       "name": "", //since name is not specified, the format will be applied to all values
       "thousandsSeparator": ","
     }
]

 
As a result, 4515905.51 will be displayed as 4,515,905.51 in Flexmonster.
 
Here is a JSFiddle for illustration: https://jsfiddle.net/flexmonster/5hdcqs10/.
 
 
Please let us know if we understand your case correctly.
 
We are looking forward to hearing from you.
 
Best Regards,
Vera

Hello Manoranjan,
 
Please see my reply via email.
 
Regards,
Kate

Hello, Manoranjan,
 
Thank you for providing a detailed description of the desired component behavior.
 
We would like to kindly mention that the formatting of members on the frozen area and in the filter pop-up is not supported by Flexmonster.
 
Please let us know if any further questions arise.
 
Best regards,
Milena