Skip to main content

Account Dataset

Overview

Feature Description

Guandata BI supports retrieving account data from common OA systems and synchronizing it with the Guandata BI analytics platform through Account Sync. Supported sources currently include WeCom, DingTalk, LDAP, Feishu, and SAP ERP, with more OA systems being added over time.

Account Datasets help enterprises connect their OA account systems with the Guandata BI account system in a structured and integrated way. This makes it easier to manage accounts across multiple systems and tools and reduces account management overhead.

Use Cases

When enterprises build and maintain Guandata accounts, they often want to reuse existing internal account data that is scattered across business systems or OA systems. When the number of users is large, manually maintaining Guandata accounts becomes time-consuming and inefficient. To solve this, Guandata BI supports retrieving account data from common OA systems and synchronizing it into the Guandata BI analytics platform.

Prerequisites

Before creating an Account Dataset, users need to configure the corresponding OA system accounts as required.

User Guide

Steps

  1. Select the connector
  2. Select the data table
  3. Configure data connection and updates
  4. Confirm the data table information
  5. Manage the created dataset

Select the Connector

Entry point: Data Preparation > Datasets > New Dataset > Application (Account Dataset) > Select Connector.

Note

This entry point is visible only to administrators, and the related systems such as WeCom, DingTalk, LDAP, and Feishu must first be enabled in Admin Center.

Select the Data Table

Before creating an Account Dataset, select the account used to retrieve account data from the OA system.

  • WeCom: If multiple enterprise WeCom instances are configured in Admin Center, you can select an enterprise name from the dropdown. If only one is configured, the dropdown option is Default Enterprise.
  • DingTalk: If multiple DingTalk organizations are configured in Admin Center, you can select an enterprise name from the dropdown. If only one is configured, the dropdown option is Default.

After selecting the account, choose whether to retrieve the user table, the user group table corresponding to departments, or both. By default, both are selected.

Configure Data Connection and Updates

Configure update settings for the Account Dataset, including scheduling status, dataset update cycle, and task priority.

The detailed process is not expanded here because it is similar to the update configuration for database connections. See Standard Database Connection Guide.

Confirm the Data Table Information

Provide an easy-to-recognize dataset name, specify the save location, and add a description if needed. Click Confirm Creation to create the dataset.

Manage the Created Dataset

After the dataset is created successfully, it can be found in the corresponding folder in Dataset Management. Open its details page to view the dataset overview, related Cards, data security information, and edit configuration items on each page.

FAQ

If the dataset does not need to be used for Account Sync, the following steps can be skipped. If LDAP already contains the required mandatory fields for Account Sync, this step can also be skipped. Because account type or user group information may not exist in the user table, or may not match Account Sync requirements, ETL processing may be needed.

Note
  1. If DN is used as the user or user group ID, any change in the DN structure appears as a new user or user group during Account Sync.
  2. For users, the account field must use cnname; otherwise LDAP login will not work and only Guandata username-password login will be available.
  3. If LDAP itself has no user group ID and you want Account Sync to synchronize group information as well, use ETL to provide a usable user group ID.
  4. For more details, see Account Sync.