Confused why a ServiceNow reference field shows the right results on one form but feels wrong on another? The answer is usually the ServiceNow Dictionary. In this post, you will see how dictionary entries drive field type, mandatory rules, defaults, attributes, and reference behavior, and how that foundation connects to reference qualifiers, field behavior, and form design. You will also get a simple ServiceNow MVC (Model View Controller) map that helps you place logic in the right layer, reduce scripting, and prevent “mysterious” issues across UI16, Workspace, Service Portal, imports, and APIs. If you want cleaner data, faster forms, and fewer surprises in lookups, start here.