Importing Custom Property Values

After associating custom properties to object types, you can set values for the properties by exporting the objects and the associated custom properties into a file, add values to the custom properties, and import it to Data Catalog. This method helps you to enrich technical metadata in bulk.

Importing the values of custom properties are available for data assets that are created using a relational database or Oracle Object Storage. Examples of relational database include Microsoft SQL Server, MySQL, and Oracle Database. For data assets created using a relational database, you can import custom property values at the schema and data entity levels. For Oracle Object Storage, at the bucket and data entity levels.

Importing custom property values in bulk saves time and makes the review of the content easier. Ensure that you begin import at the same object in the data asset from where you exported the file.

    1. In the details page of the object type for which you exported the custom property values, select Import Custom Properties.
    2. In the Import Custom Properties dialog box that appears, select the Skip empty values in the excel file checkbox so that the empty values in the file don't overwrite the existing values in the data catalog.
      Note

      When several-values-enabled custom properties are imported to the data catalog with the Skip empty values in the excel file checkbox selected, the values in the Excel file are added to the existing values for that property in the catalog, which means that the existing values aren't overwritten.
    3. Select Import.
      While importing the file, all the objects in the file get imported, irrespective of the scope of the object from where the import is started. Therefore, all the values of the custom properties present in the file get updated.
  • This task isn't available in the CLI.

  • This task isn't available in the API.