A governance policy states that hard-coded IDs must never be present in deployed components.

Hard-coded Salesforce IDs are a deployment anti-pattern because IDs vary across environments. A Record Type, Account, Contact, Price Book, or configuration record may have one ID in Development and a different ID in QA or Production. The correct design is to resolve IDs dynamically using parameters, relationship fields, unique keys, DeveloperName values, or Data Mapper lookup mappings. Manually changing IDs after deployment is fragile and violates governance. Excel lookup tables are outside the controlled metadata/configuration flow and are not reliable. Even standard-looking references should not be hard-coded unless Salesforce guarantees portability, which is not the normal case for org-specific record IDs. Salesforce Data Mapper Load configuration supports lookup behavior that uses a field value to query Salesforce data and write the resolved result to the output field.

================