Semantic layer connections

Provider-defined connection forms

Installed semantic-layer extensions supply their connection fields and help text. Required fields are marked with an asterisk. Examples in empty fields are placeholders, not selected values. Follow the provider's field help for optional and conditionally required settings.

A nullable password is displayed as one optional password input. Leaving an untouched null value blank preserves it; clearing a value sends an empty string. Providers decide how these values are interpreted.

Providers can mark a private-key field with x-input-type: pem to request a multiline editor. Paste the whole key, including matching BEGIN and END lines. The inline check only checks the private-key envelope, not cryptographic validity. Password-protected keys also need their passphrase. The hint is for private keys, not certificates.

Automatic metadata discovery is debounced. Discovery failures do not prevent entering manual values when suggestions are unavailable. Discovery errors use fixed messages rather than displaying provider exceptions. Save displays the server's sanitized validation reason, such as a duplicate name or missing configuration field, with a generic fallback when no reason is available. Saved secrets remain masked while editing; configuration changes may require re-entering masked values, as explained by the server's validation message. Changing connection dependencies can clear dependent selections, so check those fields before saving.

Dependent source selectors

In Add Semantic View, changing a selected Database makes its dependent Schema choices unavailable while fresh options load, including the debounce interval. A matching response preserves selections that remain valid and clears those no longer offered. If loading fails, the form retains your selections but keeps stale choices unavailable; a later form edit can retry once for that dependency state. Changing the Database requests choices for the new state. After a failed refresh, saving stays blocked only while a single-choice dependent field has choices loaded. If no dependent field has its prerequisites filled, clearing a required source keeps dependent choices unavailable until that source is filled. Clearing an optional dependency can load choices for the empty state instead. Semantic views listed for an earlier dependency are discarded, and views cannot be added while dependent choices are loading.