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
{{ message }}
This repository has been archived by the owner on Nov 10, 2017. It is now read-only.
I have a customer model as well as sub-customer model.
I have two buttons named "sync customer" and "sync sub-customer". When a user click on "sync-customer " button I want to sync ONLY CUSTOMER from QBO to my customer model.
Similarly, "sync sub-customer" will sync ONLY SUB-CUSTOMER from QBO to my sub-customer model.
For now, whenever I am syncing customer from "sync customer" button it is pulling customer and sub-customers both in my same customer model.
There should be a CustomerTypeName property with a colon-delimited list. However, I just created a test sub-Customer in QB Online and when I fetch it using Quickeebooks I don't see that property. So I don't know how to determine if a customer is a sub-customer unless you have your own application logic/flag to determine that.
I see there is a:
<CustomFieldxmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:type="BooleanTypeCustomField">
<DefinitionId>Bill With Parent</DefinitionId>
<Value>true</Value>
</CustomField>
property set. But one can still set that to false even if it IS a sub-Customer - so thats not definitive.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I have a customer model as well as sub-customer model.
I have two buttons named "sync customer" and "sync sub-customer". When a user click on "sync-customer " button I want to sync ONLY CUSTOMER from QBO to my customer model.
Similarly, "sync sub-customer" will sync ONLY SUB-CUSTOMER from QBO to my sub-customer model.
For now, whenever I am syncing customer from "sync customer" button it is pulling customer and sub-customers both in my same customer model.
How to differentiate between them?
The text was updated successfully, but these errors were encountered: