Hi @cnr ,
Interesting case, but I’m not sure I completely understood it.
What is your purpose?
AddRow() formula returns an
Action, not a row (*).
Therefore I expect that the quirky behaviour is due to the fact that the first time it adds the full row by guessing the data inference taking the origin of this action.
Let’s say that I’d expect an error, in this case, as we are comparing
Ref) objects, but
I’d not consider it a bug (more on this from @Jason_Tamulonis and other @codans, I hope)
Also, I think it’s not related with the
WithName() bug (now fixed): that was a due to a referential context not passed to
In the document I provided an example of how to refer to a newly created row.
I’m sure @Paul_Danyliuk (guess who… ) fully explained about it but I cannot find the original post.
It is a typical use-case of opening the detail of a newly created row in a different table.
It still relies however on the “forced” way to create a row from an action, though.
As said sometimes in the past, I would open this topic.
I think that returning the subject of the action - rather than the actions itself - would be more useful and intuitive, as you pointed out with this post.
So add/modify/delete row should return the affected row(s) by simplifying significantly the logic of some typical use-cases.
Happy to discuss more about it.