If you don't receive a neat solution to that, you could always just create a second attribute to temporarily store the incremented value, and then copy that value back into the original attribute, by either a copy rule (if that works) or a second automatic action which follow the first.
Obviously not as nice as just having the one though...
If you're only setting the value by automatic actions you should be OK to reference itself. The calculation would simply be "return Change._Attribute + 1".
Alternatively you could use the serial number of a collection to do the counting.
Thanks for the reply.
I actually implemented the latter (Collections) method as I was also storing the count against each record there, so by doing a latest() on the collection and then incrementing the last count value read from there I could increment by 1 and save and thus achieve same.
So what I guess you are saying then it's legal to reference self by name even if it's not listed in teh selection tree? That's good to know.
Yes as long as its not a calculation attribute. It would be fine to reference on a calculation in an automatic action.