Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Uploading of responses for an adaptive model using CSV fails

SA-17857

Summary



User has tried uploading responses for an adaptive model from Adaptive Models Management landing page using CSV file. User has suspected that when CSV record(cell) has formatted text such as Enter or Tab characters then a new record was getting inserted and also inappropriate warnings was displayed.

Error Messages



Not Applicable.

Steps to Reproduce



1) Launch Adaptive Models Management landing page.
2) For any existing adaptive model try uploading responses using CSV. 
3) After uploading, click Next. 


Root Cause



Issue was caused due to the invalid data in the CSV file being uploaded.

Resolution



Headers in CSV file have to confirm to the Pega 'identifier' standard - as they are based on the predictor Property names of the class of the Adaptive Model (AM) rule to which the CSV is being uploaded. 

User is advised that they cannot have dots or spaces in Property names, so these are seen as invalid, unless they have defined a predictor on the AM rule on a nested property, for example, MyPage.MyTestProp. In this case, there were no such properties, so the warnings were thrown. 

In addition, user can neither have spaces in property names nor in CSV headers which is why the warning was showing during the CSV file upload.

After removing the dot from the column header for the single valued property the warnings went off as informed above.

 

Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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

Pega Community 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
Contact us