Sometimes I create rules based on existing Rules, and it would be a time-saver if I could copy and modify existing ones. The Rule can be disabled after the copy and can turn to enable once it is different from its origin.
This request should really be rolled into Centralized script management for Workspace
Not sure if this thread is still active but I just wanted to confirm I have the same or similar need right now - to duplicate/copy the automation rule BUT then to move it to a different database. I am missing something like “Copy rule to database”. Currrently the rule is duplicated only within the same database and I can only duplicate it manually.
It’s pretty hard to implement this, since the parameters used in an automation (triggering field(s), fields to update, etc.) are usually specific to the database that the rule is operating on.
Thanks, Chris, makes sense. My situation: I have a database listing current currency exchange rates between CZK and EUR. I use these rates across different databases for conversion. The automation rules for conversion and for filling in relations to the exchange rate database are pretty much very similar or even same. But I understand this may be an edge case.
Are you using the currency exchange template?
FYI, in general, I often find that formulas usually work better than automations for these cases.
No, great to know about this template. We keep updating the rates monthly based on the information from our bank and then averaging them. I use these updated rates across different databases using relations and automations (partly because I don’t want only the calculation but also updating a separate field). So far smooth experience, not complaining. Just that sometimes it would save a few minutes to duplicate those rules instead of manually creating them.
This might be helpful @Rasto
Thank you, @RonMakesSystems! I need to go through the whole video in detail but if I understood it well - at around 6:45 you mention you didn’t want to use automations and show how to use the auto-linking feature instead. Interesting. I mean we have already solved it via automations in a similar way, one difference being that we cannot use the Currency Exchange integration because we need our bank-specific exchange rates as input.
This will be added in nearest future, Q4 2025
Fair, I think a longer term and more scaleable solution would still be to emulate the currency exchange database, but have the data inputted manually based on your bank, instead of updating all the rules.
Agree, Ron.