Forum Discussion
ChayceDuncan2
7 years agoQrew Cadet
Yes - your best approach will be to use a Webhook in this instance and have it triggered when your trigger field changes. Your XML request is actually copied in the link you provided, I tweaked it a little to bring it up to today - you would simply expand it for all the fields where I stopped
<qdbapi>
<usertoken>usertoken goes here</usertoken>
<rid>[record_id]</rid>
<field fid="6" filename="delete"></field>
<field fid="26" filename="delete"></field>
<field fid="27" filename="delete"></field>
**<insert the rest of your fields here>**
</qdbapi>
For more detail - the above is what you would put in the 'Message Body' - as the detail for what you want to do
Your endpoint URL would be the table in which you're doing the edit record, so probably the same table the webhook is in
HTTP Method is POST
Message Format is XML
Your message header would be
key: QUICKBASE-ACTION
value: API_EDITRECORD
Chayce Duncan | Technical Lead
(720) 739-1406 | chayceduncan@quandarycg.com
Quandary Knowledge Base
<qdbapi>
<usertoken>usertoken goes here</usertoken>
<rid>[record_id]</rid>
<field fid="6" filename="delete"></field>
<field fid="26" filename="delete"></field>
<field fid="27" filename="delete"></field>
**<insert the rest of your fields here>**
</qdbapi>
For more detail - the above is what you would put in the 'Message Body' - as the detail for what you want to do
Your endpoint URL would be the table in which you're doing the edit record, so probably the same table the webhook is in
HTTP Method is POST
Message Format is XML
Your message header would be
key: QUICKBASE-ACTION
value: API_EDITRECORD
Chayce Duncan | Technical Lead
(720) 739-1406 | chayceduncan@quandarycg.com
Quandary Knowledge Base
- JordanMcAlister6 years agoQrew CaptainHi!
I am revisiting this after having to hold off on it to do some other things, but after setting it up, it doesn't seem to be working through the way I need it. So, the status change happens in another table. There's the work request table that hold records of poles from the poles table then there's the field work table that hold the field data for poles. It is set up this way because all these tables weren't set up at the same time.
The way I have it set up right now is that when the status changes to a specific value in the work requests table then I have an automation set to check a checkbox within the field work table which is where the pictures of the poles I want to delete are and where the webhook is located. The webhook works if I manually check the checkbox in the field work table, but it doesn't work if the automation changes the checkbox.
Any suggestions?
------------------------------
Jordan McAlister
------------------------------