July 2025
Schema changes
Docebo
Effective July 1, 2025 we use a new July 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.
We are updating the connector schema to prevent or resolve data integrity issues.
2 total changes • 2 possible breaking changes
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
GAMIFICATION_LEADERBOARD | |||||
column | Primary Key Change | users_id | users_id 🔑 | Added to primary key. | |
GAMIFICATION_LEADERBOARD_POSITION | |||||
column | Primary Key Change | gamification_leaderboard_id | gamification_leaderboard_id 🔑 | Added to primary key. |
NetSuite SuiteAnalytics
We now incrementally sync the NextTransactionLineLink
and PreviousTransactionLineLink
tables for the Netsuite2.com data source.
We have changed the primary key for the PostingAccountActivity
, PreviousTransactionLineLink
, and NextTransactionLineLink
tables.
- For
PostingAccountActivity
, we now use the combination offivetran_id
andfivetran_index
columns as the composite primary key. - For
PreviousTransactionLineLink
, we now use the combination ofpreviousdoc
andfivetran_index
columns as the composite primary key. - For
NextTransactionLineLink
, we now use the combination ofnextdoc
andfivetran_index
columns as the composite primary key.
Previously, _fivetran_id
was their primary key.