You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We have many stored procedures, user-defined table types and user-defined table functions. We would like to be able to add these to the data catalogue.
Describe the solution you'd like
We would like to be able to send via the API the table definition with the TableType being
StoredProcedure
UserDefinedTableType
TableValuedFunction
We would like to be able to define input parameters. This would be an additional tab on the table page. Input parameters should be able to have tags and glossary items assigned to them, just like columns.
We would like to be able to set the table SQL in the ViewDefinition field.
We would like to be able to view the ViewDefinition on the page.
Making this available only via API (i.e. not needing to update the ingestion adapters) would be a good first start.
Describe alternatives you've considered
As an alternative, we will be defining these artefacts as Views, however, this is not ideal.
We will be defining input parameters using a convention that ensures they are always the first columns such as @ParameterName.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We have many stored procedures, user-defined table types and user-defined table functions. We would like to be able to add these to the data catalogue.
Describe the solution you'd like
We would like to be able to send via the API the table definition with the TableType being
We would like to be able to define input parameters. This would be an additional tab on the table page. Input parameters should be able to have tags and glossary items assigned to them, just like columns.
We would like to be able to set the table SQL in the ViewDefinition field.
We would like to be able to view the ViewDefinition on the page.
Making this available only via API (i.e. not needing to update the ingestion adapters) would be a good first start.
Describe alternatives you've considered
As an alternative, we will be defining these artefacts as Views, however, this is not ideal.
We will be defining input parameters using a convention that ensures they are always the first columns such as @ParameterName.
The text was updated successfully, but these errors were encountered: