When extracting a case data to csv file, we have few properties which contains comma(,) in it and during extraction pega extracting these property values into 2 different cells , value before comma(,) into one cell and value after comma(,) into another cell, because of this the file format is changed and different column headers are holding wrong values, how to fix this?
any solutions would be well appreciated…!!!
Thanks in advance…!!!
@AnjaneyuluG Pease can you carry out a PSC search for key words 'CSV extract’ and you should be able to find several posts as well as the below support documents:
BIX generates CSV files with additional unwanted rows and columns
Troubleshooting BIX for on-premises environments
When extracting case data to a CSV file in Pega, if some properties contain commas, they can be misinterpreted as separate fields. To handle this, you can use a different delimiter, such as a semicolon or a tilde, instead of a comma. This can be done by adding the -l parameter when running the extraction process. This will ensure that property values containing commas are not split into separate cells, preserving the correct format of your CSV file.
The articles found on the PSC search should help you avoid the scenario you describe.
This is solved by passing the pyArgs Parameter as “-l ","”