Microsoft Lists
Microsoft Lists is a Microsoft 365 application for work management and tracking. A list is a collection of data that you can share with your team. Fivetran supports syncing lists from your SharePoint site to your destination. You can sync multiple lists as unique tables to your destination.
NOTE: To sync documents from your SharePoint site, use our SharePoint connector. We retrieve every document from your SharePoint folder and sync each document as a seperate table in the destination.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | check | |
| History mode | ||
| Custom data | check | |
| Data blocking | ||
| Column hashing | ||
| Re-sync | check | |
| API configurable | check | API configuration |
| Priority-first sync | ||
| Fivetran data models | ||
| Private networking | ||
| Authorization via API | check |
Setup guide
Follow our step-by-step Mirosoft Lists setup guide to connect your Microsoft lists with your destination using Fivetran connectors.
Sync overview
Use the Microsoft Lists connector to sync your lists. We retrieve all the lists from the site you select. We support sites under both /sites and /teams URLs. Each list is synced as a separate table in the destination.
We add two metadata tables to your destination:
siteNamecontains the metadata of the lists that we sync.siteName_columnscontains the mapping details of the table columns in the destination and the list columns in the Microsoft Lists user interface.
Schema information
This schema applies to all Microsoft Lists connectors.
To zoom, open the ERD in a new window.We use a combination of the site name and list name as the destination table name. For example, a list called cars in a site site is synced as SITE_CARS table.
For columns with lookup fields, the column is synced as column_name_lookup_id. The value in the column corresponds to the id column in the respective lookup field source column.
For more information about the schema and table naming rule set, see our naming conventions documentation.
We use the site name in the destination metadata table names. For example, if the site name is 'Test Site', the metadata tables in the destination are TEST_SITE and TEST_SITE_COLUMNS.