Microsoft Dynamics NAV
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 / Marketing · Two-way sync platform
Microsoft Dynamics NAV and RollWorks integration
Plan how Microsoft Dynamics NAV and RollWorks 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 sync test
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting eventA change involving Microsoft Dynamics NAV Customers or RollWorks Accounts (TAL Items) needs a defined result in the other system.
Start with Microsoft Dynamics NAV Customers and RollWorks Accounts (TAL Items). 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
| Microsoft Dynamics NAV record | RollWorks record | Record matching | Field ownership |
|---|---|---|---|
| CustomersProposed record; confirm Stacksync object support.Customer identity assessment | Accounts (TAL Items)Proposed record; confirm Stacksync object support. | 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. |
| CompaniesProposed record; confirm Stacksync object support.Record matching | Accounts (TAL Items)Proposed record; confirm Stacksync object support. | Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. | Assign ownership separately for relationship details and finance-controlled billing details. |
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.
RollWorks
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 | Microsoft Dynamics NAV | RollWorks |
|---|---|---|
| Integration interface | SOAP and OData web services published from NAV pages and codeunits; direct SQL Server access on-premises | REST APIs (Audience, Prospecting v2) plus a GraphQL Reporting API |
| Authentication | Confirm the credentials, API plan, and permissions required for Microsoft Dynamics NAV. | Confirm the credentials, API plan, and permissions required for RollWorks. |
| 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
Microsoft Dynamics NAV
- Integration interface
- SOAP and OData web services published from NAV pages and codeunits; direct SQL Server access on-premises
- Authentication
- Confirm the credentials, API plan, and permissions required for Microsoft Dynamics NAV.
- 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 Microsoft Dynamics NAV account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Microsoft Dynamics NAV, including read/write support, authentication, and initial-load limits.
Limitations to check
- Confirm Stacksync support for Microsoft Dynamics NAV and the record types your workflow needs.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
RollWorks
- Integration interface
- REST APIs (Audience, Prospecting v2) plus a GraphQL Reporting API
- Authentication
- Confirm the credentials, API plan, and permissions required for RollWorks.
- 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 RollWorks account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for RollWorks, including read/write support, authentication, and initial-load limits.
Limitations to check
- Confirm Stacksync support for RollWorks and the record types your workflow needs.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
Prepare Microsoft Dynamics NAV and RollWorks 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.
Microsoft Dynamics NAV setup checklist
- Identify the Microsoft Dynamics NAV account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Microsoft Dynamics NAV, including read/write support, authentication, and initial-load limits.
RollWorks setup checklist
- Identify the RollWorks account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for RollWorks, 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 Microsoft Dynamics NAV and RollWorks 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
Customer identity
Customers / Accounts (TAL Items)
Before linking Microsoft Dynamics NAV Customers to RollWorks Accounts (TAL Items), check whether the customer is an individual or a company. Match the correct record type in each system.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Microsoft Dynamics NAV
- Object support to establish
- RollWorks
- Object support to establish
- 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.
Record matching
Companies / Accounts (TAL Items)
Compare whether Microsoft Dynamics NAV Companies and RollWorks Accounts (TAL Items) describe the same company in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Microsoft Dynamics NAV
- Object support to establish
- RollWorks
- Object support to establish
- Record identity
- Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient.
- Field ownership
- Assign ownership separately for relationship details and finance-controlled billing details.
Fields to include
- Source record ID
- Legal or display name
- Business-unit reference
- Lifecycle status
- Record dependencies
- Resolve parent organizations, business units, and currency references before dependent transactions.
- Validation
- Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.
- Recovery
- Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.
Compare integration approaches
Choose a method around one example record and the update your business needs. Use Customers / Accounts (TAL Items) 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 Microsoft Dynamics NAV and RollWorks 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 / Accounts (TAL Items), update direction, account tier, and related-record handling.
Custom API or workflow
- Best fit
- Consider when Microsoft Dynamics NAV and RollWorks 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 Microsoft Dynamics NAV / RollWorks 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 sync test
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Customers or Accounts (TAL Items) record needs a defined result in the other system.
- Start with Microsoft Dynamics NAV Customers and RollWorks Accounts (TAL Items). 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.
Company sync test
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Companies or Accounts (TAL Items) record needs a defined result in the other system.
- Start with Microsoft Dynamics NAV Companies and RollWorks Accounts (TAL Items). Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve parent organizations, business units, and currency references before dependent 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: Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.
If it fails: Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.
Reconcile Microsoft Dynamics NAV business records with RollWorks
This is an evaluation scenario; connector and operation support require confirmation.
Starting event: A finance-owned record in Microsoft Dynamics NAV needs operational visibility through Accounts (TAL Items) or Campaigns.
- Select Customers or Vendors with the correct legal entity, period, and currency.
- Define a reporting relationship in RollWorks; 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 / Accounts (TAL Items)
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.
Companies / Accounts (TAL Items)
Test case
Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.
Expected result
The expected company 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 Microsoft Dynamics NAV Customers and RollWorks Accounts (TAL Items), 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 company change
Investigate
Inspect Microsoft Dynamics NAV Companies and RollWorks Accounts (TAL Items), their IDs, and the destination error.
Next action
Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.
A record type or update is unavailable
Investigate
Check the Microsoft Dynamics NAV and RollWorks 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 Microsoft Dynamics NAV and RollWorks
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
Microsoft Dynamics NAV RollWorks 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 RollWorks.
RollWorks Microsoft Dynamics NAV 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 Microsoft Dynamics NAV.
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
Microsoft Dynamics NAV and RollWorks integration FAQ
Integration directory
Related integrations
Review documented support, sync direction, and setup requirements on each pair page. Search all 368 integrations listed for Microsoft Dynamics NAV and RollWorks.
Next step
Plan your integration with an engineer
Walk through your Microsoft Dynamics NAV and RollWorks records, field mappings, and requirements with an integration engineer.
