System Build Help

Get Help
1

Hey everyone,

Need to say what a great community this has been so far and how much I have been loving Fibery. Im looking for some slight guidance and some help with suggestions on the build.

We come from clickup and while I do love their automations I hated the no database feel and no relations like Fibery offers.

We are a Marketing company with a ton of client facing work, in clickup the way I had it built out was a sort of a baton passing task, task would come in from the PM it would go to the copywriting, the task would then move to the videographer, from there it would go to the editor, review team, then scheduler this was mainly done through automations.

Currently in Fibery I just have one creative task database that has multiple different views per department and an automation that changes the phase from say editing to review, issue I am running into now is the add a task or add record button if I change view on one board it changes them across all of them, I am guessing its because the task entry is a creative task and no matter the view it will be set to whatever I set it to on one of the boards.

Im just trying to grasp if I am really setting this up the right way, I do have a seperate database for the customers, employees, etc just I was at a loss for how to do it for the creative departments without everything being in one database. If anyone has some insight in this I would appreciate it!

Thanks,

J

1 Like
2

Hmm I’m not entirely sure I understand how it’s set up.

Can you share screenshots of the different views per department? What fields each has?

A general rule of thumb is that is its the same thing, same fields, same database. If it’s a different thing, different fields, different database. You could split this into one project, and multiple tasks. Then the project is what gets filled out, and each person / team gets tasks to do things in that project.

Again, not entirely sure how you have it set up so it’s hard to give advice.

If you can share a screen recording with this that would be very helpful!

If board = entity, you can use rules to specify which entity view: Fibery

1 Like
3

I’m guessing that we’re talking about entity views (potentially using rules to determine which one to show?)

If you change to a specific entity view for a task, then indeed, the entity view will be changed for another task that you have open at the same time.
Is this what you meant?

In general, if you’re relying on rules for entity views, you would ideally seldom need to manually override

1 Like
4

Please share a screenshot so we can better understand what you mean here. This reads as if you’re creating a task and then opening the task to see the entity layout and that’s an important detail in the workflow you’re trying to create

1 Like