-
Instructions to Ask a Question
Click on the "Ask a Question" button and select the application for which you would like to ask questions.
We have 5 different products namely - Pabbly Connect, Pabbly Subscription Billing, Pabbly Email Marketing, Pabbly Form Builder, Pabbly Email Verification.
The turnaround time is 24 hrs (Business Hours - 10.00 AM to 6.00 PM IST, Except Saturday and Sunday). So your kind patience will be highly appreciated!
🚀🚀Exclusive Discount Offer
Just in case you're looking for any ongoing offers on Pabbly, you can check the one-time offers listed below. You just need to pay once and use the application forever -🔥 Pabbly Connect One Time Plan for $249 (🏆Lifetime Access) - View offer
🔥 Pabbly Subscription Billing One Time Plan for $249 (🏆Lifetime Access) - View offer
-
1308 JSON is not well formed
- Thread starter GSG
- Start date
GSG
Member
Please see attached sequence of images (in chronological order) showing that with an existing contact already in Books, there is a failure to update that contact.
The workflow uses a router. Where the Contact ID does not already exist, the router employs 'Create a New Contact in Books', and this part of the router works (with a few anomalies - see below)
The main problem is with the other part of the router - where the Contact ID already exists in Books. When we try to Update the contact in Books, there is a json 1308 error.
I think the field for "Contact Name (Required)" is the problem. I am not sure why we have to add this field as the contact ID for the customer is already mapped above it in this step, so surely if the contact ID is populated, the update should go to the correct customer ID and the extra "Contact Name (Required)" field is redundant?
There are some other issues we have noticed. For example, where a Zoho Books customer does not exist and a new contact is created (the side of the router which does work), the fields for Books Custom Fields (final 2 screenshots) do not map correctly to the approriate fields in Zoho Books. For example the field for "Territory" is actually mapped by the field for "Code", and the field for "Customer Category" is actually mapped to "Shipping email"
Hope you can help out with this. It has me scratching my head!
The workflow uses a router. Where the Contact ID does not already exist, the router employs 'Create a New Contact in Books', and this part of the router works (with a few anomalies - see below)
The main problem is with the other part of the router - where the Contact ID already exists in Books. When we try to Update the contact in Books, there is a json 1308 error.
I think the field for "Contact Name (Required)" is the problem. I am not sure why we have to add this field as the contact ID for the customer is already mapped above it in this step, so surely if the contact ID is populated, the update should go to the correct customer ID and the extra "Contact Name (Required)" field is redundant?
There are some other issues we have noticed. For example, where a Zoho Books customer does not exist and a new contact is created (the side of the router which does work), the fields for Books Custom Fields (final 2 screenshots) do not map correctly to the approriate fields in Zoho Books. For example the field for "Territory" is actually mapped by the field for "Code", and the field for "Customer Category" is actually mapped to "Shipping email"
Hope you can help out with this. It has me scratching my head!
Attachments
Hey @GSG
We have made a slight change in the Update Contact action step and it should work now. So, kindly give it a try now apart from that the contact which you are trying to update does not exist in your Zoho CRM we have checked it with the help of the "Get Contact" action step. So kindly try updating the contact with a new one.
We have made a slight change in the Update Contact action step and it should work now. So, kindly give it a try now apart from that the contact which you are trying to update does not exist in your Zoho CRM we have checked it with the help of the "Get Contact" action step. So kindly try updating the contact with a new one.
Similar threads
