Example of Message body for API_DoQuery Webhook
Can someone provide an example "Message Body" for an API_DoQuery Webhook, I'm lost on how the fields get populated from the XML reply and I'd like to see the structure of the code.
Forum Discussion
Is this a production app currently? And do you know what the key field in your contacts table currently is?
Option 1 - If possible - the ideal solution would be to change the key field of your 'Contacts' table to be the 'Email' field. If done that way - you could automatically relate your contacts your 'Sales' table as you called it - but making the email brought in via your front end system as the reference field. Basically if your contacts were unique by Email - your 'sales' data could auto-relate. However - if this app is in production and your contacts are widely used - this approach should be taken with caution as changing keys late in the game comes with risks.
Option 2 - if you have an integration tool like Workato - you could have a secondary process in that tool to do what I now see you were trying to do with the DoQuery - and have a background process that relates your new 'Sales' to the appropriate person.
Option 3 - if you're familiar with a development language - you do the same thing as in option 2 - but just script it into a Quick Base code page - and have someone click a button to sync your data via Javascript, or write a background job to do in a server language like Ruby or Node as another option.
There is a 4th option - but its very hacky for lack of a better word in this case - and works only in very fringe cases of Quick Base. When you are bringing in data from your front end system - is it being brought in one by one? Or in mass - meaning lots of records at once.
I'm happy to elaborate on any of the above as well if you want more info.
Chayce Duncan | Technical Lead
(720) 739-1406 | chayceduncan@quandarycg.com
Quandary Knowledge Base
Option 1 - If possible - the ideal solution would be to change the key field of your 'Contacts' table to be the 'Email' field. If done that way - you could automatically relate your contacts your 'Sales' table as you called it - but making the email brought in via your front end system as the reference field. Basically if your contacts were unique by Email - your 'sales' data could auto-relate. However - if this app is in production and your contacts are widely used - this approach should be taken with caution as changing keys late in the game comes with risks.
Option 2 - if you have an integration tool like Workato - you could have a secondary process in that tool to do what I now see you were trying to do with the DoQuery - and have a background process that relates your new 'Sales' to the appropriate person.
Option 3 - if you're familiar with a development language - you do the same thing as in option 2 - but just script it into a Quick Base code page - and have someone click a button to sync your data via Javascript, or write a background job to do in a server language like Ruby or Node as another option.
There is a 4th option - but its very hacky for lack of a better word in this case - and works only in very fringe cases of Quick Base. When you are bringing in data from your front end system - is it being brought in one by one? Or in mass - meaning lots of records at once.
I'm happy to elaborate on any of the above as well if you want more info.
Chayce Duncan | Technical Lead
(720) 739-1406 | chayceduncan@quandarycg.com
Quandary Knowledge Base