Catalog Artifacts
Overview
The Catalog provides an ability to build artifacts and save them into the Project tree. An artifact includes details of all the Catalog fields with their properties, such as Classification and PII, for a currently displayed Catalog version.
Pre-requisite for building the Catalog artifact is running the Discovery Job for at least one Project interface.
Build Artifacts
Building a Catalog artifact is done by clicking Actions > Build Artifacts in the Catalog application's Menu bar. A Catalog artifact is a file called catalog_field_info.csv. It is created in a CSV format, saved into the Implementation/SharedObjects/Interfaces/Discovery/MTable folder in the Project tree and uploaded to the Fabric memory as an MTable.
The below image is an example of a Catalog artifact:
The artifact is created for the Catalog version that is displayed in the application. The last column's heading holds the version number, such as V4 in the case of the above image. This column remains always empty.
Note that a Catalog artifact can be created for any Catalog version. Each new artifact overrides the previous one in the Project tree.
Catalog Artifacts
Overview
The Catalog provides an ability to build artifacts and save them into the Project tree. An artifact includes details of all the Catalog fields with their properties, such as Classification and PII, for a currently displayed Catalog version.
Pre-requisite for building the Catalog artifact is running the Discovery Job for at least one Project interface.
Build Artifacts
Building a Catalog artifact is done by clicking Actions > Build Artifacts in the Catalog application's Menu bar. A Catalog artifact is a file called catalog_field_info.csv. It is created in a CSV format, saved into the Implementation/SharedObjects/Interfaces/Discovery/MTable folder in the Project tree and uploaded to the Fabric memory as an MTable.
The below image is an example of a Catalog artifact:
The artifact is created for the Catalog version that is displayed in the application. The last column's heading holds the version number, such as V4 in the case of the above image. This column remains always empty.
Note that a Catalog artifact can be created for any Catalog version. Each new artifact overrides the previous one in the Project tree.
