Automation on created with filtered field value condition

🔧 Bugs & Issues
1

I want an automation to run on a created record - but only a few of them. Determined by a calculation field.

  1. it doesn’t work on created, as on created, the calculation didn’t finish yet.
  2. it doesn’t work on updated, as the finished first calculation doesn’t seem to trigger an record update.

That seems to be a catch 22.

I think the “created” event shouldn’t fire as long as the first calculation of the calculation fields isn’t finished.

What workaround to you have for this situation? Regularly repeated run instead triggered by event?
Anything else?

Is the new record with new calculation solving that?

1 Like
2

Hi @dirk_s,

very interesting use case :100:

With the new record, records are handled as drafts during creation, and calculation fields are continuously calculated while the record is being created. This has several advantages, including that the calculation values are already available during the creation process. So in your case, the correct values should already be there when the created automation fires.

We deliberately chose this approach because it was a frequent feature request from many Podio users. It also enables calculations in forms and, more generally, while a record is still being created.

This is different from the old record flow, where record creation happened purely client-side and the calculations only ran after the record had been created.

Have you already tested this with the new record?

Best regards and have a nice day,
Leo

3

Hi Leo,
I will do. The creation is done via a webhook automation - so no UI involved. Hope this is then still considered draft until the calculations are done?

Will let you know about the result of my test.

Actually: Its already a new record with new calculation field. My assumption: As an automation creates the record, its not handled as draft and the next automation based on creation already kicks in before the fields are calculated?