Anywhere! This is because the left side ( the attribute() call) acts at document level so doesn’t care bout the context of the current note/agent: it has the same effect wherever it is run. When testing, I used the Edict of ‘Note B’, but you could use a rule or a stamp or in this case a quickstamp as once run you don’t need the code again.
What you can’t do, via an attribute’s suggested values is to have different suggestions for ‘Note A’ as opposed to ‘Note B’. This is because, as above an attribute’s suggested value work at document level for all notes/agents/etc.
I’ve just updated Suggest Attribute value lists to clarify that suggested values are per attribute and not per note. These things tend to lay near obvious once you know.
Another really good strategy for this is, rather than using the suggested value on an attribute, is to create a resources container, e.g., People. In the people container create notes with the note names being the name for the people. Then, use collect to populate the target attribution, e.g., `$Person=collect(children,$Name)', where $Person is a set attribute. Add this code as a $Rule to your People container. This way, every time you add a new person to this container the name will be available for selection across your Tinderbox file.
Note: I’ve found this methods to be much more flexible and portable across Tinderbox files than messing with suggested. Also, check the our video library we’ve discussed this method in several past meetups.