How to handle environment-specific schema names inside SQL Catalog Item queries during asset promotion? I am promoting a SQL Catalog Item from Environment A to Environment B in Ataccama ONE.The SQL Catalog Item does not exist in Environment B, so it is expected to be created as part of the import. The required Location/Source GUID mappings are already configured.The challenge is that the SQL Catalog Item contains an SQL query with an environment-specific schema name.For example, in Environment A, the query contains:FROM ENV_A_SCHEMA.brz_pa_oracle_view.table1WHERE Report_Snapshot_Date = ( SELECT MAX(Report_Snapshot_Date) FROM ENV_A_SCHEMA.brz_pa_oracle_view.table1)LEFT JOIN ENV_A_SCHEMA.brz_pa_oracle_view.table2 pmIn Environment B, the schema should be:Β FROM ENV_B_SCHEMA.brz_pa_oracle_view.table1Β and similarly for the other tables.What I triedBased on the Environment Mapping documentation, I configured a scalar mapping for the Location:Β { "location.name": [ { "pattern": "^<ENV_A_SCHEMA>$", "replacement": "<ENV_B_SCHEMA>" } ]}The Location mapping works a