Add the Technical Lineage for Tableau (Beta) capability to the Edge site

After you create a connection to Tableau, you can add the Technical Lineage for Tableau (Beta) capability.

Requirements and permissions

A global role that has the following global permissions:

  • System administration
  • Manage connections and capabilities, for example Edge integration engineer.
  • Register profiling information

Steps

  1. Open an Edge site.
    1. On the main menu, click , and then click Settings.
      The Settings page opens.
    2. In the tab pane, click Edge.
      The Edge sites overview appears.
    3. In the Edge site overview, click the name of an Edge site with the status Healthy.
      The Edge site page appears.
  2. In the Capabilities section, click Add capability.
    The Add capability page appears.
  3. Enter the required information.
    FieldDescriptionRequired

    Capability

    This section contains the general information about the capability.

    Name

    The name of the Edge capability.

    Yes

    Description

    The description of the Edge capability.

    No

    Capability template

    The capability template for TableauI. Select Technical Lineage for Tableau (Beta).

    Yes

    Main

    The required information for creating a technical lineage.

    Source ID

    The name of the data source. You can give this any name, as long as it is unique.

    Warning If you are switching between the lineage harvester and Edge, the value in this field must exactly match the value of the id property in your lineage harvester configuration file.

    Yes

    Delete raw metadata after processing

    Technical lineage via Edge harvests metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance, for processing. This option indicates whether or not the source metadata should be deleted after it is processed.

    Select this option to indicate that the source metadata is deleted after processing.

    Clear the checkbox to keep the source metadata after processing. The metadata is stored in the Collibra infrastructure.

    Note Selecting this option can negatively impact performance.

    		 
    Analyze only

    This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances.

    When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester.

    This option is not enabled by default.

    You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows:

    • During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage.
    • On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.

    No

    Tableau connection

    The Tableau connection that you created for ingestion in Data Catalog.

    Tip Select the name that you provided in the Name field when you created a connection to Tableau.

    Yes

    Domain ID

    The unique reference ID of the domain in Collibra Data Intelligence Cloud in which you want to ingest the Power BI assets.

    Open the relevant domain in Collibra. The URL looks like: https://<yourcollibrainstance>/domain/22258f64-40b6-4b16-9c08-c95f8ec0da26?view=00000000-0000-0000-0000-000000040001. In this example, the reference ID is in bold.

    		 Yes
    REST only

    Indication whether or not you want to use both the Tableau REST API and Tableau Metadata API to harvest Tableau metadata.

    • Cleared (default): The lineage harvester will use the REST API and Metadata API to harvest Tableau metadata.
    • Selected: The lineage harvester will only use the REST API to harvest Tableau metadata.
    Note This filed must be cleared, to:
    • Enable technical lineage and the automatic stitching of Column assets to Tableau Data Attribute assets.
    • Harvest owner information for Tableau projects, workbooks and data models.

    No

    Exclude images

    Indication whether or not you want to excluding the downloading of images.

    • Cleared: Images are downloaded.
    • Selected (default): Images are not downloaded.

    Note The maximum number of images that can be uploaded to Collibra per day is determined by the configuration of the file upload service, in Collibra Console. For complete details, see the Upload configuration settings in DGC service configuration: options.

    No

    Site ID

    The site IDs of the Tableau sites that you want to include in the ingestion process.

    Important Ensure that you specify the correct value. The correct value is the URL of the site to which you want to sign in. When you manually sign in to Tableau Server or Tableau Online, the site ID is the value that appears after /site/ in the browser address bar. In the following example URLs, the site ID is MarketingTeam:
    • Tableau Server: http://MyServer/#/site/MarketingTeam/projects
    • Tableau Online: https://10ay.online.tableau.com/#/site/MarketingTeam/workbooks

    On Tableau Server, however, the URL of the Default site does not specify the site. For example, the URL for a view named Profits, on a site named Sales, is http://localhost/#/site/sales/views/profits. The URL for this same view on the Default site is http://localhost/#/views/profits. The site name Sales does not figure in the URL.
    Example If you want to ingest two Tableau sites "Site 1" and "Site 2", you can enter the following information in this field: ["site ID of Site 1", "site ID of Site 2"].

    Yes

    Site Name
    		The site names of the Tableau sites you specified in the Site ID field.

    Yes

    Concurrency level

    This field is intended to help if you are experiencing HTTP 401 Unauthorized errors due to too many concurrent HTTP calls, using the same token. It allows you to specify the internal sizing, meaning the amount of tasks that can be executed at the same time.

    The default value is "10", meaning as many as 10 HTTP requests can take place in parallel. Consider reducing the value if you are experiencing HTTP 401 Unauthorized errors. Setting the value to "1" effectively disables the concurrency level, so that HTTP requests will be run in a synchronous manner, instead of in parallel.

    No

    Source configuration
    		This field allows you to provide JSON code for database mapping, domain mapping and filtering.

    Database mapping:

    "databaseMapping": {
	"<hostname:port>":"<actual database name>"
},

    Domain mapping:

    "domainMapping": {
	"<Site-1>": "reference-id-of-Domain-1",
	"<Site-1> > <Project-Default>": "reference-id-of-Domain-2"
	}

    Filtering:

    "filters": {
	"projects":{"site_name2 > project_name2": "domain-reference-id2",
	"site_name3 > project_name3 > subproject_name": "domain-reference-id2"}
	}

    No

    Active

    The option determines whether to include or remove the technical lineage of the data source.

    Select this option to include the technical lineage of this data source.

    Clear the checkbox to exclude the technical lineage of this data source.

    No

    Paging

    This section allows you to customize the Tableau API pagination settings.
    The default values are sufficient in most cases; however, you can decrease them to help mitigate node limit errors, or increase them to speed up API calls.

    "paging": {
	"databasesPageSize": 100,
	"tablesPageSize": 100,
	"tablesColumnsPageSize": 100,
	"tableColumnsPageSize": 1000,
	"datasourcesPageSize": 50,
	"datasourcesFieldsPageSize": 50,
	"datasourceFieldsPageSize": 100,
	"worksheetsPageSize": 100,
	"worksheetsFieldsPageSize": 100,
	"worksheetFieldsPageSize": 1000,
	"usersPageSize": 100,
	"dashboardsPageSize": 100,
	"columnsLimit": 20,
	"fieldsLimit": 20
	}

    Settings per metadata type and descriptions

    Metadata typeSetting and description
    Dashboard
    • dashboardsPageSize: The number of dashboards per page.
    Worksheet
    • worksheetsPageSize: The number of worksheets per page.
    • worksheetsFieldsPageSize: The number of worksheet fields per page.
    Database
    • databasesPageSize: The number of databases per page.
    Table
    • tablesPageSize: The number of tables per page.
    • tablesColumnsPageSize: The number of table columns per page.
    Table columns
    • tableColumnsPageSize: The number of table columns per page.
    Users
    • usersPageSize: The number of users per page.
    Data source
    • datasourcesPageSize: The number of data sources per page.
    • datasourcesFieldsPageSize: The number of data source fields per page.
    • columnsLimit: The number of data source field columns per page.
    • fieldsLimit : The number of referenced data source fields per page.
    Data source field
    • datasourceFieldsPageSize: The number of data source fields per page.
    • columnsLimit: The number of data source field columns per page.
    • fieldsLimit : The number of referenced data source fields per page.

    No

  4. Click Create.
    The Edge site connects to your data source.

What's next?

Manually synchronize Tableau sites.