You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I must +1 this, We discussed this a bit offline and think that either raising an exception or a warn message in a logger is pretty critical if non parsable data is being passed in.
I think it will let individuals be able to crush bad QBXML before they loose there mind. Because lets be real... we are not Quickbooks expert... some client just said ... can we integrate with quickbooks and we unwittingly said yes.
This is even ignoring ones that are defined on the schema so this is now even more important -.- when trying to call ItemInventoryAddRq it barked at me cus' i didn't specify some fields, one of which was COGSAccountRef, after adding it, it still complained and then i noticed the field wasn't in the resulting XML
so i guess i'll probably be working on this one soon
Currently if you send a hash to hash_to_obj and it doesn't understand part of it, it just ignores it, it'd be nice if it logged it somewhere
The text was updated successfully, but these errors were encountered: