MarkLogic
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 / Analytics · Two-way sync platform
MarkLogic and Microsoft Power BI integration
Plan how MarkLogic and Microsoft Power BI 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
Event or activity reporting workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting eventA change involving the proposed event or activity table in MarkLogic or Microsoft Power BI Refresh History needs a defined result in the other system.
Start with the proposed event or activity table in MarkLogic and Microsoft Power BI Refresh History. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve the related customer, user, or transaction identity without assuming the event ID is the entity ID.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
What to verifyDeliver the same event twice, then an older event after a newer one; verify duplicate and ordering behavior.
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
| MarkLogic record | Microsoft Power BI record | Record matching | Field ownership |
|---|---|---|---|
| Proposed event or activity tableProposed table; choose its name and schema.Reporting dataset | Refresh HistoryProposed record; confirm Stacksync object support. | Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key. | Decide whether the destination stores an immutable history or only a current-state summary. |
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.
Microsoft Power BI
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 | MarkLogic | Microsoft Power BI |
|---|---|---|
| Integration interface | REST API (Client API), plus SQL/ODBC access over TDE views and Java/Node client libraries | Power BI REST API, including the Execute Queries (DAX) endpoint and admin scanner APIs; a read-write XMLA endpoint is available on Premium, Premium-Per-User, and Fabric capacity. |
| Authentication | Confirm the credentials, API plan, and permissions required for MarkLogic. | Confirm the credentials, API plan, and permissions required for Microsoft Power BI. |
| 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
MarkLogic
- Integration interface
- REST API (Client API), plus SQL/ODBC access over TDE views and Java/Node client libraries
- Authentication
- Confirm the credentials, API plan, and permissions required for MarkLogic.
- 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 MarkLogic account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for MarkLogic, including read/write support, authentication, and initial-load limits.
Limitations to check
- Confirm Stacksync support for MarkLogic and the record types your workflow needs.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
Microsoft Power BI
- Integration interface
- Power BI REST API, including the Execute Queries (DAX) endpoint and admin scanner APIs; a read-write XMLA endpoint is available on Premium, Premium-Per-User, and Fabric capacity.
- Authentication
- Confirm the credentials, API plan, and permissions required for Microsoft Power BI.
- 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 Power BI account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Microsoft Power BI, including read/write support, authentication, and initial-load limits.
Limitations to check
- Confirm Stacksync support for Microsoft Power BI and the record types your workflow needs.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
Prepare MarkLogic and Microsoft Power BI 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.
MarkLogic setup checklist
- Identify the MarkLogic account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for MarkLogic, including read/write support, authentication, and initial-load limits.
Microsoft Power BI setup checklist
- Identify the Microsoft Power BI account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Microsoft Power BI, 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 MarkLogic and Microsoft Power BI 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 event or activity table in MarkLogic (choose its name) / Refresh History
Plan a event or activity dataset while preserving its source meaning.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- MarkLogic
- Your database schema
- Microsoft Power BI
- Object support to establish
- Record identity
- Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key.
- Field ownership
- Decide whether the destination stores an immutable history or only a current-state summary.
Fields to include
- Source event ID
- Event type
- Occurred-at time
- Related record ID
- Payload version
- Record dependencies
- Resolve the related customer, user, or transaction identity without assuming the event ID is the entity ID.
- Validation
- Deliver the same event twice, then an older event after a newer one; verify duplicate and ordering behavior.
- Recovery
- Identify side effects already completed before replaying an event; use the agreed deduplication key.
Compare integration approaches
Choose a method around one example record and the update your business needs. Use Proposed event or activity table in MarkLogic (choose its name) / Refresh History 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: Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key. 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 MarkLogic and Microsoft Power BI 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 event or activity table in MarkLogic (choose its name) / Refresh History, update direction, account tier, and related-record handling.
Custom API or workflow
- Best fit
- Consider when MarkLogic and Microsoft Power BI 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.
File or scheduled snapshot
- Best fit
- Consider for a one-time MarkLogic / Microsoft Power BI 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
Event or activity 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 event or activity table in MarkLogic (choose its name) or Refresh History record needs a defined result in the other system.
- Start with MarkLogic Proposed event or activity table in MarkLogic (choose its name) and Microsoft Power BI Refresh History. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve the related customer, user, or transaction identity without assuming the event ID is the entity ID.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Deliver the same event twice, then an older event after a newer one; verify duplicate and ordering behavior.
If it fails: Identify side effects already completed before replaying an event; use the agreed deduplication key.
Define an explicit handoff between MarkLogic and Microsoft Power BI
This is an evaluation scenario; connector and operation support require confirmation.
Starting event: A business event involving Documents or Document Metadata & Properties needs a defined response involving Refresh History or Activity Events (Audit Log).
- Document what the source event means and which destination record or action should respond. A similar name does not establish a shared entity.
- Retain separate IDs and choose whether the destination is a report, a new work item, or a change to an existing record.
- Assign an approval owner and a duplicate-detection rule before running an action. Use a custom workflow only after its endpoint support is confirmed.
Expected result: An example input has an unambiguous destination and expected result; repeated delivery produces only the intended change.
If it fails: Resolve missing identity or ambiguous business meaning before retrying; route unsupported operations to the implementation owner.
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 event or activity table in MarkLogic (choose its name) / Refresh History
Test case
Deliver the same event twice, then an older event after a newer one; verify duplicate and ordering behavior.
Expected result
The expected event or activity 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 event or activity change
Investigate
Inspect MarkLogic Proposed event or activity table in MarkLogic (choose its name) and Microsoft Power BI Refresh History, their IDs, and the destination error.
Next action
Identify side effects already completed before replaying an event; use the agreed deduplication key.
A record type or update is unavailable
Investigate
Check the MarkLogic and Microsoft Power BI 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 MarkLogic and Microsoft Power BI
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
MarkLogic Microsoft Power BI 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 Power BI.
Microsoft Power BI MarkLogic 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 MarkLogic.
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
MarkLogic and Microsoft Power BI integration FAQ
-
Explore a MarkLogic and Microsoft Power BI integration with a Stacksync engineer. Stacksync support for MarkLogic and Microsoft Power BI 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 MarkLogic account, edition, environment, and business objects the integration must access. Identify the Microsoft Power BI 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 event or activity table in MarkLogic (choose its name) in MarkLogic and Refresh History in Microsoft Power BI. 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 event or activity table in MarkLogic (choose its name) / Refresh History 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 370 integrations listed for MarkLogic and Microsoft Power BI.
Next step
Plan your integration with an engineer
Walk through your MarkLogic and Microsoft Power BI records, field mappings, and requirements with an integration engineer.
