Could not parse XML input
Hi there, When I was trying to copy a project this morning. A strange error happened. There is an error message that flashes so quickly I can't read it. In the end, it leads me to a page say...
Forum Discussion
Hi Austin,
Thank you very much for analyzing the problem. Thanks!
I am not comfortable with JS. I've asked a friend to help me, in your way. We don't have enough time to dig deep. But we are close.
It seems that the code can't read the model record ID#, or can't create a new ID#. ..............Something is wrong here.
We will keep looking it over the weekend and hope to solve it.
Thank you very much for analyzing the problem. Thanks!
I am not comfortable with JS. I've asked a friend to help me, in your way. We don't have enough time to dig deep. But we are close.
It seems that the code can't read the model record ID#, or can't create a new ID#. ..............Something is wrong here.
We will keep looking it over the weekend and hope to solve it.
- 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
------------------------------- The new community is very strange. I don't like some of the changes like not being able to expand posted pictures any longer.
That makes sense, XML does not like that character. If you have the ability to process the data at all before sending you could use regex to replace & with & which is the way XML expects it. It doesn't always work but it should work.
A hidden field? Is it just hidden on the form from most users or is this a built in field that you did not create?
The field itself is not XML. It is just that QuickBase uses XML pretty heavily for the API so somewhere in that code there might actually be an issue. Without seeing the code I can't say where the issue is exactly. Somewhere in there a conversion is happening, either from or to xml and an error should be thrown. It could be in the way it is importing it or it could be in how it is reading the fields from QuickBase. I wish I could be more help in finding the exact bug.- Thank you very much Austin,
Sorry it's been a while.
It's hard to find my own post in this new community version.
Yes, this is a field that created by others and was hidden because it's not necessary anymore. But they still keep the field since there are some data they want to keep.
Thanks for your explain. Next time, I would know where to debug and fix. For now, I will just leave it be.
thanks
------------------------------
Ning Li
------------------------------
