If the steps are static and don't change, you could do this with a formula:
If they're dynamic, then I'd recommend a table where each record represented a single step linked to a single org, and then you could do lookups based on whether the step's completed or not:
And I've set it up for you here!
If the steps are static and don't change, you could do this with a formula:
If they're dynamic, then I'd recommend a table where each record represented a single step linked to a single org, and then you could do lookups based on whether the step's completed or not:
And I've set it up for you here!
Hi adam,
Mostly, they are stagnant overall, some may not apply to some of the organizations, but I was just planning on marking those as complete. For the static formula, the only thing is that the tasks have long names, not numbers, and I currently have 47 tasks on the list. And I don't want them to be referred to as numbers cause that is how I will refer to them. So is there a way to do that easily with a formula? I'm thinking that it might be best to do it the other way with the Org<>Steps table.
Thanks!
You'll need two linked record fields. One for tasks assigned, and one for tasks completed. An automation or script can highlight the tasks that are incomplete of those assigned.
You can use an automation to auto assign tasks from a view. Then, as tasks are completed, add them to the Completed tasks linked record field. An automation would handle the unfinished tasks out of tasks assigned.
Alternatively, Have a third mapping table of tasks assigned per org. each task assigned to each org will be one record here. You can then rollup finished and unfinished tasks easily. From a db perspective, this is a more solid approach.
Hi adam,
Mostly, they are stagnant overall, some may not apply to some of the organizations, but I was just planning on marking those as complete. For the static formula, the only thing is that the tasks have long names, not numbers, and I currently have 47 tasks on the list. And I don't want them to be referred to as numbers cause that is how I will refer to them. So is there a way to do that easily with a formula? I'm thinking that it might be best to do it the other way with the Org<>Steps table.
Thanks!
Yeap, formula wise it'd be the same, it'd just be a pretty long formula
Having the Org <> Steps table would be nice yeah, and it would let you track specific data tied to each task too
Yeap, formula wise it'd be the same, it'd just be a pretty long formula
Having the Org <> Steps table would be nice yeah, and it would let you track specific data tied to each task too
Is there a way to set this up that reduces the number of records I need? With 4 orgs (plus other things I need in that base) I am already over the limit (I am on the free plan). Thank you!
