Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validate order of elements #14

Open
JasonBarnabe opened this issue Jan 31, 2015 · 3 comments
Open

Validate order of elements #14

JasonBarnabe opened this issue Jan 31, 2015 · 3 comments

Comments

@JasonBarnabe
Copy link
Contributor

QuickBooks doesn't like when things are out of order, but we're not validating that.

@jarederaj
Copy link

It would be nice if you used some kind of standard XML error response instead of a string that just reads "QuickBooks found an error when parsing the provided XML text stream."

This is basically like throwing a silent error and leaves me wondering what of a thousand things could be wrong with the xml... plus, why is an XML processor responding with invalid xml. It's fine if you don't want to validate it, but tell me that's what you're doing with your standard xml response.

@ruckus
Copy link
Contributor

ruckus commented Jul 8, 2015

I think its largely because qbxml cannot/doesnt validate the order of XML elements but QB/Web Connector does require specific ordering. Which, yes, is a huge pain in the ass and is totally lame.

The error text that you're seeing is not generated by qbxml but by the web connector.

The overall solution is to use the qb*xml validator tool which is shipped with the SDK (and only runs on Windows). It can be downloaded here:

https://developer.intuit.com/docs/0250_qb/0010_get_oriented/0060_sdk_components

@JasonBarnabe
Copy link
Contributor Author

I don't think there's any reason why qbxml couldn't validate the order of elements, but it currently doesn't. I would be happy to accept a pull request that changes this.

As @ruckus says the message is coming from web connector, and we're just passing it along...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants