Postman Collection Runner vs Postman App: Variable Precedence Ambiguity

Answer to the Core Questions

1. Can the variable resolution order be customized? No. In all current Postman releases the hierarchy is hard‑coded as collection > environment > global. Data‑file variables are treated as environment variables and therefore override any environment or global value of the same name.

2. What can you do to avoid accidental shadowing? Use clear, non‑conflicting names, prefixes, or clear the environment before a run. You can also store constants in the Globals tab or load them via the environment tab instead of a data file.

3. Is there an API flag to change precedence? No. The Postman API currently offers no endpoint or flag that alters the variable resolution order for automated test runs.

Confirmed Facts (verified with the Postman console)

• In the app, a request uses the collection variable when a name clash exists.
• During a Collection Runner run, a CSV/JSON data file variable replaces an environment variable with the same name.
• There is no UI setting or API parameter that changes this behavior.

Practical Steps to Avoid Unintended Overrides

1. Audit variable names: Keep collection, environment, and data‑file variables in separate namespaces. A common convention is to prefix data‑file variables with data_.
   • Example: data_userId vs userId.
2. Clear the environment before the run: In the Collection Runner, click Clear environment or use a pre‑request script that deletes or resets the relevant keys.

   // Pre‑request script example
   pm.environment.clear();
   // Re‑load only the variables you need
   pm.environment.set("token", "{{envToken}}" );
   

3. Load constants via the environment tab: If a value should never be overridden by data‑file variables, store it in the environment (or global) and reference it as {{token}}. Do not duplicate it in the data file.
4. Use environment files instead of CSV/JSON for static values: Environment files are loaded as part of the environment scope and respect the established precedence.
5. Review the Postman Console: After a run, inspect pm.variables.get() outputs to confirm which scope supplied each value.

When Might You Need a Different Order?

If you have a scenario where a data‑file variable must intentionally override a collection variable, you cannot rely on the current precedence. In that case, rename the collection variable or move the overriding logic into a pre‑request script that sets the value explicitly.

Ask for Missing Diagnostic Detail

To tailor a solution precisely, could you confirm whether you need any data‑file variables to intentionally shadow collection variables, or if all overrides should be prevented?