Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Hari Jetti (HJetti)
IP Australia
Pega Consultant
IP Australia
AU
HJetti Member since 2011 17 posts
IP Australia
Posted: Mar 28, 2017
Last activity: Mar 31, 2017
Posted: 28 Mar 2017 7:56 EDT
Last activity: 31 Mar 2017 6:14 EDT
Closed

Invalid escape sequence - Service File rule

Hi there,

We are implementing a service file rule with a comma separated csv file. The file contains 3 columns where each value is specified in quotes. For example ["value 1","Value 2", "Value 3"], now when running service file following error is coming. If the 3rd column value not specified in quotes then no issue.

com.pega.pegarules.pub.PRException: Error while parsing: Invalid escape sequence. Escape character must be followed by either field delimiter, or record delimiter, or another escape character.

Please advice if anyone come across such issue. We are using Pega 7.2.2 version

Thanks,

Hari Jetti

***Updated by moderator: Lochan to update Categories***

To see attachments, please log in.
Case Management
System Administration

Posted: 7 years ago
Posted: 29 Mar 2017 20:02 EDT
Hari Jetti (HJetti)
IP Australia
Pega Consultant
IP Australia
AU

Hi Mahesh,

We had tried this by keeping $ at the record terminator and it works fine, but the file is received for an external source and they are not happy to introduce new terminator

Thanks,

Hari Jetti

To see attachments, please log in.
Posted: 7 years ago
Posted: 31 Mar 2017 6:14 EDT
Shanthini Charles (ShanthiniC)
Techmahindra

Techmahindra
IN

Hi Hari,

For a file to be read and parsed a record terminator is mandatory. Have you used delimiter \n and record terminator \n without adding $ to file ?

Regards,

Shanthini Charles

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice