Could not parse XML input

What add-on are you using?

It sounds like there is an error with the addon. This could be caused by either the add-on or possibly your schema or fields if they have changed at all. It really depends on the add-on and what it is trying to do. If you can say which add-on it is I can try and help you out.

Thank you very much. Austin. 

It's a Config.js program, embedded in Home page setting / "Page". 

It's look like this:  

var APPTOKEN = "dwnt9wipc3cvfcg6nvd****ps4";
var userIDs = new Object();

var tblProject = "bjtm***m9";
var tblProjectFields = new Object();
tblProjectFields['PrimaryKey'] = 3; 
//CLIST BUILDER
tmpFields = new Array();
for (el in tblProjectFields) 
tmpFields.push(tblProjectFields[el])
var tblProjectCLIST = tmpFields.join(".");
delete tmpFields;

So it creates a csv of the entire table or possibly a record and then it tries to import it somewhere else.

Without seeing all of the code and the exact record you are having issues with it is hard to say. If it is erroring on just the one record then my guess would be there is a character in there that it was not ready to handle. Do you have any abnormal text characters in any of these records?

The way I would go about it is adding a console.log to the right place in that code and seeing the exact xml it is trying to import. That way you can get a look at what it is trying to import, it might help to debug it. You might also be able to see the XML inside of the Chrome developer console but I forget exactly how, possibly in the network tab. That would be the easier way.

If you are not comfortable with JavaScript you might need to contact the people who you got the script from. It is hard to debug without seeing all the code or the exact record it is failing on but if you do the stuff above it should give you a better idea I think.

Hi Austin, 

It took me a while to used to this new community page. 

Just want to update you that I have solved this problem.  It's nothing related with the coding. In the end, I found there is a hidden field with a special character "&" which is not allowed in XML. Thanks again for your suggestion. It really helps!

My following question is I don't understand why this filed is a XML field?  If next time, I need to add a new field, from where and how I can avoid using a XML field. 


Thank, 
Ning 
 


------------------------------
Ning Li
------------------------------