Duplicate <object>

Feature requests
1

The idea is:

The duplicate option would be very useful for literally every object in our possession: Database, Automation, Node in automation, Dashboard, etc.
This can serve multiple purposes such as: backup before testing, MVPs, swift scaling.

Save as private template option would be a great addition to that, aswell .

My use case:

Applying the same automation to different databases and showing the results on two separate dashboards with separate layouts.

2

We will incorporate it into our future product roadmap. You can stay updated on our roadmap and upcoming developments here: Bika.ai - Automate Your Work with Intelligence.

1 Like
3

While we don’t currently support cloning databases, Automations, or Automations, you can achieve similar results through a slightly more involved workaround: Export and re-import the objects via .bika files. This method allows you to effectively duplicate items across your projects. :sweat_smile:

1 Like
4

Hi @Kelvin, well, exporting doesn’t work as expected:

  • We can’t export DBs with more than 50k rows. That actually needs to be increased to the account limits asap
  • When trying to export single automation, it gives an error:
    The automation XXX action FIND_RECORDS linked resource not in current folder
    (the DB is in the same folder actually)
  • Cannot export database view. This is crucial to being able to export filter-based. Since find records is capped at 100 records I can’t even automatically copy filtered records to another DB to export it
5

Yeah, the 50k row export limit is a thing right now. But for your use case, if you choose “Don’t include database records” during export to only get the database structure, would that work as a temporary fix?

Btw I just tried reproding the automation export error – turns out it’s a bug. Our devs are on it! Meanwhile, might wanna try exporting the entire parent folder instead (with the same “no records” option).

Exporting views is a solid idea! The team’s actually considering adding that to our roadmap. Appreciate you bringing these up!

6

Hi @Kelvin, yea I was able to export the full folder previously so I can confirm that’s fine
My use case is that I make a DB processing automation which uses external API and OpenAPI to make changes in the DB. I have a few similarly structured DBs (that’s just a segments of a main DB from another source) so I can unfortunately use the same automation over to different DBs as it seems to break everything once I change the DB which is processed in the Find records node. Might be mistaken, but this is what I have tested out. Well, since I was able to export .bika and so I didn’t have to build the same automations for each DB all over again, that’s working for now! As I previously mentioned in my Appsumo review, the toolset is great, and I’m ready to some trial and error. Thank you!

7

Hey there! Glad exporting the .bika file worked for your workflow!

About the “Find Records” action - have you tried modifying its configuration after importing to point to the new database? Could you share what specifically goes wrong when you switch databases? Any error messages popping up?