create-sql-mappings

To update SQL mappings without recreating views, specify the technical domain and target views to selectively overwrite only the SQL mappings while preserving the original view definitions and semantic terms.

Yes, you can publish affected Draft views directly after updating SQL mappings. The workflow supports optional publication of Draft views to move them toward production as an end-to-end process.

Glossary enrichment for SQL view mappings generates or refines user instructions from the data dictionary before invoking the mapping tool, ensuring semantic terms align with the governance semantic layer.

Yes, identifying the relevant technical domain is required before creating SQL mappings. The skill uses the domain to target specific views or all views within that domain for selective mapping updates.

The best way to correct SQL mappings in a governance semantic layer is to use selective mapping updates that overwrite only the SQL mappings for specific views, preserving existing semantic terms without touching view definitions.

SQL mapping updates should preserve semantic terms by default. If terms are lost, verify that the glossary instruction enrichment is properly generating user instructions from the data dictionary before the mapping tool executes.