Generally, String, Number, Set and List types auto-populate a value pop-up list of existing values used (in the entire document) for that attribute. The list will show up to 999 items, listed in case-insensitive lexical sort order (or number sequence for Number-type). In the case of multi-value attributes (Set and List types), items used by the current note are ticked in the pop-up list.
This pop-up list can be seen in attribute value boxes in both text pane key attribute tables and in the attributes tab of Get Info dialogs. It is also used to populate a pop-up on the Quickstamp Inspector.
A further aspect is that it is possible to pre-populate this list with ‘suggested’ [sic] values that are listed even in advance of any note using them. However, it is not possible to restrict notes to a particular set of values.
Attribute Browser view offers a visual way to explore the values of a given attribute. It can also be set in scope to reflect only part of the current document, the scope being either a a container (and descendants) within the overall document or an ad hoc scope via an agent.
Viewed from an action-code perspective, values() can be used to collect all values used by a given attribute. It defaults to document scope but an optional parameter allows a more restrictive scope.
So that is the range of ways of getting/seeing attribute values.
A user-defined attribute doesn’t have ‘fields’, just a value (or value(s) for Set/List types). I assume you’re thus referring to the attribute’s value. If so…
It sounds like you want to use a scoped values() action for $Name, scoped to only find the notes of interest. Alternatives are to use collect() or collect_if() action
If not attribute value(s), please can you clarify in more detail the actual task. I sense you’re working back from an envisaged outcome or another app’s workflow. Defining the task in the context of Tinderbox (as opposed to some other context) will make it easier for your fellow Tinderbox users here to help you.
Are you asking for a grid where you edit a value of some other note from the current note’s context? I’m not sure, based on your description, that such is possible. However…
If you envisage a grid where each target note is a row and each column is the value of an attribute and editing cell edits the value for a note/attribute context, I’d say this can’t be done in the form described. The closest would be to try using Attribute Browser view with column view enabled. But column view with many columns will tend to tax the app’s performance in a big doc. With a better understanding of at actual task or a demo file to work with, I suspect there are easier/better ways to the same end (albeit via a different route) using the features that Tinderbox already offers.