=IF(EXACT(ValueA;ValueB); ValueA; "Mismatch!")
So you basically just compare two other rows (which you can hide if you like) and if they are exactly the same you display the value, otherwise you display an error. =IF(EXACT(ValueA;ValueB); ValueA; "Mismatch!")
So you basically just compare two other rows (which you can hide if you like) and if they are exactly the same you display the value, otherwise you display an error.The next step may be Don't Repeat Yourself (DRY), so even N nearly duplicate formulae for N rows is N-1 more times than needed.
It's not so bad with one column, but after rearranging a dozen columns and copy-pasting some corrections, the question becomes, "Is everything still working okay, or do I need to skip lunch?"
There's ways around, like a `CURRENT_ROW()` function. That makes it generic.
Understandably, it can be a hassle to type extra functions all the time. Boilerplate for one-liners isn't fun; the whole point is rapid iteration and prototyping.
Just saying, if a model is important enough to keep around and maintain, put in some pragmatic checks--just like your example.
Pretty useful! https://help.libreoffice.org/latest/en-US/text/scalc/01/0512...