Can you integrate SuiteAnalytics with TiDB?

Explore a SuiteAnalytics and TiDB integration with a Stacksync engineer. Stacksync support for TiDB is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.

Can SuiteAnalytics and TiDB sync in both directions?

SuiteAnalytics is read-only through Stacksync. Two-way sync is not supported through these connectors; use a supported direction or review another implementation.

How fast does the SuiteAnalytics to TiDB sync run?

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.

Will existing duplicates merge automatically?

No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.

How do I map SuiteAnalytics fields to TiDB?

Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.

What should I do if a record fails to sync?

Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.

What does a SuiteAnalytics and TiDB integration cost?

Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.

Which records should the SuiteAnalytics and TiDB pilot start with?

Start by reviewing Customer in SuiteAnalytics and Proposed customer table in TiDB (choose its name) in TiDB. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.

What should be ready before the SuiteAnalytics and TiDB initial load?

Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Have a NetSuite administrator enable SuiteAnalytics Connect and token-based authentication. Identify the TiDB account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.

ERP / Database · Two-way sync platform

SuiteAnalytics and TiDB integration

Plan how SuiteAnalytics and TiDB should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.

Set this up from Claude or ChatGPT

Scope your workflow with an integration engineer
Review the systems, records, and updates you need

Integration planning

stacksync.com

SuiteAnalytics

TiDB

Review the integration scope

Built for teams where self-serve, reliability and scale matter

Case study

Migrated from MuleSoft

Case study

Migrated from Celigo

Migrated from Heroku Connect

Migrated from Matillion

Case study

Migrated from Fivetran

Case study

Migrated from Celigo

Proposed workflow

Customer reporting workflow

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting eventA change involving SuiteAnalytics Customer or the proposed customer table in TiDB needs a defined result in the other system.

Start with SuiteAnalytics Customer and the proposed customer table in TiDB. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

What to verifyTest an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

Review records and field ownership

AI assistant

Set up SuiteAnalytics and TiDB from Claude or ChatGPT

Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste.

1. Add the Stacksync MCP server

Server URL

https://mcp.stacksync.com/mcp

In Claude

Open Customize → Connectors, select + Add, then Add custom connector.
Name it Stacksync and enter https://mcp.stacksync.com/mcp.
Select Connect, sign in to Stacksync and choose your workspace.

In ChatGPT

Open Settings → Apps → Advanced settings and turn on Developer mode.
Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth.
Sign in to Stacksync, then enable Stacksync from the tools menu in a chat.

Set up Codex or Claude Code

Codex

codex mcp add stacksync --url https://mcp.stacksync.com/mcp
codex mcp login stacksync

Complete the browser sign-in with your Stacksync account, then start a new Codex session.

Claude Code

claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp

Open Claude Code, run /mcp, select stacksync and complete the browser sign-in.

Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet.

Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: setup steps in the docs.

2. Ask your assistant

Create a sync between my SuiteAnalytics and TiDB.

Also from the same chat

You can also ask for workflows and AI agents (Genies) that use SuiteAnalytics and TiDB. The assistant checks what each app supports, for example:

“Build a workflow that messages our team in Slack when a SuiteAnalytics record changes.”
“Create a Genie that answers questions about our TiDB data in Slack.”

What happens next

Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat.
Gives you a secure sign-in link for each app it connects; you open it and sign in to that app.
Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first.

New to Stacksync? Create an account first, then sign in from your assistant.

Proposed record relationships

Records to connect

Use these examples to define record matching and field ownership for your technical review.

Download the mapping worksheet

CSV · No email required

Example record relationships between SuiteAnalytics and TiDB
SuiteAnalytics record	TiDB record	Record matching	Field ownership
CustomerDocumented record: Read: Supported. Write: see guide.Reporting dataset	Proposed customer tableProposed table; choose its name and schema.	Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.	Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.
InvoiceDocumented record: SupportedReporting dataset	Proposed customer invoice tableProposed table; choose its name and schema.	Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap.	The financial system owns posting and accounting treatment. A posted invoice may need a credit or adjustment process instead of an overwrite.
Vendor BillDocumented record: SupportedReporting dataset	Proposed supplier bill tableProposed table; choose its name and schema.	Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice.	Accounts payable owns approval and posting; a supplier bill is not an accounts-receivable invoice.

These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.

Record coverage to review

Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.

SuiteAnalytics

Read-only connector

Record types covered in the setup guide

Record types	Coverage and requirements
Customer Contact All custom objects Nexus Tax Type Sales Tax Item Billing Schedule Customer Subsidiary Relationship Account Accounting Period Bin Transfer Currency Rate Price Level Term Subsidiary Vendor Vendor Category Employee Other Name Category Vendor Subsidiary Relationship Project Project Status Project Task Job Type Task Partner Customer Status Phone Call Support Case Calendar Event Note Type Message Contact Category Contact Role Customer Category Customer Message Department Expense Category Job Status Classification Location Saved Searches Deleted Records	Reading: Supported. Updating this object: confirm availability.
Invoice Sales Order Check Credit Card Charge Credit Card Refund Credit Memo Currency Revaluation Customer Deposit Customer Payment Customer Refund Deposit Deposit Application Estimate Expense Report Intercompany Journal Entry Advanced Intercompany Journal Entry Item Fulfillment Item Receipt Journal Entry Opportunity Purchase Order Transfer Vendor Bill Vendor Credit Vendor Payment	Supported. Confirm field permissions and sync direction.
Lead Case Published Reports	Reading: Request access. Updating this object: confirm availability.

Read the SuiteAnalytics connector guide

TiDB

Connection and object support require review

Record types to review with Stacksync

Record types	Coverage and requirements
Tables Databases Views Columns Indexes Sequences	Confirm support for this record type and the direction you need.

Discuss TiDB requirements

Connection essentials

Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.

View setup requirements and limits

Connection requirement	SuiteAnalytics	TiDB
Integration interface	SQL over ODBC, JDBC, and ADO.NET (SuiteAnalytics Connect)	MySQL wire protocol (SQL)
Authentication	NetSuite token-based authentication with integration credentials, access token, account ID, and a role with SuiteAnalytics permissions.	Confirm the credentials, API plan, and permissions required for TiDB.
Change detection	The saved Stacksync guide does not specify the change-detection mechanism.	Confirm how Stacksync detects changes for this connector and the objects you need.
Read access	Available for supported records	Confirm with Stacksync
Write access	Not supported by this connector	Confirm with Stacksync

Enterprise controls

Security and control for your integrations

Explore security controls

Compliance and data transfers

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Record-level recovery

Inspect sync errors and use retry and revert controls to resolve failed updates.

Read the recovery guide

Implementation

Technical reference

Review setup, record relationships, testing, and recovery for your implementation.

Authentication, permissions and API limits

Connection requirements and limits

SuiteAnalytics

Integration interface: SQL over ODBC, JDBC, and ADO.NET (SuiteAnalytics Connect)
Authentication: NetSuite token-based authentication with integration credentials, access token, account ID, and a role with SuiteAnalytics permissions.
Change detection: The saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
Read access: Available for supported records
Write access: Not supported by this connector

Setup requirements

Have a NetSuite administrator enable SuiteAnalytics Connect and token-based authentication.
Create an integration, access token, and role with the SuiteAnalytics Connect permissions listed in the authorization guide.

Limitations to check

SuiteAnalytics is a read-only route. Use a separately supported NetSuite connector for write-back requirements.

Technical documentation

Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.

SuiteAnalytics setup guide

TiDB

Integration interface: MySQL wire protocol (SQL)
Authentication: Confirm the credentials, API plan, and permissions required for TiDB.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Setup requirements

Identify the TiDB account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for TiDB, including read/write support, authentication, and initial-load limits.

Limitations to check

Confirm Stacksync support for TiDB and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Prepare SuiteAnalytics and TiDB access

Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.

SuiteAnalytics setup checklist

Have a NetSuite administrator enable SuiteAnalytics Connect and token-based authentication.
Create an integration, access token, and role with the SuiteAnalytics Connect permissions listed in the authorization guide.

Setup guides: Authorize SuiteAnalytics NetSuite SuiteAnalytics Connect

TiDB setup checklist

Identify the TiDB account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for TiDB, including read/write support, authentication, and initial-load limits.

Prepare to go live

Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.

Use the SuiteAnalytics and TiDB planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

Talk to an engineer · Review current pricing

Record identity and field ownership

Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.

Download the mapping worksheet · CSV, no email required

Reporting dataset

Customer / Proposed customer table in TiDB (choose its name)

Plan a customer dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

SuiteAnalytics: Documented record · Read: Supported. Write: see guide.
TiDB: Your database schema
Record identity: Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
Field ownership: Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.

Fields to include

Source customer ID
Person/company classification
Legal entity or business unit
Destination identity reference

Record dependencies: Resolve person or company type, legal entity, business role, and any billing account before transactions.
Validation: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Recovery: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

References: SuiteAnalytics: Customer documentation

Reporting dataset

Invoice / Proposed customer invoice table in TiDB (choose its name)

Plan a customer invoice dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

SuiteAnalytics: Documented record · Supported
TiDB: Your database schema
Record identity: Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap.
Field ownership: The financial system owns posting and accounting treatment. A posted invoice may need a credit or adjustment process instead of an overwrite.

Fields to include

Source invoice ID
Customer or supplier reference
Line totals
Currency
Posting/payment status

Record dependencies: Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting.
Validation: Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.
Recovery: Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.

References: SuiteAnalytics: Invoice documentation

Reporting dataset

Vendor Bill / Proposed supplier bill table in TiDB (choose its name)

Plan a supplier bill dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

SuiteAnalytics: Documented record · Supported
TiDB: Your database schema
Record identity: Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice.
Field ownership: Accounts payable owns approval and posting; a supplier bill is not an accounts-receivable invoice.

Fields to include

Source bill ID
Supplier reference
Entity
Line amounts and currency
Approval/posting state

Record dependencies: Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.
Validation: Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.
Recovery: Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.

References: SuiteAnalytics: Vendor Bill documentation

Reporting dataset

Sales Order / Proposed sales order table in TiDB (choose its name)

Plan a sales order dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

SuiteAnalytics: Documented record · Supported
TiDB: Your database schema
Record identity: Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices.
Field ownership: Decide which system approves the order and which can cancel or amend it after fulfillment begins.

Fields to include

Source order ID
Customer reference
Line references and quantities
Order status
Currency

Record dependencies: Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Validation: Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
Recovery: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

References: SuiteAnalytics: Sales Order documentation

Reporting dataset

Customer Payment / Proposed payment or settlement table in TiDB (choose its name)

Plan a payment or settlement dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

SuiteAnalytics: Documented record · Supported
TiDB: Your database schema
Record identity: Preserve transaction ID, provider/source, currency, and links to invoices; one payment may settle several documents.
Field ownership: Keep payment authorization, settlement, and accounting allocation distinct.

Fields to include

Source transaction ID
Invoice references
Amount and currency
Settlement status
Reversal reference

Record dependencies: Resolve the affected invoices and cash/account references before allocating the payment.
Validation: Test partial payment, one-to-many allocation, refund, and repeated delivery of the same transaction.
Recovery: Look up the original transaction before retrying to prevent duplicate allocation or charging.

References: SuiteAnalytics: Customer Payment documentation

Reporting dataset

Vendor / Proposed supplier or vendor table in TiDB (choose its name)

Plan a supplier or vendor dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

SuiteAnalytics: Documented record · Read: Supported. Write: see guide.
TiDB: Your database schema
Record identity: Use the supplier ID within its business entity; a supplier name may occur in several subsidiaries.
Field ownership: Assign responsibility for approved supplier details; restrict changes to payment instructions to the business approval process.

Fields to include

Source supplier ID
Legal name
Entity reference
Payment terms
Active status

Record dependencies: Resolve business-unit and payment-term references before purchasing transactions.
Validation: Test a supplier shared across subsidiaries and an inactive supplier referenced by an open bill.
Recovery: Review rejected supplier changes before retrying dependent bills; do not reactivate a supplier merely to make a write pass.

References: SuiteAnalytics: Vendor documentation

Compare integration approaches

Choose a method around one example record and the update your business needs. Use Customer / Proposed customer table in TiDB (choose its name) to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.

Stacksync managed sync

Best fit: Review compatibility with a Stacksync engineer using an example of the records and updates you need.
Operating responsibility: Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose: Check record matching: Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. Verify field coverage, deletion handling, and how changes are detected.

Native vendor integration

Best fit: A vendor-built integration may fit if it supports your SuiteAnalytics and TiDB record types.
Operating responsibility: Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose: First check whether either vendor offers this integration. If available, verify Customer / Proposed customer table in TiDB (choose its name), update direction, account tier, and related-record handling.

Custom API or workflow

Best fit: Consider when SuiteAnalytics and TiDB need a transformation, approval, or action outside a direct record sync.
Operating responsibility: Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose: Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery. Separate reading history from actions that send messages, grant access, or post transactions.

File or scheduled snapshot

Best fit: Consider for a one-time SuiteAnalytics / TiDB migration or a reporting need with an explicit freshness window.
Operating responsibility: Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose: Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow scenarios and expected results

Customer reporting workflow

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Customer or Proposed customer table in TiDB (choose its name) record needs a defined result in the other system.

Start with SuiteAnalytics Customer and TiDB Proposed customer table in TiDB (choose its name). Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Customer invoice reporting workflow

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Invoice or Proposed customer invoice table in TiDB (choose its name) record needs a defined result in the other system.

Start with SuiteAnalytics Invoice and TiDB Proposed customer invoice table in TiDB (choose its name). Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.

If it fails: Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.

Supplier bill reporting workflow

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Vendor Bill or Proposed supplier bill table in TiDB (choose its name) record needs a defined result in the other system.

Start with SuiteAnalytics Vendor Bill and TiDB Proposed supplier bill table in TiDB (choose its name). Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.

If it fails: Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.

Reconcile SuiteAnalytics business records with TiDB

This is an evaluation scenario; connector and operation support require confirmation.

Starting event: A finance-owned record in SuiteAnalytics needs operational visibility through a selected destination dataset.

Select Customer or Vendor with the correct legal entity, period, and currency.
Define a reporting relationship in TiDB; do not equate customer records, ledger accounts, and posted transactions.
Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.

Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.

If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.

Initial load and acceptance testing

Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.

Customer / Proposed customer table in TiDB (choose its name)

Test case

Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

Expected result

The expected customer relationship is preserved with no duplicate action or unintended write.

Invoice / Proposed customer invoice table in TiDB (choose its name)

Test case

Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.

Expected result

The expected customer invoice relationship is preserved with no duplicate action or unintended write.

Vendor Bill / Proposed supplier bill table in TiDB (choose its name)

Test case

Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.

Expected result

The expected supplier bill relationship is preserved with no duplicate action or unintended write.

Sales Order / Proposed sales order table in TiDB (choose its name)

Test case

Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.

Expected result

The expected sales order relationship is preserved with no duplicate action or unintended write.

Direction and permissions

Test case

Bring an example source record and the intended destination operation to the compatibility review. Confirm the supported route before granting write access.

Expected result

Only an approved, supported direction and permitted fields are written.

Freshness and reconciliation

Test case

Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.

Expected result

The process meets its agreed freshness target and reconciliation has no unexplained differences.

Failed updates, retries and recovery

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

Rejected or repeated customer change

Investigate

Inspect SuiteAnalytics Customer and TiDB Proposed customer table in TiDB (choose its name), their IDs, and the destination error.

Next action

Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Rejected or repeated customer invoice change

Investigate

Inspect SuiteAnalytics Invoice and TiDB Proposed customer invoice table in TiDB (choose its name), their IDs, and the destination error.

Next action

Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.

Rejected or repeated supplier bill change

Investigate

Inspect SuiteAnalytics Vendor Bill and TiDB Proposed supplier bill table in TiDB (choose its name), their IDs, and the destination error.

Next action

Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.

A record type or update is unavailable

Investigate

Check the SuiteAnalytics and TiDB connector guides, account permissions, and any operations marked On Request.

Next action

Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.

Source and destination disagree after a retry

Investigate

Compare current source values, destination validation, identity mappings, and any side effects already completed.

Next action

Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.

Read the Stacksync issues dashboard guide for retry and revert behavior.

Change detection and update delivery

How updates move between SuiteAnalytics and TiDB

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

SuiteAnalytics TiDB Direction requires confirmation

Detect changesThe saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.

Apply updatesConfirm that Stacksync can create or update the records you need in TiDB.

TiDB SuiteAnalytics Direction not supported

Detect changesThis route requires read access from TiDB and write access to SuiteAnalytics; the documented connector restrictions do not permit it.

Apply updatesUse a supported direction or review a separate integration method for this requirement.

Update timing and record limits

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
Review write-back, deletion handling, update timing, and account limits with the integration team.

FAQ

SuiteAnalytics and TiDB integration FAQ

Resources for your technical review

Next step

Plan your integration with an engineer

Walk through your SuiteAnalytics and TiDB records, field mappings, and requirements with an integration engineer.

Talk to an engineer Explore plans and pricing