Creatio to Microsoft Dynamics 365 Business Central — SmartTracks Partner Certification
Your Creatio–Business Central SmartTracks Reference, Explained
This program walks Net@Work's consultants through installing, configuring, building, and supporting a Creatio ↔ Microsoft Dynamics 365 Business Central integration on the InterWeave SmartIntegration Hub.
The guide is organized as a reference manual, not a linear course — it follows the natural lifecycle of an engagement (install, configure, map, build, operate, support) so a consultant can read it end-to-end during onboarding or jump straight to the part relevant to the task at hand. This is a companion certification track for Net@Work, InterWeave's implementation partner for Creatio–Business Central engagements, not a single end-customer's configuration document.
The eleven modules below map one-to-one to the eleven parts of the underlying Implementation Guide. Three certification tracks group those modules by role — most consultants only need one track, with Modules 01 and 11 relevant to everyone.
Three Tracks, One Platform
Choose the track that matches your role on a Net@Work engagement. Solution Architect builds on Implementation Consultant certification.
Install, Configure & Go Live
For consultants who install, configure, and go live on customer engagements — standing up the Hub, connecting both systems, and activating SmartFlows BC-01 through BC-04.
Support Live Customers
For staff supporting live customers post-go-live — reading sync status, diagnosing errors, running steady-state operations, and responding to incidents.
Scope Custom Work
For staff scoping custom SmartFlows and complex deployments — extending the standard integration beyond the BC-01–BC-04 set.
Eleven Modules, Three Tracks
Work through the modules assigned to your track in order. Module 01 and Module 11 are shared by everyone.
Installation Guide
What "installation" means for a SaaS-delivered Hub, Business Central and Creatio prerequisites, the pre-installation checklist, and how to verify a new Hub instance before moving to configuration.
VIEW FULL LESSON →SmartIntegration Configuration Guide
The L1/L2/L3 pipeline every sync event passes through, connecting Creatio and Business Central, activating SmartFlows BC-01–BC-04 in dependency order, and setting a conflict-resolution policy.
VIEW FULL LESSON →Business Central Guide
The three supported Business Central deployment models, Azure AD app registration and OAuth 2.0 setup, required permission sets, and on-premises/Power Platform notes.
VIEW FULL LESSON →Creatio Guide
Creatio REST API prerequisites, webhook and event configuration for sub-5-second sync latency, entity-to-object mapping, and required permissions and security roles.
VIEW FULL LESSON →SmartFlow Development Guide
SmartFlow architecture (retry, dead-letter handling, sequencing), FlowCopilot's natural-language configuration, building a custom SmartFlow, trigger types, and Sandbox-to-Production deployment.
VIEW FULL LESSON →Field Mapping Guide
The L1/L2/L3 mapping model, standard entity mappings shipped with BC-01–BC-04, custom field mapping, and currency/tax/unit-of-measure transformation rules.
VIEW FULL LESSON →Troubleshooting Guide
IWSyncRegistry and IWSyncLog as the two places to check record health, the most common sync error categories and resolutions, the diagnostic workflow, and the escalation path to InterWeave Support.
VIEW FULL LESSON →Administration Guide
User and role management principles, monitoring and alerting configuration, the sync status dashboard and reports, environment management, and platform uptime SLAs by support tier.
VIEW FULL LESSON →Best Practices Guide
The master-data-sync-first principle, the standard three-phase/eight-week rollout, conflict-resolution design patterns, performance optimization, and security/PII handling.
VIEW FULL LESSON →Operations Runbook
The daily operations checklist, incident response procedure, planned maintenance and change windows, the 30-day hypercare model, and the implementation-to-steady-state handoff checklist.
VIEW FULL LESSON →Consultant Certification Manual
The SmartTracks certification overview, the three certification tracks and prerequisites, what each module assesses, exam and renewal (pending InterWeave enablement input), and partner enablement resources.
VIEW FULL LESSON →Module Detail
The complete content for each module. Work through your track in order — Module 01 and Module 11 first and last, everything else in between.
- Explain what "installation" means for a SaaS-delivered Hub
- List the Business Central and Creatio prerequisites needed before provisioning
- Work through the pre-installation checklist with a customer
- Verify a new Hub instance is healthy before moving to Module 02
1.1 What Installation Actually Means
The InterWeave SmartIntegration Hub is event-driven middleware sitting between Creatio and Business Central. Neither system is modified to support the integration — no custom fields, schema changes, or code are added to either one. All sync logic lives inside the Hub's configurable rule layer.
Because the Hub is delivered as managed SaaS, "installation" is a configuration and connectivity exercise — provisioning a Hub instance and establishing the network and credential path to the customer's environments — rather than a software deployment onto customer infrastructure.
1.2 Prerequisites
Business Central: Online, On-Premises, or Power Platform deployment (Module 03 covers all three), an Azure AD tenant with app-registration rights, and a named integration user with the permission set from Module 03. Creatio: REST API enabled, and a dedicated integration user with the security role from Module 04.
1.3 Pre-Installation Checklist
Complete this with the customer before scheduling the Phase 1 kickoff in the standard eight-week implementation plan (Module 09).
- Business Central deployment type confirmed (Online / On-Premises / Power Platform)
- Business Central tenant/company ID(s) identified for sandbox and production
- Creatio environment URL and edition confirmed
- Integration user accounts created in both systems, or an owner assigned to create them
- Network/firewall change owner identified on the customer side, if required
- InterWeave partner sandbox environment provisioned for the consultant (Module 11)
- Kickoff meeting scheduled with the customer's CRM and Finance stakeholders
1.4 Provisioning & Verifying the Installation
- Request a new Hub instance for the customer through the InterWeave Partner Portal.
- Select the connector pack: Creatio (source) and Business Central (bi-directional).
- Enter Business Central connection details per the deployment type (Module 03).
- Enter Creatio connection details (Module 04).
- Run the built-in connectivity test for both systems.
- Confirm the Hub instance shows "Connected" for both systems before proceeding to Module 02.
Before moving on, confirm: both connectors show Connected; a test record in each sandbox appears in IWSyncLog with a logged event; and no authentication or permission errors appear in the Hub's connection diagnostics panel.
- SmartIntegration Hub
- The core service instance being provisioned for a customer
- Connector Ecosystem
- Pre-built Creatio and Business Central connectors, licensed as part of Hub provisioning
- IWSyncRegistry
- System table tracking sync status per entity (synced / pending / error)
- IWSyncLog
- System table logging every sync attempt with timestamp, event, and result
- Describe the three-layer pipeline every sync event passes through
- Connect a provisioned Hub instance to a Creatio and Business Central tenant
- Activate SmartFlows BC-01–BC-04 in the correct dependency order
- Set a conflict-resolution policy before activating BC-01
2.1 The Three-Layer Pipeline
Every sync event passes through three configurable layers before it's written to the receiving system. Every attempt — successful or not — is logged to IWSyncLog, and every synced entity carries a live status in IWSyncRegistry.
| Layer | Function |
|---|---|
| L1 — Entity Match | Determines whether an incoming record corresponds to an existing one, matching by tax ID, email, or external ID, to prevent duplicates |
| L2 — Transformation | Converts field values between systems: currency, tax codes, units of measure, address formats, picklists |
| L3 — Orchestration | Sequences the write, applies conflict-resolution rules, retries on transient failure, writes with a full audit trail |
2.2–2.3 Connecting Both Systems
From the Hub instance: open Connectors → Creatio, enter the environment base URL, choose OAuth 2.0 client credentials as the authentication method, enter the integration user's client ID/secret, and run Test Connection — a successful test returns the Creatio version and confirms the integration user's role. For Business Central, open Connectors → Business Central, select the deployment type, authenticate per Module 03, select the target company, and run Test Connection.
2.4 Configuring SmartFlows BC-01–BC-04
Once both connectors report Connected, activate SmartFlows in dependency order. BC-01 is the foundation and must go live first; BC-02 depends on it, and BC-03/BC-04 can be configured in parallel once BC-01 is validated. Always activate a new SmartFlow in Sandbox first.
| SmartFlow | Direction | Depends On | Purpose |
|---|---|---|---|
| BC-01 — Master Data Sync | Creatio ↔ BC | — | Customers, vendors, contacts — the foundation flow |
| BC-02 — Sales & Financial Sync | Creatio → BC → Creatio | BC-01 | Sales orders, invoices, payment status |
| BC-03 — Inventory & Item Sync | BC → Creatio | BC-01 | Item catalog, multi-location inventory availability |
| BC-04 — Purchasing & Production Sync | Creatio ↔ BC | BC-01 | Purchase orders, Bill of Materials, production order status |
2.5–2.6 Conflict Resolution & End-to-End Testing
Before activating BC-01, set the conflict-resolution policy: source-of-truth by field (e.g. Business Central always wins on payment terms) or source-of-truth by system (one system wins for all fields on an entity type, with per-field exceptions). Anything outside the configured rule set is flagged in IWSyncRegistry for manual review, never silently applied.
- Create a test customer in Creatio sandbox; confirm it appears in Business Central sandbox within the target sync latency (under 5 seconds)
- Update the same customer's address in Business Central; confirm it flows back to Creatio
- Review IWSyncLog for both events; confirm status = synced with no errors
- Deliberately trigger a conflict and confirm the configured rule behaves as expected
- Confirm no duplicate customer record was created — validates L1 entity matching
- Identify Business Central's three supported deployment types
- Complete Azure AD app registration and OAuth 2.0 setup
- Know the permission set the integration user requires
- Understand the on-premises web service tier and Power Platform notes
3.1 Supported Deployment Types
Confirm which model the customer runs before starting connector configuration — the connection method and prerequisites differ meaningfully.
| Deployment | Connection Method | Notes |
|---|---|---|
| Business Central Online (SaaS) | OData v4 API · Power Platform connectors | Preferred deployment; fastest to provision, supports Copilot and Power BI natively |
| Business Central On-Premises | OData API · Web Services (SOAP) | Requires an on-premises web service tier reachable by InterWeave |
| Business Central with Power Platform | Dataverse virtual tables · Power Automate | For customers standardizing on the Microsoft Power Platform ecosystem |
3.2 Azure AD App Registration & OAuth 2.0
- Register a new application under the customer's Azure AD tenant (or reuse an existing integration app registration).
- Add the Business Central API permission and grant admin consent.
- Generate a client secret and record its expiration date.
- Note the Tenant ID, Client ID, and Client Secret for entry into the Hub's connector screen (Module 02).
- Confirm the integration user or service principal has the required permission set.
3.3–3.4 API Access & Permissions
The Hub reads and writes Business Central data through the standard OData v4 API surface — Customers, Vendors, Items, Sales Orders, Purchase Orders, and related entities — rather than direct database access, which is what allows the integration to work without schema changes. The integration user or service principal should hold the narrowest permission set that covers these objects; see Module 09's security guidance for the broader principle.
- Complete Creatio REST API prerequisites for a new integration user
- Configure webhook or polling-based event triggers
- Map Creatio entities to their Business Central objects
- Know the security role the integration user requires
4.2 Creatio REST API Prerequisites
- Confirm the Creatio REST API is enabled for the target environment.
- Create a dedicated integration user — never reuse a named employee's login.
- Register an OAuth 2.0 client for the integration user, or generate API credentials per edition.
- Assign the integration user the required security role (Section 4.5).
- Record the environment base URL and credentials for the Hub's Creatio connector screen (Module 02).
4.3 Webhook & Event Configuration
Creatio-originating triggers run in either event-driven (webhook) or polling mode. Event-driven mode delivers the platform's sub-5-second sync latency target; polling is a fallback when webhook delivery isn't feasible on the customer's network.
4.4 Entity & Section Mapping
| Creatio Entity | Business Central Object | Direction | SmartFlow |
|---|---|---|---|
| Account | Customer Card / Vendor Card | Creatio ↔ BC | BC-01 |
| Contact | Contact Card | Creatio ↔ BC | BC-01 |
| Opportunity / Order | Sales Order / Invoice | Creatio → BC | BC-02 |
| Product / Price List Item | Item Card | BC → Creatio | BC-03 |
| Purchase Request | Purchase Order | Creatio → BC | BC-04 |
| Production / Project Milestone | Production Order | BC → Creatio | BC-04 |
- Describe SmartFlow retry, dead-letter, and sequencing behavior
- Explain what FlowCopilot does — and doesn't — configure unassisted
- Walk through the steps to build a custom SmartFlow
- List the Creatio and Business Central trigger types
5.1 SmartFlow Architecture
| Capability | Description |
|---|---|
| Retry | Transient failures are retried on a backoff schedule before being flagged as an error |
| Dead-letter handling | Permanently failed events move to a dead-letter queue for manual review, never dropped silently |
| Sequencing | Related events process in order so a dependent record is never written before its parent exists |
5.2 FlowCopilot: Natural-Language Configuration
FlowCopilot is the Hub's natural-language assistant for configuring SmartFlows and sync rules. A consultant describes the desired behavior in plain language — e.g. "sync the customer's credit limit from Business Central to Creatio but never write it back" — and FlowCopilot proposes the corresponding mapping and directionality for review before it's applied.
5.3–5.4 Building a Custom SmartFlow & Triggers
Most engagements only need the standard BC-01–BC-04 set. A custom SmartFlow is appropriate when a customer needs to sync an entity not covered by the standard set — for example, a custom Creatio section or a Business Central extension table.
- Define the source and target entity, and the sync direction.
- Define the trigger(s) that fire the flow.
- Define or reuse an L1 entity-match rule so the flow doesn't create duplicates.
- Define the L2 field transformation rules (Module 06).
- Define the L3 orchestration behavior: retry policy, sequencing dependencies, conflict-resolution rule.
- Name and document the flow using the BC-0X convention, or a customer-specific prefix.
- Test thoroughly in Sandbox before requesting production deployment.
Custom SmartFlow scoping and pricing follow the "Additional sync SmartFlow" line item in the standard InterWeave pricing model (design, build, test, and documentation included per flow).
5.5–5.6 Testing & Production Deployment
- Run each trigger scenario individually in Sandbox and confirm the correct downstream write
- Run a bulk/batch scenario (50+ records) to confirm sequencing and retry behavior under volume
- Deliberately break a scenario and confirm it fails gracefully into IWSyncLog rather than partially writing
- Confirm the flow respects the conflict-resolution policy from Module 02
As a general principle: never enable a new or modified SmartFlow directly in Production. Promote from a validated Sandbox configuration during a scheduled change window (Module 10).
- Explain the L1/L2/L3 mapping model at the field level
- Reference the standard BC-01–BC-04 entity mappings
- Understand currency, tax, and unit-of-measure transformation behavior
- Follow the mapping change-management process
6.1–6.2 Mapping Model & Standard Entity Mappings
Every mapped field passes through the same three-layer model used throughout the platform: L1 identifies whether a record already exists in the target system, L2 converts the value into the target's expected format, and L3 sequences and writes the transformed value. After transformation, the Hub writes a complete, traceable record — neither system needs to interpret raw data from the other.
Standard mappings shipped with BC-01–BC-04 mirror the entity table in Module 04, Section 4.4 — use it as the starting point for any new implementation before considering customer-specific customization.
6.3 Custom Field Mapping
Custom field mapping beyond the standard scope follows the "Custom field mapping" pricing line item. Document every custom mapping in the customer's environment-specific addendum so future consultants inherit the context.
6.4 Transformation Rules
| Data Type | Transformation Behavior |
|---|---|
| Currency | Converted using the target system's current exchange rate; original and converted values both retained for audit |
| Tax codes | Mapped via a configurable crosswalk; unmapped codes held for review rather than defaulted |
| Units of measure | Converted using Business Central's UoM conversion table; multi-location rollups respect each location's base UoM |
| Addresses | Reformatted to the target system's expected structure |
A transformation that can't be resolved — an unrecognized currency code, for example — holds the record in IWSyncRegistry as "error" rather than writing a guessed or default value.
6.5 Mapping Validation & Change Management
- Test every mapping change in Sandbox against a representative sample of real records
- Document the change, its owner, and its rationale in the environment-specific addendum
- Confirm the change doesn't conflict with an existing conflict-resolution rule
- Communicate the change to the customer's CRM and Finance stakeholders before promoting to Production
- Use IWSyncRegistry and IWSyncLog to check a record's sync health
- Recognize the platform's common sync error categories
- Follow the diagnostic workflow from symptom to resolution
- Know what to gather before escalating to InterWeave Support
7.1–7.2 IWSyncRegistry & IWSyncLog
IWSyncRegistry holds current sync status per entity (synced / pending / error) and the last successful sync timestamp. IWSyncLog holds the full event history — every sync attempt, successful or not, with a timestamp, source event, and result. The full field-level reference for both tables lives in the source Implementation Guide.
7.3 Common Sync Errors & Resolutions
| Issue | Cause | Resolution |
|---|---|---|
| Partial write to Business Central | Transmission failure mid-write | No write is ever confirmed without the complete record; the event stays in the retry queue |
| Duplicate customer/vendor record | L1 entity match couldn't confidently resolve the record | Flagged for manual review in IWSyncRegistry, never auto-merged |
| Conflicting bi-directional edits | Same record changed in both systems in the sync window | Resolved per the configured conflict rule; anything outside it is flagged |
| Currency/tax/UoM mismatch | Value doesn't map per the L2 rules | Logged, not dropped — update the crosswalk and re-queue |
| Inventory sync failure (BC-03) | Business Central inventory read didn't complete | Existing values aren't overwritten by an unconfirmed read; supports on-demand re-sync |
7.4–7.5 Diagnostic Workflow & Escalation
- Start in IWSyncRegistry: locate the record, confirm its status and last successful sync.
- Cross-reference IWSyncLog for that record's event history and the specific error on the failed attempt.
- Match the error against Section 7.3; if it's a mapping issue, resolve it in Module 06 and re-queue.
- If it's connectivity or permissions, revisit Module 02, 03, or 04.
- If the record still fails, escalate — with the record's IWSyncRegistry status, the relevant IWSyncLog event ID(s), the SmartFlow involved, and steps already attempted.
| Support Tier | Support Model | Platform Uptime SLA |
|---|---|---|
| Professional | Business hours | 99.5% |
| Enterprise | Priority support + dedicated CSM | 99.9% |
| Ultimate | 24/7 enterprise support | 99.95% |
- Apply least-privilege role assignment for Hub users
- Configure alert routing so sync errors reach the right owner
- Know what the sync status dashboard surfaces in Creatio
- Keep Sandbox and Production environments clearly separated
8.1–8.2 User Management & Monitoring
Assign the narrowest role that lets each person do their job: administrators who can change connector credentials and mapping configuration should be a short, named list; support and consulting staff who only need to review sync status and logs should have read-only access. Configure alert routing during initial setup — Business Central connectivity alerts to the customer's IT owner and InterWeave support; data-conflict alerts to the business owner best positioned to resolve them.
8.3 Sync Status Dashboard & Reports
The Hub surfaces operational reports directly in Creatio, giving Sales, Finance, and Operations one view without direct Business Central access: sync status by object type, records pending or in error, and last sync timestamp; account balance and payment status; open purchase/production orders and real-time inventory availability.
8.4–8.6 Environments, Governance & SLA
Label every environment clearly (Sandbox / Production, plus company name for multi-company customers) and never point a Production SmartFlow at a Sandbox company. PII and financial fields flagged in IWSyncRegistry are encrypted in the transformation layer and excluded from integration logs; all data in transit uses TLS 1.3. Confirm the customer's contracted support tier during onboarding — it determines both uptime SLA and escalation path (Module 07).
- Explain why BC-01 must always be validated before BC-02–BC-04
- Walk a customer through the standard three-phase rollout
- Apply conflict-resolution design patterns during discovery
- Follow the platform's security and PII handling practices
9.1 Master-Data-Sync-First Principle
BC-01 is the foundation flow every other SmartFlow depends on. Customers, vendors, and contacts must be reliably synchronized and de-duplicated before sales, inventory, or purchasing data layers on top — a Sales Order synced against an unresolved or duplicate Customer creates exactly the mismatch the platform is designed to prevent. Never sequence BC-02, BC-03, or BC-04 ahead of a validated BC-01.
9.2 Phased Rollout Strategy
| Phase | Focus | Weeks | Key Deliverables |
|---|---|---|---|
| 1 | Foundation: Master Data Sync | 1–3 | API credentials validated; BC-01 deployed and tested; stakeholder validation workshop |
| 2 | Sales, Financial & Inventory Sync | 4–6 | BC-02 and BC-03 configured and validated; full UAT with Sales and Finance |
| 3 | Purchasing, Production & Go-Live | 7–8 | BC-04 tested; reports configured; production go-live; 30-day hypercare begins |
9.3–9.5 Conflict Patterns, Performance & Security
Decide the conflict-resolution model during discovery, not during Phase 1 build. Two patterns cover most engagements: Business Central as source of truth for financial fields (payment terms, credit limits, pricing), and Creatio as source of truth for relationship fields (communication preferences, account ownership). Keep the rule set narrow and explicit — anything outside it should be flagged for manual review, not silently resolved by a default.
If sync latency is consistently slower than the sub-5-second target, check in order: trigger mode (event-driven vs. polling), Business Central deployment type, batch volume, and custom SmartFlow complexity. On security: use dedicated, narrowly-scoped integration users — never a named employee's login — and track Azure AD client secret expiration on a shared calendar owned by the implementation team.
- Run the daily operations checklist
- Follow the incident response procedure for a real sync disruption
- Schedule changes inside a defined change window
- Complete the implementation-to-steady-state handoff
10.1 Daily Operations Checklist
- Review the sync status dashboard for records in "error" status older than the customer's SLA window
- Review IWSyncLog for dead-lettered events from the prior 24 hours
- Confirm both connectors still show "Connected" — flag any credential expiration warnings
- Spot-check the flagged-conflict queue and route unresolved items to the right business owner
10.2 Incident Response Procedure
An "incident" is a disruption serious enough to affect business operations — not an individual record error, which follows the normal Module 07 workflow.
- Confirm scope: a single SmartFlow, a full connector outage, or a Hub-wide issue.
- Check IWSyncLog and the connector status panel for when the disruption began and what changed just before it.
- If it's a connector-level failure, stop the affected SmartFlow(s) rather than letting failed events queue indefinitely.
- Notify the customer's designated contact per their SLA tier, and escalate to InterWeave Support if unresolvable at the partner level.
- Once resolved, reconcile every record affected during the outage window rather than assuming the retry queue caught everything.
- Document the incident, root cause, and resolution.
10.3–10.5 Change Windows, Hypercare & Handoff
Schedule SmartFlow promotions, field mapping changes, bulk data loads, and credential rotations during a defined low-activity change window, communicated in advance. Every implementation includes a 30-day hypercare period after go-live, with closer monitoring and the implementation consultant remaining primary contact. At the end of hypercare, confirm all contracted SmartFlows are live with zero unresolved errors, documentation is complete, the customer's administrators have walked through the dashboard, and a formal handoff meeting has transitioned primary contact to standard support.
- Understand the goal of SmartTracks certification for Net@Work consultants
- Match your role to the correct certification track
- Know what each module is assessed on
- Find the partner enablement resources you'll need throughout an engagement
11.1 SmartTracks Certification Overview
SmartTracks is InterWeave's guided implementation and enablement methodology, extended here into a certification program for partner consultants. The goal: a Net@Work consultant who completes SmartTracks certification should be able to independently install, configure, and support a standard Creatio ↔ Business Central integration using this guide as their reference, escalating to InterWeave only for platform-level issues rather than basic configuration questions.
11.2 Certification Tracks & Prerequisites
| Track | Intended For | Prerequisite |
|---|---|---|
| Implementation Consultant | Consultants who install, configure, and go live on engagements | Modules 01–06, hands-on Sandbox access |
| Support Engineer | Staff supporting live customers post-go-live | Modules 07, 08, and 10 |
| Solution Architect | Staff scoping custom SmartFlows and complex deployments | Implementation Consultant certification, plus Modules 05 and 09 in depth |
11.3–11.6 What Each Certification Module Assesses
- Module 1 — Platform Fundamentals: explain, without reference material, how a single record moves from a Creatio event to a written Business Central record.
- Module 2 — Connector Installation & Configuration: successfully complete the end-to-end connection test (Module 02, Section 2.6) in a live sandbox.
- Module 3 — SmartFlow Development: complete the sandbox validation checklist (Module 05, Section 5.5) against a working BC-01 deployment.
- Module 4 — Troubleshooting & Support: correctly diagnose and resolve a set of seeded sync errors in a training sandbox.
11.7–11.8 Exam, Renewal & Partner Resources
| Resource | Where to Find It |
|---|---|
| Partner Portal — sandbox provisioning, documentation, certification tracking | partner.interweave.biz |
| Sales & partnership inquiries | sales@interweave.biz |
| Phone (USA) | (203) 274-5226 |
| Phone (Canada) | 1-800-671-8692 |
| Primary partner contact | Bruce Magown, CEO & Founder — bmagown@interweave.biz |
- SmartTracks
- InterWeave's guided implementation and partner certification methodology
- BC-01–BC-04
- The four standard SmartFlows covering master data, sales/financial, inventory, and purchasing/production sync
- L1 / L2 / L3
- Entity Match, Transformation, and Orchestration — the three layers every sync event passes through
- Hypercare
- The 30-day period of closer monitoring immediately following production go-live
BC-01 – BC-04, At a Glance
Keep this table open while configuring — it's the fast lookup for direction, dependency, and purpose.
| SmartFlow | Entities | Direction | Depends On |
|---|---|---|---|
| BC-01 — Master Data Sync | Account/Contact → Customer/Vendor/Contact Card | Creatio ↔ BC | — |
| BC-02 — Sales & Financial Sync | Opportunity/Order → Sales Order/Invoice | Creatio → BC → Creatio | BC-01 |
| BC-03 — Inventory & Item Sync | Item Card → Product/Price List Item | BC → Creatio | BC-01 |
| BC-04 — Purchasing & Production Sync | Purchase Order, Production Order ↔ Purchase Request, Milestone | Creatio ↔ BC | BC-01 |
Frequently Asked Questions
Answers to the questions Net@Work consultants ask most often during onboarding.
Get Help When You're Stuck
Three resources, in the order most Net@Work consultants need them.
InterWeave Partner Portal
Sandbox provisioning, documentation, and certification tracking for Net@Work consultants.
partner.interweave.biz →InterWeave Academy & Help Center
Revisit these modules anytime, plus broader Creatio and Business Central documentation and support articles.
academy.interweave.biz →Primary Partner Contact
For partnership, scope, or engagement-level questions outside self-service: Bruce Magown, CEO & Founder.
bmagown@interweave.biz →Scope reminder. This is a Version 0.1 working draft prepared for Net@Work as InterWeave's implementation partner. "Engineering Input Needed" callouts throughout mark sections that require real technical detail from InterWeave engineering before this is finalized as partner enablement material — verify every screen, exact step, and current field name against the live platform before using this guide with an actual customer engagement.