When in the testing phase I was using a copy of the production file in QBOnline, and everything worked smoothly interacting with CustomFields.
But now that I’ve switched over to the production environment CustomFields are no longer available.
I’ve tried deleting and recreating QBO app connections in addition to recreating the Zaps that use them to no avail.
What changed such that these fields are no longer available via Zapier?
Best answer by SamBView original
Just recreated the original connection to the demo account mentioned above, and the original custom fields are showing again, but the production account’s custom fields are still not propagating through.
Is this an issue with:
Need a solution or I’ll have to develop something in GCloud for this.
Thanks in advance,
Created a brand new and seprated zapier demo account, connecting directly to the production QBO file, and this is still an issue… so #1 or #3 doesn’t seem to be the issue above.
Could there be a bug with Quickbooks Online Advanced, Zapier not supporting custom fields with this version?
Looks like the issue maybe with backward/forward compatibility between version of QBO, namely Plus vs Advanced.
A custom field will be shown in the API response only if:
The mapping of the first three custom fields will be Immutable, i.e. even if the first three fields are marked as 'Inactive' in QuickBooks Advanced, they will still continue to be mapped in the API response.
For details refer to this link:
To verify this from QBO UI:
Those fields that get exposed to the API are only the first three created with type String, even if they get deactivated!
This is related the issue being discussed in this other thread:
So I’m going to close this thread so that we can better track who is affected by this issue in the other thread. As you’ve already been added to the bug report mentioned on that other thread we’ll be in touch as soon as it’s been resolved. :)