Just wondering if anyone would consider this a bug, or if there is some way to make the experience better?
I have a Table that is meant to have 1 record per [employee] per [month], and no more. So I set a valid_if rule to accomplish this and prevent duplicates.
ISBLANK( FILTER( employee_month , AND( [id] <> [_THISROW] , [employee] = [_THISROW].[employee] , [month] = [_THISROW].[month] ) ) )
The validation works as expected:
I also have a table View of this Table, which is grouped by [month]
After drilling down into a single [month] group, clicking the add button utilizes the magic of pre-filling that [month] value.
But then if I select an [employee], like above, that I know already has a record for this [month], the validation rule doesn’t re-evaluate:
Even if I change the [month] value, then change it back, still no re-evaluation. It is only when I finally try to click Save that it re-evaluates and shows the validation error.
I suppose I can probably put the same valid_if expression onto the [employee] column as well, as a usability workaround . However I think this is undesirable behavior and/or a bug, anyone else?