IQMS (DELMIAworks)
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. |
ERP / Database · Two-way sync platform
IQMS (DELMIAworks) and MongoDB integration
Plan how IQMS (DELMIAworks) and MongoDB 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 reporting workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting eventA change involving IQMS (DELMIAworks) Customers or the proposed customer table in MongoDB needs a defined result in the other system.
Start with IQMS (DELMIAworks) Customers and the proposed customer table in MongoDB. 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 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
| IQMS (DELMIAworks) record | MongoDB record | Record matching | Field ownership |
|---|---|---|---|
| CustomersProposed record; confirm Stacksync object support.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. |
| Bills of MaterialsProposed record; confirm Stacksync object support.Reporting 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. |
| Sales OrdersProposed record; confirm Stacksync object support.Reporting dataset | Proposed sales order tableProposed table; choose its name and schema. | Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices. | Decide which system approves the order and which can cancel or amend it after fulfillment begins. |
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.
MongoDB
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| See connector requirements. Confirm field permissions and sync direction. |
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 | IQMS (DELMIAworks) | MongoDB |
|---|---|---|
| Integration interface | Database-level access and vendor integration interfaces; no broadly documented public REST API | MongoDB wire protocol via official drivers; Atlas additionally offers an administration REST API for cluster management |
| Authentication | Confirm the credentials, API plan, and permissions required for IQMS (DELMIAworks). | Database credentials |
| Change detection | Confirm how Stacksync detects changes for this connector and the objects you need. | Stacksync uses MongoDB oplog and change streams. |
| Read access | Confirm with Stacksync | Available for supported records |
| Write access | Confirm with Stacksync | Available for supported records |
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
IQMS (DELMIAworks)
- Integration interface
- Database-level access and vendor integration interfaces; no broadly documented public REST API
- Authentication
- Confirm the credentials, API plan, and permissions required for IQMS (DELMIAworks).
- 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 IQMS (DELMIAworks) account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for IQMS (DELMIAworks), including read/write support, authentication, and initial-load limits.
Limitations to check
- Confirm Stacksync support for IQMS (DELMIAworks) and the record types your workflow needs.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
MongoDB
- Integration interface
- MongoDB wire protocol via official drivers; Atlas additionally offers an administration REST API for cluster management
- Authentication
- Database credentials (username/password) or TLS/SSL X.509 certificate (.pem upload), entered individually or via a MongoDB connection string (SRV or standard); Stacksync IP allowlisting required
- Change detection
- Stacksync uses MongoDB oplog and change streams. A replica set is required, including for a single-node deployment.
- Read access
- Available for supported records
- Write access
- Available for supported records
Setup requirements
- Use auto-generated ObjectId values for collection _id keys and run the database as a replica set.
- Allow Stacksync network access and grant database-level permissions to read/write collections and access the oplog.
Limitations to check
- Individual collection-only permission grants are insufficient for change replication; grant access at the database level.
- Only ObjectId collection keys are supported; SSH tunneling has protocol and deployment restrictions in the guide.
Technical documentation
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Prepare IQMS (DELMIAworks) and MongoDB 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.
IQMS (DELMIAworks) setup checklist
- Identify the IQMS (DELMIAworks) account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for IQMS (DELMIAworks), including read/write support, authentication, and initial-load limits.
MongoDB setup checklist
- Use auto-generated ObjectId values for collection _id keys and run the database as a replica set.
- Allow Stacksync network access and grant database-level permissions to read/write collections and access the oplog.
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 IQMS (DELMIAworks) and MongoDB 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
Customers / Proposed customer table in MongoDB (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.
- IQMS (DELMIAworks)
- Object support to establish
- MongoDB
- 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.
Reporting dataset
Bills of Materials / Proposed supplier bill table in MongoDB (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.
- IQMS (DELMIAworks)
- Object support to establish
- MongoDB
- 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.
Reporting dataset
Sales Orders / Proposed sales order table in MongoDB (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.
- IQMS (DELMIAworks)
- Object support to establish
- MongoDB
- 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.
Reporting dataset
Suppliers / Proposed supplier or vendor table in MongoDB (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.
- IQMS (DELMIAworks)
- Object support to establish
- MongoDB
- 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.
Reporting dataset
Bills of Materials / Proposed product or catalog item table in MongoDB (choose its name)
Plan a product or catalog item dataset while preserving its source meaning.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- IQMS (DELMIAworks)
- Object support to establish
- MongoDB
- Your database schema
- Record identity
- Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys.
- Field ownership
- Assign ownership for catalog content, price, and stock separately.
Fields to include
- Source product ID
- SKU or variant reference
- Description
- Unit of measure
- Price-list reference
- Record dependencies
- Resolve units, variants, categories, and applicable price lists before order lines.
- Validation
- Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.
- Recovery
- Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.
Reporting dataset
Items & Inventory / Proposed inventory or stock position table in MongoDB (choose its name)
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.
- IQMS (DELMIAworks)
- Object support to establish
- MongoDB
- Your database schema
- 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.
Compare integration approaches
Choose a method around one example record and the update your business needs. Use Customers / Proposed customer table in MongoDB (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 IQMS (DELMIAworks) and MongoDB 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 Customers / Proposed customer table in MongoDB (choose its name), update direction, account tier, and related-record handling.
Custom API or workflow
- Best fit
- Consider when IQMS (DELMIAworks) and MongoDB 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 IQMS (DELMIAworks) / MongoDB 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 Customers or Proposed customer table in MongoDB (choose its name) record needs a defined result in the other system.
- Start with IQMS (DELMIAworks) Customers and MongoDB Proposed customer table in MongoDB (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.
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 Bills of Materials or Proposed supplier bill table in MongoDB (choose its name) record needs a defined result in the other system.
- Start with IQMS (DELMIAworks) Bills of Materials and MongoDB Proposed supplier bill table in MongoDB (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.
Sales order reporting workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Sales Orders or Proposed sales order table in MongoDB (choose its name) record needs a defined result in the other system.
- Start with IQMS (DELMIAworks) Sales Orders and MongoDB Proposed sales order table in MongoDB (choose its name). Use the record-matching and field-ownership rules from your mapping worksheet.
- Create or locate the customer and products first; resolve taxes, currency, and fulfillment 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 a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
If it fails: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Reconcile IQMS (DELMIAworks) business records with MongoDB
This is an evaluation scenario; connector and operation support require confirmation.
Starting event: A finance-owned record in IQMS (DELMIAworks) needs operational visibility through Documents or Embedded documents and arrays.
- Select Sales Orders or Items & Inventory with the correct legal entity, period, and currency.
- Define a reporting relationship in MongoDB; 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.
Customers / Proposed customer table in MongoDB (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.
Bills of Materials / Proposed supplier bill table in MongoDB (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 Orders / Proposed sales order table in MongoDB (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.
Suppliers / Proposed supplier or vendor table in MongoDB (choose its name)
Test case
Test a supplier shared across subsidiaries and an inactive supplier referenced by an open bill.
Expected result
The expected supplier or vendor 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 IQMS (DELMIAworks) Customers and MongoDB Proposed customer table in MongoDB (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 supplier bill change
Investigate
Inspect IQMS (DELMIAworks) Bills of Materials and MongoDB Proposed supplier bill table in MongoDB (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.
Rejected or repeated sales order change
Investigate
Inspect IQMS (DELMIAworks) Sales Orders and MongoDB Proposed sales order table in MongoDB (choose its name), their IDs, and the destination error.
Next action
Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
A record type or update is unavailable
Investigate
Check the IQMS (DELMIAworks) and MongoDB 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 IQMS (DELMIAworks) and MongoDB
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
IQMS (DELMIAworks) MongoDB 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 MongoDB.
MongoDB IQMS (DELMIAworks) Direction requires confirmation
Detect changesStacksync uses MongoDB oplog and change streams. A replica set is required, including for a single-node deployment.
Apply updatesConfirm that Stacksync can create or update the records you need in IQMS (DELMIAworks).
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
IQMS (DELMIAworks) and MongoDB integration FAQ
-
Explore a IQMS (DELMIAworks) and MongoDB integration with a Stacksync engineer. Stacksync support for IQMS (DELMIAworks) 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.
-
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 Customers in IQMS (DELMIAworks) and Proposed customer table in MongoDB (choose its name) in MongoDB. 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 Customers / Proposed customer table in MongoDB (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.
-
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Identify the IQMS (DELMIAworks) account, edition, environment, and business objects the integration must access. Use auto-generated ObjectId values for collection _id keys and run the database as a replica set. Use the pair worksheet to record ownership and acceptance criteria.
Integration directory
Related integrations
Review documented support, sync direction, and setup requirements on each pair page. Search all 305 integrations listed for IQMS (DELMIAworks) and MongoDB.
Popular · 4 of 305
No integrations match .
Next step
Plan your integration with an engineer
Walk through your IQMS (DELMIAworks) and MongoDB records, field mappings, and requirements with an integration engineer.
