Had a table called Tasks, and a table called TimeLogs. TimeLogs have a lookup column that selects a single task and logs a start time and an end time. Because I referenced the TimeLogs several times in my Task columns, I created a column in Tasks called TimeLogs. Some of my functionality broke as it thought I was referring to either the table or the column incorrectly in several places. When referring to the column, I can make sure to use CurrentValue.TimeLogs or thisRow.TimeLogs, but sometimes when I wanted the table, it would assume I meant the thisRow or CurrentValue, but there is no way to tell it, no I mean Table.TimeLogs.
Would be nice if it warned me or blocked me from naming them the same, as I’m not sure there is a place to go to see all the filters, column functions, etc that have been broken, other then going through them one by one, or waiting for a coworker to complain that a feature is broken.
I think when you create a lookup column, it automatically names it the same as the table?