Apache Cassandra
Connection and object support require review
Record types to review with Stacksync
| Record types | Coverage and requirements |
|---|---|
| Confirm support for this record type and the direction you need. |
Database / ERP · Two-way sync platform
Apache Cassandra and Sage 300 integration
Plan how Apache Cassandra and Sage 300 should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.
- Scope your workflow with an integration engineer
- Review the systems, records, and updates you need
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 invoice reporting workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting eventA change involving the proposed customer invoice table in Apache Cassandra or Sage 300 AR Invoices and Receipts needs a defined result in the other system.
Start with the proposed customer invoice table in Apache Cassandra and Sage 300 AR Invoices and Receipts. 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.
What to verifyTest a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.
Review records and field ownershipProposed record relationships
Records to connect
Use these examples to define record matching and field ownership for your technical review.
Download the mapping worksheetCSV · No email required
| Apache Cassandra record | Sage 300 record | Record matching | Field ownership |
|---|---|---|---|
| Proposed customer invoice tableProposed table; choose its name and schema.Reporting dataset | AR Invoices and ReceiptsProposed record; confirm Stacksync object support. | 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. |
| Proposed journal or ledger entry tableProposed table; choose its name and schema.Reporting dataset | Journal BatchesProposed record; confirm Stacksync object support. | Retain journal ID and line IDs within the legal entity and accounting period. | The ledger owns posting approval and period controls; an integration should not treat a posted journal as an ordinary editable row. |
| Proposed inventory or stock position tableProposed table; choose its name and schema.Reporting dataset | Inventory ItemsProposed record; confirm Stacksync object support. | Identify stock by product/variant, location, and any lot or serial dimension; a product ID alone is insufficient. | Choose the stock authority and distinguish available, reserved, and physical quantities. |
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.
Sage 300
Connection and object support require review
Record types to review with Stacksync
| Record types | Coverage and requirements |
|---|---|
| Confirm support for this record type and the direction you need. |
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 | Apache Cassandra | Sage 300 |
|---|---|---|
| Integration interface | CQL over the Cassandra native binary protocol | Sage 300 Web API (REST) on newer releases; .NET/COM SDK and direct SQL Server access on-prem |
| Authentication | Confirm the credentials, API plan, and permissions required for Apache Cassandra. | Confirm the credentials, API plan, and permissions required for Sage 300. |
| Change detection | Confirm how Stacksync detects changes for this connector and the objects you need. | Confirm how Stacksync detects changes for this connector and the objects you need. |
| Read access | Confirm with Stacksync | Confirm with Stacksync |
| Write access | Confirm with Stacksync | Confirm with Stacksync |
Enterprise controls
Security and control for your integrations
Explore security controlsCompliance 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 guideImplementation
Technical reference
Review setup, record relationships, testing, and recovery for your implementation.
Authentication, permissions and API limits
Connection requirements and limits
Apache Cassandra
- Integration interface
- CQL over the Cassandra native binary protocol
- Authentication
- Confirm the credentials, API plan, and permissions required for Apache Cassandra.
- 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 Apache Cassandra account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Apache Cassandra, including read/write support, authentication, and initial-load limits.
Limitations to check
- Confirm Stacksync support for Apache Cassandra and the record types your workflow needs.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
Sage 300
- Integration interface
- Sage 300 Web API (REST) on newer releases; .NET/COM SDK and direct SQL Server access on-prem
- Authentication
- Confirm the credentials, API plan, and permissions required for Sage 300.
- 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 Sage 300 account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Sage 300, including read/write support, authentication, and initial-load limits.
Limitations to check
- Confirm Stacksync support for Sage 300 and the record types your workflow needs.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
Prepare Apache Cassandra and Sage 300 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.
Apache Cassandra setup checklist
- Identify the Apache Cassandra account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Apache Cassandra, including read/write support, authentication, and initial-load limits.
Sage 300 setup checklist
- Identify the Sage 300 account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Sage 300, 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 Apache Cassandra and Sage 300 planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
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
Proposed customer invoice table in Apache Cassandra (choose its name) / AR Invoices and Receipts
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.
- Apache Cassandra
- Your database schema
- Sage 300
- Object support to establish
- 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.
Reporting dataset
Proposed journal or ledger entry table in Apache Cassandra (choose its name) / Journal Batches
Plan a journal or ledger entry dataset while preserving its source meaning.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Apache Cassandra
- Your database schema
- Sage 300
- Object support to establish
- Record identity
- Retain journal ID and line IDs within the legal entity and accounting period.
- Field ownership
- The ledger owns posting approval and period controls; an integration should not treat a posted journal as an ordinary editable row.
Fields to include
- Source journal ID
- Account references
- Debit/credit amounts
- Entity
- Accounting period
- Record dependencies
- Resolve chart-of-account, currency, entity, and dimension references before lines.
- Validation
- Verify balanced debits and credits, dimension requirements, and rejection for a closed period.
- Recovery
- Reconcile posting status and use the finance-approved reversal or adjustment process instead of replaying a posted entry.
Reporting dataset
Proposed inventory or stock position table in Apache Cassandra (choose its name) / Inventory Items
Plan a inventory or stock position dataset while preserving its source meaning.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Apache Cassandra
- Your database schema
- Sage 300
- Object support to establish
- Record identity
- Identify stock by product/variant, location, and any lot or serial dimension; a product ID alone is insufficient.
- Field ownership
- Choose the stock authority and distinguish available, reserved, and physical quantities.
Fields to include
- Product reference
- Location reference
- Quantity type
- Quantity
- As-of time
- Record dependencies
- Resolve product, unit, warehouse/location, and lot/serial references.
- Validation
- Test the same SKU in two locations, a reservation, and an older snapshot arriving late.
- Recovery
- Reconcile the latest stock position before retrying; do not apply an old absolute quantity after new movements.
Reporting dataset
Proposed purchase order table in Apache Cassandra (choose its name) / Purchase Orders
Plan a purchase order dataset while preserving its source meaning.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Apache Cassandra
- Your database schema
- Sage 300
- Object support to establish
- Record identity
- Retain purchase-order and line IDs together with the supplier and legal-entity context.
- Field ownership
- Keep procurement approval separate from receipt and payment states.
Fields to include
- Source purchase-order ID
- Supplier reference
- Line references
- Quantity
- Approval status
- Record dependencies
- Resolve supplier, product, business unit, and delivery-location references before lines.
- Validation
- Test a partially received purchase order and an amendment after approval.
- Recovery
- Reconcile receipts already recorded before resubmitting an amended order.
Compare integration approaches
Choose a method around one example record and the update your business needs. Use Proposed customer invoice table in Apache Cassandra (choose its name) / AR Invoices and Receipts 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: Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap. 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 Apache Cassandra and Sage 300 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 Proposed customer invoice table in Apache Cassandra (choose its name) / AR Invoices and Receipts, update direction, account tier, and related-record handling.
Custom API or workflow
- Best fit
- Consider when Apache Cassandra and Sage 300 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 Apache Cassandra / Sage 300 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 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 Proposed customer invoice table in Apache Cassandra (choose its name) or AR Invoices and Receipts record needs a defined result in the other system.
- Start with Apache Cassandra Proposed customer invoice table in Apache Cassandra (choose its name) and Sage 300 AR Invoices and Receipts. 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.
Journal or ledger entry reporting workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Proposed journal or ledger entry table in Apache Cassandra (choose its name) or Journal Batches record needs a defined result in the other system.
- Start with Apache Cassandra Proposed journal or ledger entry table in Apache Cassandra (choose its name) and Sage 300 Journal Batches. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve chart-of-account, currency, entity, and dimension references before 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: Verify balanced debits and credits, dimension requirements, and rejection for a closed period.
If it fails: Reconcile posting status and use the finance-approved reversal or adjustment process instead of replaying a posted entry.
Inventory or stock position reporting workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Proposed inventory or stock position table in Apache Cassandra (choose its name) or Inventory Items record needs a defined result in the other system.
- Start with Apache Cassandra Proposed inventory or stock position table in Apache Cassandra (choose its name) and Sage 300 Inventory Items. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve product, unit, warehouse/location, and lot/serial references.
- 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 the same SKU in two locations, a reservation, and an older snapshot arriving late.
If it fails: Reconcile the latest stock position before retrying; do not apply an old absolute quantity after new movements.
Reconcile Sage 300 business records with Apache Cassandra
This is an evaluation scenario; connector and operation support require confirmation.
Starting event: A finance-owned record in Sage 300 needs operational visibility through a selected destination dataset.
- Select Journal Batches or Purchase Orders with the correct legal entity, period, and currency.
- Define a reporting relationship in Apache Cassandra; 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.
Proposed customer invoice table in Apache Cassandra (choose its name) / AR Invoices and Receipts
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.
Proposed journal or ledger entry table in Apache Cassandra (choose its name) / Journal Batches
Test case
Verify balanced debits and credits, dimension requirements, and rejection for a closed period.
Expected result
The expected journal or ledger entry relationship is preserved with no duplicate action or unintended write.
Proposed inventory or stock position table in Apache Cassandra (choose its name) / Inventory Items
Test case
Test the same SKU in two locations, a reservation, and an older snapshot arriving late.
Expected result
The expected inventory or stock position relationship is preserved with no duplicate action or unintended write.
Proposed purchase order table in Apache Cassandra (choose its name) / Purchase Orders
Test case
Test a partially received purchase order and an amendment after approval.
Expected result
The expected purchase 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 invoice change
Investigate
Inspect Apache Cassandra Proposed customer invoice table in Apache Cassandra (choose its name) and Sage 300 AR Invoices and Receipts, 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 journal or ledger entry change
Investigate
Inspect Apache Cassandra Proposed journal or ledger entry table in Apache Cassandra (choose its name) and Sage 300 Journal Batches, their IDs, and the destination error.
Next action
Reconcile posting status and use the finance-approved reversal or adjustment process instead of replaying a posted entry.
Rejected or repeated inventory or stock position change
Investigate
Inspect Apache Cassandra Proposed inventory or stock position table in Apache Cassandra (choose its name) and Sage 300 Inventory Items, their IDs, and the destination error.
Next action
Reconcile the latest stock position before retrying; do not apply an old absolute quantity after new movements.
A record type or update is unavailable
Investigate
Check the Apache Cassandra and Sage 300 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 Apache Cassandra and Sage 300
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
Apache Cassandra Sage 300 Direction requires confirmation
Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.
Apply updatesConfirm that Stacksync can create or update the records you need in Sage 300.
Sage 300 Apache Cassandra Direction requires confirmation
Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.
Apply updatesConfirm that Stacksync can create or update the records you need in Apache Cassandra.
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.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
FAQ
Apache Cassandra and Sage 300 integration FAQ
-
Explore a Apache Cassandra and Sage 300 integration with a Stacksync engineer. Stacksync support for Apache Cassandra and Sage 300 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.
-
Confirm two-way support with Stacksync for the records and fields you need in both systems. Access to a vendor API does not confirm that its Stacksync connector supports write-back.
-
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Identify the Apache Cassandra account, edition, environment, and business objects the integration must access. Identify the Sage 300 account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.
-
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
-
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.
-
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.
-
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.
-
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.
-
Start by reviewing Proposed customer invoice table in Apache Cassandra (choose its name) in Apache Cassandra and AR Invoices and Receipts in Sage 300. 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.
-
Choose a method around one example record and the update your business needs. Use Proposed customer invoice table in Apache Cassandra (choose its name) / AR Invoices and Receipts 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.
Integration directory
Related integrations
Review documented support, sync direction, and setup requirements on each pair page. Search all 433 integrations listed for Apache Cassandra and Sage 300.
Popular · 7 of 433
-
Apache Cassandra and Acumatica -
Apache Cassandra and SAP S/4HANA -
Apache Cassandra and Odoo -
Sage 300 and Airtable -
Sage 300 and AWS Aurora MySQL - Sage 300 and AWS Aurora PostgreSQL
-
Sage 300 and MongoDB
No integrations match .
Next step
Plan your integration with an engineer
Walk through your Apache Cassandra and Sage 300 records, field mappings, and requirements with an integration engineer.
