Is this an example of the actual payload that is failing?
Did anything change with the structure or did you add any new fields recently? Your file fields are mixing ' and " in the same input which probably isn't the issue but stood out.
Hi Chayce,
I am using a software called Alteryx to parse my data and pull out of SAP to figure which line items need to be added to my Quickbase app. That software needs me to use the inverted commas in that fashion to make it work.
I have not added any new fields...as you can see all the fields I am trying to add data to in the QB app, have an FID#. This morning, the API_Add call went through properly and added a record in QB. But just this one from Feb 27th (entry date) did not make it through.
Would like to depend upon the API calls to create the records and not miss any. Hence, want to understand why this line failed to load into QB and yes....that is the actual payload that is failing...just x'ed out the names and emails and user token.
Thanks!
It appears I forgot to mention the exact error I get.
Here it is...
| <?xml version="1.0" ?> | |
| <qdbapi> | |
| <action>API_AddRecord</action> | |
| <errcode>11</errcode> | |
| <errtext>Could not parse XML input</errtext> | |
| <errdetail>XML Parsing Error. unclosed token at line 1 column 907 (which is byte 908)</errdetail> | |
| </qdbapi> | |
So I tried to find the 907th byte...and that is the very last part of the payload. 907+ remaining bytes shown below.
| ></qdbapi> |
So confused.
In the data you've omitted, do you have any special characters like & or < in any of the inputs? If it worked prior, then with no changes to the API call it sounds like there is something in the actual data that is being interpreted in the XML and corrupting the payload. For example having & typically has to be escaped as & - do you have any occurrence of invalid characters anywhere in the example that is failing?
