I have a table called Tickets. When I am editing a ticket and select a specific menu item from a single-select field, I have an automation that creates a new ticket. This works smoothly when I am in an ungrouped view.
However, if my view is grouped in any way, the automation causes the record that triggers the automation to temporarily pop out of the group as if I had changed data that the group is based on – bordered by an orange rectangle with the “Record Moved” label. (Is there a term for this state in AirTable? I haven’t been able to find it!)
The temporarily moved record is not that big a deal – if I just hit esc or tab, the record pops back into its rightful place and all is well with the world. But it looks confusing and stupid and people hate it. I’m looking for someway to end the automation with the record back in the grid where it belongs instead of floating in space.
The strange thing to me is that the record that moves is not the new record that I created with the automation, but the original record that I used to trigger the automation. I think this is odd because nothing about this record has changed other that the single select field, which has nothing to do with the grouping. If I turn the automation off, changing the single-select doesn’t pop the record – so why does this happen with automation? Is there anyway to stop it?
Things I have tried:
Some screen shots of a stripped down example of my problem:
View before the automation is triggered:
View after the automation, showing the annoyingly moved field:
My automation trigger:
My automation action:
Is there a way to stick the record into the grid at the end of the automation, or do I just have to live with it like this?
No sorting, no filtering, just the one group. I agree with you … I don’t understand why it is affected. Like I say, if I turn off the automation, setting the single-select doesn’t move it … it is something that is caused by the automation. I built this super-simple example with nothing tricky in it, still can’t figure it out!