Michael Miller
Mike,
The validation windows can still be confusing if they don't inform the user about which fields are the source and which are the destination, in fact they may look identical in some instances. Even as the DynamicValue table editor, I get confused when I have to validate values on Road Centerlines for the new segment's information, the "from" street info, and the "to' street info. In all three cases the validation window (with your new addition) would show:
Select a valid value to store for RoadCenterline: FULLNAME,MUNICIPALITY,STCODE
Ideally, the validation window would tell you which table's fields are being updated and what the source table and fields are as well.
Template - Fields from DynamicValue table in <>
Validating <TABLENAME> (<FIELDNAME>), select valid value(s) from <VALUEINFO>
Example 1 - New road segment with "from" and "to" street validations
Validating RoadCenterline (FULLNAME,MUNI1,STCODE), select valid value(s) from MasterStreetName|FULLNAME,MUNICIPALITY,STCODE
Validating RoadCenterline (FRSTNM,MUNI2,FRSTNBR), select valid value(s) from MasterStreetName|FULLNAME,MUNICIPALITY,STCODE
Validating RoadCenterline (TOSTNM,MUNI3,TOSTNBR), select valid value(s) from MasterStreetName|FULLNAME,MUNICIPALITY,STCODE
Example 2 - Creating or updating Nodes on street intersections
Validating Nodes (FULLNAME1,MUNI1,STCODE1), select valid value(s) from MasterStreetName|FULLNAME,MUNICIPALITY,STCODE
Validating Nodes (FULLNAME2,MUNI2,STCODE2), select valid value(s) from MasterStreetName|FULLNAME,MUNICIPALITY,STCODE
I hope I'm making sense.