Skip to main content
Question

Webhook bug Where is it Pointing To?

  • September 11, 2017
  • 0 replies
  • 56 views

I created a webhook but I have almost forgotten where it is writing the info to?  I do have bug report: 

400 Error: API_Addrecord 34 You cannot change the value of this field The field named "Projected Finish" with field id 10 cannot be modified

But if I were to resolve it I need  to find the app it is going to. Following is the webhhok code: 
<qdbapi>
<usertoken>by7rxw_fj4j_bbvkw8hdquqasxbprgub8d6pwk4i</usertoken>
<field fid="7">[Project Name]</field>
<field fid="8"></field>
<field fid="9">[old.AFC Current] --> [new.AFC Current]</field>
<field fid="10">[old.Budget] --> [new.Budget]</field>
</qdbapi>
This topic has been closed for replies.

Thx app it's going to is speciified the link in a box above this code. Copy and Paste that link into a browser and it will take you to the table.

A Tip is to use that description box at the top of the Webhook screen to remind yourself of the purpose of each Webhook.

  • Author
  • Registered
  • September 12, 2017
Thanks Mark I tried that (end point) but it brings me back to my own source app. Yes these were early days and I did not make note of the purpose. 

I believe that the endpoint is a table and not an app.  So I think that was your question.  "Where is the Webhook writing to".

  • Author
  • Registered
  • September 12, 2017
Can't seem to find the table as there is no ref to it.  But it is only a couple of days I have received the error.  So there might be some table.  The code should have some ref for user to use to locate table.  

Oh, I see.  You are saying that the email about the webhook error does not tell you the table which had the error.  Is that the issue?

But I just tested a deliberate error and the email does have a link to the webhook itself.  So it is telling you the table which has the error and the webhook which has the error.

  • Author
  • Registered
  • September 12, 2017
Yes please. 

  • Author
  • Registered
  • September 12, 2017
Just sent you a copy of the error.