Webhook triggers now on EVERY single change -> no more save button

Follow

Malte Ahl

• April 28, 2014 16:40

As of today web hooks are triggered on every single change. Yesterday I had an save button, changing 10 fields of information in one item would result in one web hook call. Today every change is saved live -> 10 web hook calls for 10 changes in one item. This is really annoying. Are you planning on fixing this?

Second note: It is also really annoying that I can not use TAB anymore to move to the next field. This worked beautiful until yesterday, with your update today it is gone. Please bring it back!

Thanks

1

• 

  Bruno Soares Lima

  • April 28, 2014 17:57

  Yes, we have here the same problem, we need the edit button to edit all fields before SAVE the item. And after that, execute only one time the hook.

  0

  Comment actions Permalink
• 

  alice errett

  • April 29, 2014 12:26

  Agreed. That Tab thing is really annoying.

  0

  Comment actions Permalink
• 

  Ben Dobson

  • May 01, 2014 13:29

  Agree - can we have the save button back? This is really unintuitive and annoying. thanks

  0

  Comment actions Permalink
• 

  [100Rails] Steve Shepherd

  • May 01, 2014 21:36

  Tab is being fixed and is a known issue. Also updating the data layer behind the current popout layer.
  Because Podio have now moved to a more granular update model you will need to change your webhook code so it checks the field that was updated.
  This is better for multi user concurrence as before someone could be editing at the same time a whole record and whoever saves last wins the update. Now it is at a field level.
  There is more work being done here I think so that when a field is updated by another user it will light up green like the calcs do now. This way you can see someone else editing information.
  The sacrifice is in the webhooks. The only way they will get around this is webhooks by field and I don't think they will go that direction.

  my two cents worth... ;)

  0

  Comment actions Permalink
• 

  Andreas Haugstrup Pedersen

  • May 02, 2014 23:00

  Field-level webhooks have been supported for a long time, but you have to create them programmatically. You cannot create them via the UI. Details in the docs: https://developers.podio.com/doc/hooks

  0

  Comment actions Permalink
• 

  Bruno Soares Lima

  • May 05, 2014 12:24

  I can't believe in that, do you know know many work I will have to do to repair it?
  We have a lot of hooks and after change, a lot of problems come to us.

  I'm really desapointed with this... :(

  0

  Comment actions Permalink
• 

  Jesper Ordrup

  • May 08, 2014 22:08

  That totally explains why item:update webhooks number of calls explode. And when the webhook in turn does api calls, then we hit the api limit very very quickly. Solution - change to field hooks? But if we update 3 fields then the result is actually even more calls than before.

  Another thing is that the whole idea with saving on field level should be better - I'm not so sure. I think I like it better to have the last updater win and have consistent data instead of having an item with a mix of updates from 2 or more updates.

  0

  Comment actions Permalink

Please sign in to leave a comment.