So I have a company table with company names and I have a task list where I link to the company table.
Issue - I can type in task ABC in the task list for two different companies and it will enter as two separate rows.
BUT…if I am on the company table and want to enter task ABC (let’s say it is a common task - “pitch them”), it is choosing the pre-existing ABC and then when I go to the task list, the task is listed with two company names, which I don’t want.
I want a unique row for each task, even if the task name is the same.
Does that make sense?
I am sure there is a simple solution but I am missing it.
Because of the way relationships work it will always try and match to an existing entry. This is known as a one-to-many relationship. What we have to do it force it to exclude existing entries for other customers without excluding its own.
To do this we simply add a formula filter to the relationship column. It states that the only tasks it should show per Company row, are tasks that match the current row in the relationship.
And here you can see it not finding either of the potential tasks when trying to add another with the same details:
Note that with this filter when you use the drop down on the Tasks column in the companies table it will always return no results. This is because it will not show tasks already linked to the company and all other tasks, including tasks with no company link, are excluded by the filter. From how I see you using this I do not think this will be an issue but a modification can account for this if need be but only to show unassigned tasks.
I’d also just like to suggest that you take down the Loom recording. I am not sure if you are using test data but the clip exposes company names and their associated email addresses which could be a GDPR issue.
