MEX Integration with Dynamics 365 Business Central User Guide
Introduction
The MEX Integration extension integrates MEX Maintenance Management Software with Microsoft Dynamics 365 Business Central. It enables real-time, automated data exchange between the two systems --- eliminating manual re-entry of maintenance data, keeping inventory records accurate, and ensuring financial transactions reflect what happens on the ground.
For more information or to obtain the extension, contact:
David Blumentals
Director, Dynamics 365 Practice, David@d365.Global
WhatsApp +61 409 245 354.
What Does This Extension Do?
This extension connects MEX and Business Central across five key areas:
-
Items & Catalogue --- Pulls the MEX parts catalogue into Business Central as inventory or non-inventory items.
-
Goods Receipts --- Pushes purchase receipt data from BC back to MEX to confirm receipt of goods.
-
Resources (Employees) --- Synchronises BC resources (with trade skills) to MEX as employees.
-
Fixed Assets --- Registers new assets in MEX and keeps asset status (Active, Disposed, Idle, etc.) in sync.
-
Work Orders & Requisitions --- Pulls MEX work orders and purchase requisitions into BC for financial processing.
Who Should Read This Guide?
This guide is written for end users who interact with Business Central day-to-day. You do not need a technical background. Specific sections are marked to indicate whether they are relevant to procurement staff, maintenance coordinators, finance users, or store/warehouse staff.
Key Benefits
-
No more duplicate data entry --- Changes in MEX flow into BC automatically.
-
Accurate inventory levels --- MEX catalogue transactions update BC stock journals.
-
Faster purchase processing --- MEX requisitions become BC purchase requisitions in one click.
-
Up-to-date asset records --- Asset status changes in BC are pushed to MEX instantly.
-
Fewer errors --- Automated validation catches missing data before it reaches MEX.
⚠ Note: This extension is a Cloud (SaaS) deployment and requires Business Central version 25.x or above. It also requires the d365.Global Purchase Requisition extension (version 1.0.0.9 or above) to be installed.
Getting Started
Prerequisites
Before using this extension, confirm the following with your system administrator:
-
The MEX Integration Setup has been configured (** Base URL**, ** API Key**, and all endpoints are filled in).
-
You have been assigned the appropriate Business Central permissions for the areas you will use.
-
The d365.Global Purchase Requisition extension is installed and set up.
-
MEX API access has been granted and the API Key is active.
Finding MEX-Related Pages in Business Central
All MEX integration pages are accessible via the Business Central search bar. Press Alt + Q (or click the magnifying glass icon) and type any of the following:
| Page Name | What It Shows | Who Uses It |
|---|---|---|
| MEX Integration Setup | Central configuration for all MEX connections | Administrators |
| MEX Work Order List | Work orders pulled from MEX | Maintenance / Finance |
| Mex Requisitions | Purchase requisitions from MEX pending action | Procurement |
| MEX Staging Assets | Assets received from MEX pending review | Asset Managers |
| MEX Staging Work Orders | Work orders in staging before import | Maintenance |
| Item Import Staging | Items pulled from MEX catalogue staging | Warehouse / Procurement |
| MEX Error Log | Integration errors requiring attention | All users |
| Catalogue Transaction | MEX inventory movement transactions | Warehouse / Finance |
| Fixed Asset List | Fixed assets with MEX sync status | Asset Managers |
| Resource List | Resources with MEX sync status | HR / Maintenance |
Understanding Sync Status
Many records in Business Central will display a MEX Sync Status field. This tells you whether a record has been successfully sent to or received from MEX:
| Status | Meaning | Action Required |
|---|---|---|
| (Blank) | Record has not yet been synced | Trigger sync manually or wait for scheduled run |
| Success | Record synced successfully with MEX | None |
| Error | Sync failed — details in MEX Sync Message | Check the error message and correct the data |
⚠ Note: If a record shows an Error status, open the record and read the MEX Sync Message field --- it will describe exactly what went wrong.
Items & Catalogue Synchronisation
The MEX catalogue contains all parts, materials, and supplies managed by the maintenance team. This extension pulls the MEX catalogue into Business Central, creating or updating items automatically.
How Items Are Pulled from MEX
When a catalogue sync is triggered, the extension calls the MEX API and downloads all catalogue entries. For each item it receives:
-
If the item does not exist in BC, it is created automatically with the MEX Catalogue Number as the Item No..
-
The item’s type is set to Inventory (if stocked in MEX) or Non-Inventory (if not stocked).
-
Description, Unit of Measure, Vendor No., Vendor Item No., and Unit Price are populated from MEX data.
-
Items are first held in the Item Import Staging table for review before being created in BC.
Triggering a Catalogue Sync
-
Search for MEX Integration Setup and open it.
-
In the ribbon, click Synchronization > Sync Items.
-
The extension fetches the latest catalogue from MEX and updates the staging table.
-
Staged items are then automatically processed into BC items.
⚠ Note: If an item’s Unit of Measure or Vendor cannot be found in BC, the item will not be created and an error will be logged in the MEX Error Log. Ensure all UOMs and Vendors exist in BC before syncing.
Reviewing Staged Items
-
Search for Item Import Staging and open the list.
-
Review items that have not yet been processed (Processed = No).
-
Errors are visible in the MEX Error Log --- search for MEX Error Log to open it.
-
Once all errors are resolved, re-run the sync to process remaining items.
Catalogue Transactions (Stock Movements)
MEX records stock issues and returns against work orders. These are called Catalogue Transactions. The extension pulls these transactions and creates Item Journal Lines in Business Central for financial posting.
-
Issue transactions in MEX become Negative Adjustment journal lines in BC (reducing stock).
-
Return to Stock transactions become Positive Adjustment journal lines in BC (increasing stock).
-
Journal lines are linked to the MEX Work Order ID for traceability.
ℹ Info: If Auto Post Catalogue Transactions is enabled in MEX Integration Setup, journal lines are created automatically. Otherwise, you will need to review and post them manually from the Item Journal.
Good Receipts
When goods are received in Business Central against a purchase order, this extension automatically notifies MEX. This keeps MEX informed of stock arrivals so maintenance teams can see when parts are available.
How It Works
The sync works as follows:
-
A purchase order is received in BC (i.e. a Posted Purchase Receipt is created).
-
The receipt lines are sent to MEX via the Goods Receipt API endpoint.
-
Each receipt line is posted with: Purchase Order Number, Line Number, Quantity Received, Unit Cost, Date Received, and Region Name.
-
MEX confirms receipt --- the BC receipt line is updated with a MEX Sync Status of Success.
Triggering a Goods Receipt Sync
-
Search for MEX Integration Setup and open it.
-
Click Synchronization > Sync Good Receipts.
-
The extension finds the most recent Posted Purchase Receipt and sends its lines to MEX.
-
Check the MEX Sync Status on the receipt lines to confirm success.
Checking Sync Status on a Receipt
-
Go to Purchases > Posted Receipts and open the relevant receipt.
-
In the receipt lines, look for the MEX Sync Status and MEX Sync Message fields.
-
A Success status means MEX has been notified.
-
An Error status means the sync failed --- read the MEX Sync Message for details.
⚠ Note: Only the most recent Posted Purchase Receipt is synced in each run. If you need to resync older receipts, contact your administrator.
Resources (Employees)
Business Central Resources represent maintenance workers and tradespeople. This extension synchronises these resources to MEX as employees, including their trade skills, rates, and active status.
What Is Synced
| BC Field | MEX Field | Notes |
|---|---|---|
| Resource No. | Employee Number | Used as the unique identifier |
| Name | First Name | Full name goes to first name field |
| Name 2 | Last Name | |
| Blocked | Is Active | Blocked = false means active in MEX |
| Resource Skills | Trades | Each skill becomes a trade with rate and markup |
| Skill Code | Trade Code | Must match a valid MEX trade code |
| Internal Rate | Internal Rate | Hourly cost rate |
| Mark Up Amount | Markup Amount | Applied on top of internal rate |
Syncing Resources to MEX
-
Search for MEX Integration Setup and open it.
-
Click Synchronization > Sync Resources.
-
The extension finds all resources that do not yet have a MEX Resource ID assigned.
-
Each resource is sent to MEX --- on success, the MEX Resource ID is written back to the BC Resource record.
Viewing Resource Sync Status
-
Search for Resource List and open it.
-
Look for the MEX Sync Status and MEX Resource Id fields.
-
Resources with a MEX Resource Id have been successfully registered in MEX.
ℹ Info: Resources are only created in MEX the first time they are synced (when MEX Resource Id is blank). Subsequent changes to resource details are not automatically pushed --- contact your administrator if an update is needed.
Fixed Assets
Fixed Assets in Business Central can be registered in MEX and kept in sync. This ensures the maintenance team in MEX has an accurate, up-to-date asset register that reflects the financial asset records in BC.
Asset Lifecycle and Status
The extension tracks the following asset statuses between BC and MEX:
| BC Asset Status | MEX Asset Status | Triggered By |
|---|---|---|
| Commissioning | Commission | Manual sync from Fixed Asset record |
| Active | ACTIVE | Status change on Fixed Asset |
| Idle | Idle | Status change on Fixed Asset |
| Transfer | Transfer | Status change on Fixed Asset |
| Disposed | Dispose | FA Journal disposal posting in BC |
Mandatory Fields for Asset Registration
When the Check FA Mandatory Fields option is enabled in MEX Integration Setup, the following fields must be filled on the Fixed Asset before it can be sent to MEX:
-
Description
-
Global Dimension 1 Code (Department / Account Code)
-
FA Location Code
-
FA Subclass Code
-
For Owned assets: an FA Ledger Entry with Acquisition Cost must exist (to provide purchase date)
⚠ Note: If mandatory fields are missing, the asset will not be sent to MEX and the specific error will appear in the MEX Error Log. Open the error log from the Fixed Asset card using Actions > View MEX Log.
Registering a New Asset in MEX
-
Open the Fixed Asset card in Business Central.
-
Ensure all mandatory fields are completed (see Mandatory Fields for Asset Registration).
-
Set the Asset Status to Commissioning.
-
The extension automatically sends the asset to MEX when you save, or your administrator triggers a batch sync.
-
On success, the MEX Asset Id field is populated on the Fixed Asset record.
Disposing an Asset
When an asset is disposed of through a Fixed Asset Journal in BC, the extension automatically updates MEX:
-
Post a disposal entry in the FA Journal in BC as normal.
-
The extension detects the disposal posting and sends an update to MEX with status Dispose.
-
The asset is also marked as Inactive in MEX.
-
The BC Fixed Asset record is updated with MEX Sync Status = Success.
Reviewing Staging Assets
Assets received from MEX are first placed in a staging area before being imported into BC:
-
Search for MEX Staging Assets and open the list.
-
Review each staged asset record.
-
Assets can be reviewed on the MEX Staging Asset Card for full details.
ℹ Info: The staging area gives you a chance to review assets from MEX before they affect your BC data. Contact your administrator for the import process.
Work Orders
Work Orders in MEX describe maintenance tasks assigned to assets. This extension pulls work orders from MEX into Business Central so that labour costs, spare parts usage, and asset-related charges can be financially processed.
Viewing Work Orders in Business Central
-
Search for MEX Work Order List and open it.
-
The list shows all work orders pulled from MEX with their status, priority, asset number, and progress.
-
Click on a work order to open the MEX Work Order Card for full details.
Work Order Card --- Key Fields
| Field | Description |
|---|---|
| Work Order Number | The MEX work order reference number |
| Description | What the maintenance task involves |
| Asset Number | The asset being maintained (Tech ID) |
| Status | Current work order status from MEX |
| Priority | Urgency level set in MEX |
| Department | Account code / cost centre for this work |
| Job Type | Type of maintenance job |
| Due Start / Finish Date Time | Scheduled maintenance window |
| Progress Percentage | How much of the work is complete |
| Instructions | Specific instructions for the technician |
| Safety Notes | Safety requirements for this work order |
Work Order Spares
Each work order may have spare parts (materials) required. The Work Order Spares sub-list on the Work Order Card shows all spares linked to that work order from MEX, including the catalogue number and quantity.
Work Order Trades (Labour)
Each work order may also have trade allocations --- these represent labour hours charged by trade code (e.g. Electrician, Mechanic). The Work Order Trades sub-list shows all trade entries from MEX, including the trade code, hours, and rates.
Creating Journal Entries from Work Orders
Labour and asset costs from work orders can be posted to the BC general ledger and fixed asset ledger.
Creating General Journal Entries (Labour Costs)
-
Open the MEX Work Order Card.
-
Click Actions > Create Journal Entries.
-
General journal lines are created using the trade codes and hours from the Work Order Trades sub-list.
-
Review the journal lines in the configured General Journal batch, then post as normal.
Creating Fixed Asset Journal Entries
-
Open the MEX Work Order Card.
-
Click Actions > Create FA Journal Entries.
-
Fixed Asset journal lines are created to record maintenance costs against the relevant asset.
-
Review the lines in the configured FA Journal batch, then post as normal.
ℹ Info: The General Journal and FA Journal templates/batches used for work order entries are configured in MEX Integration Setup. Contact your administrator if journal entries are not being created correctly.
Pulling Work Orders from MEX
-
Search for MEX Work Order List and open it.
-
Click Actions > Get Work Orders.
-
The extension fetches the latest work orders from MEX and updates the list.
ℹ Info: Work orders are filtered to only show changes since the last sync date. The Work Order Modified DateTime in MEX Integration Setup tracks when the last pull occurred.
MEX Requisitions (Purchase Requests)
When maintenance staff in MEX raise a purchase requisition (a request to buy parts or materials), this extension automatically pulls those requisitions into Business Central. A BC Purchase Requisition is then created for the procurement team to process.
The Requisition Flow
| Step | System | What Happens |
|---|---|---|
| 1 | MEX | Maintenance staff raises a requisition for parts |
| 2 | MEX | Requisition is set to Pending Approval status in MEX |
| 3 | BC Extension | Extension detects pending requisitions and imports them |
| 4 | BC | MEX Requisition record is created in BC |
| 5 | BC | BC Purchase Requisition is automatically created |
| 6 | BC | If workflow is active, requisition is sent for approval |
| 7 | BC | Procurement processes the approved requisition as a Purchase Order |
| 8 | MEX | Once approved in BC, the requisition is marked approved in MEX |
Viewing MEX Requisitions
-
Search for MEX Requisitions and open the list.
-
The list shows all purchase requisitions received from MEX.
-
Click on a requisition to open the Requisition Document card.
Requisition Document --- Key Fields
| Field | Description |
|---|---|
| Requisition No. | The MEX requisition reference number |
| Work Order Id | The MEX work order this requisition is linked to |
| Description | What is being requested |
| Department | Account code / cost centre |
| Delivery Location | Where goods should be delivered |
| Supplier No. | Suggested supplier from MEX |
| Requisition Created By | The MEX user who raised the request |
| Required Date | When the items are needed |
| Approval Status | Current approval state in BC |
| Justification | Free-text reason for the request (from MEX comments) |
| Purchase Requisition No. | The BC Purchase Requisition linked to this MEX request |
Manually Creating a Purchase Requisition
If a BC Purchase Requisition was not automatically created (e.g. due to a validation error), you can create it manually:
-
Open the MEX Requisition Document card.
-
Review and correct any missing data (supplier, location, department).
-
Click Actions > Create Purchase Requisition.
-
A BC Purchase Requisition is created --- a confirmation message shows the new requisition number.
Pulling Requisitions from MEX
-
Search for MEX Requisitions and open the list.
-
Click Actions > Get Requisitions.
-
The extension pulls all Pending Approval requisitions from MEX and adds them to the list.
ℹ Info: Only requisitions with a Pending Approval status in MEX are imported. Requisitions that are already approved, declined, or have no approval record are skipped.
Good Receipts for Non-MEX Pos
This endpoint is for non-Mex purchase order receipts. The existing receipt endpoint is for receipting purchase order lines.
Get Custom Fields
A custom fields endpoint would entail 1 endpoint where query parameters can be used to identify an entity and then all custom field values are returned. This would work for getting any custom field values in MEX.
E.g.
Request
Method: GET
Url: /CustomFields?entityName=Requisition&entityId=123 Mandatory entityName and entityId Alternatively switch entityNumber for entityId
Response Body
[
{
"field": "{{ fieldName }}",
"value": "{{ fieldValue }}"
},
...
]Get Document
There isn’t an endpoint that supports getting a list of documents from a given entity, only to upload documents into MEX. This is another quotable item where the endpoint would look like this:
Request
Method: GET
Url: /Documents?entityName=Requisition&entityId=123 (and also a /Documents/GetAll url would be included so you can pull for the latest ones) Mandatory entityName and entityId Alternatively switch entityNumber for entityId
Response Body
[
{
"entityId": {{ entityId }}
"entityName": {{ entityName }},
"filePath": {{ filePath }}, (this contains the file name of an uploaded file, or a url of a website)
"comment": {{ comment }},
"sequenceNumber": {{ sequenceNumber }},
"url": {{ url }}, (url to access the document; this should be used by D365 to download/transfer to your ERP)
"createdByContactId": {{ createdByContactId }},
"createdDateTime": {{ createdDateTime }},
"modifiedByContactId": {{ modifiedByContactId }},
"modifiedDateTime": {{ modifiedDateTime }},
"formId": {{ formId }} (identifies if the document is a Mex form; if a form it does not exist as a document file and cannot be accessed via a url)
},
...
]
Vendor (Supplier) Synchronisation
Vendors in Business Central can be synchronised to MEX as suppliers. This ensures the MEX system has an up-to-date supplier list that matches your BC vendor master data.
Vendor Sync Status
Each vendor record in BC may show a Vendor Status field indicating their MEX sync state. A vendor is pushed to MEX when the sync is triggered and receives a MEX Supplier ID upon success.
Triggering a Vendor Sync
Vendor synchronisation is typically managed by your administrator from the MEX Integration Setup page. Contact your system administrator to run or schedule vendor syncs. If you notice a vendor is missing in MEX, raise this with your administrator and they can trigger a sync for that vendor.
ℹ Info: The Vendor Sync feature uses the Supplier Post and Supplier Update endpoints configured in MEX Integration Setup. Vendors are matched by their BC Vendor No. as the MEX supplier reference.
Error Log & Troubleshooting
The MEX Error Log is your first stop when something does not sync correctly. All integration errors are written here with the affected record and a description of what went wrong.
Opening the Error Log
-
Search for MEX Error Log and open it.
-
The list shows all current errors with the Record ID (what failed) and Error Message (why it failed).
-
You can also access the error log from individual records --- for example, from the Fixed Asset Card via Actions > View MEX Log.
Common Errors and How to Resolve Them
| Error Message | Cause | Resolution |
|---|---|---|
| UOM [X] not found. | The item’s Unit of Measure from MEX does not exist in BC | Create the Unit of Measure in BC (search for Units of Measure), then re-run the item sync |
| Vendor [X] not found. | The supplier from MEX does not match a BC Vendor No. | Create or update the vendor in BC, then re-run the item sync |
| Asset Description is mandatory… | Fixed Asset is missing its Description field | Open the Fixed Asset and enter a Description, then retry the sync |
| Asset Department Code is mandatory… | Global Dimension 1 Code is blank on the Fixed Asset | Set the department/cost centre on the Fixed Asset |
| Asset should have FA ledger entry… | Owned asset has no Acquisition Cost posted | Post the acquisition entry in the FA Journal first |
| [HTTP Status] - [Error Text] | MEX API returned an error (connection or data issue) | Check the API Key and Base URL in MEX Integration Setup; verify the MEX server is accessible |
Connection Issues
If all syncs are failing with HTTP errors:
-
Search for MEX Integration Setup and open it.
-
Verify the Base URL is correct (e.g. https://sample.mex.com.au:5002/ ).
-
Verify the API Key is current and has not expired.
-
Contact your MEX system administrator to confirm the API service is running.
Staging Work Orders and Assets
Work orders and assets from MEX are placed in staging tables before being processed. If you see records stuck in staging:
-
Search for MEX Staging Work Orders or MEX Staging Assets to review the records.
-
Check each record for error indicators.
-
Contact your BC administrator to process or correct staging records.
✔ Tip: Staging records are a safety buffer --- they give you a chance to review data from MEX before it affects your live BC records.
Email Notifications
This extension can send automated email notifications for key events. These are configured by your administrator and run in the background.
| Email Type | Triggered By | Recipients |
|---|---|---|
| Purchase Order Email | New Purchase Order created from a MEX requisition | Vendor / Supplier |
| Item Notification Email | New items created from MEX catalogue sync | Configured contact |
| Remittance Email | Payment processed for a MEX-related purchase | Vendor / Supplier |
ℹ Info: Email sending must be configured in BC (SMTP setup) and the relevant notification triggers enabled by your administrator. Contact your admin if you expect emails to be sent but they are not arriving.
Quick Reference
Sync Actions Summary
| What You Want to Do | Where to Go | Action to Click |
|---|---|---|
| Pull items from MEX catalogue | MEX Integration Setup | Sync > Sync Items |
| Push goods receipts to MEX | MEX Integration Setup | Sync > Sync Good Receipts |
| Push resources/employees to MEX | MEX Integration Setup | Sync > Sync Resources |
| Pull trade codes from MEX | MEX Integration Setup | Sync > Sync Trade Codes |
| Pull work orders from MEX | MEX Work Order List | Actions > Get Work Orders |
| Pull purchase requisitions from MEX | Mex Requisitions | Actions > Get Requisitions |
| Create a BC Purchase Requisition from MEX req. | Mex Requisition Document | Actions > Create Purchase Requisition |
| Create labour cost journals from a work order | MEX Work Order Card | Actions > Create Journal Entries |
| Create fixed asset journals from a work order | MEX Work Order Card | Actions > Create FA Journal Entries |
| View all integration errors | MEX Error Log (search) | — |
| View errors for a specific Fixed Asset | Fixed Asset Card | Actions > View MEX Log |
Key Pages Summary
| Search Term | Purpose |
|---|---|
| MEX Integration Setup | All configuration, API settings, and manual sync buttons |
| MEX Work Order List | View and manage MEX work orders in BC |
| Mex Requisitions | View and process MEX purchase requisitions |
| MEX Staging Assets | Review assets from MEX before import |
| MEX Staging Work Orders | Review work orders from MEX before import |
| Item Import Staging | Review catalogue items from MEX before creation |
| Catalogue Transaction | View MEX stock movement transactions |
| MEX Error Log | All sync errors with descriptions |
| Fixed Asset List | Fixed assets with MEX sync status and IDs |
| Resource List | Resources/employees with MEX sync status |
Glossary
| Term | Definition |
|---|---|
| MEX | Maintenance management software system used to manage assets, work orders, and maintenance schedules |
| Business Central (BC) | Microsoft Dynamics 365 Business Central — the ERP system this extension is installed in |
| Catalogue | MEX parts/materials list — equivalent to the Items master in BC |
| Catalogue Transaction | A stock movement in MEX (issue or return) linked to a work order |
| Goods Receipt | The confirmation in BC that purchased goods have been physically received |
| MEX Asset ID | The unique identifier assigned by MEX when an asset is registered there |
| MEX Resource ID | The unique identifier assigned by MEX when a resource/employee is registered |
| Staging | A temporary holding area in BC where MEX data is reviewed before being imported |
| Trade Code | A skill or trade type (e.g. Electrician, Welder) used to categorise labour in MEX |
| Work Order | A maintenance task in MEX assigned to an asset, with labour and parts requirements |
| Purchase Requisition | A formal request to purchase goods, raised in MEX and processed in BC |
| API Key | A secret token used to authenticate BC’s connection to the MEX API |
| Sync Status | A field on BC records showing whether the last MEX sync was successful or failed |
Support & Further Information
Getting Help
If you encounter issues not covered in this guide:
-
Check Section Error Log & Troubleshooting first.
-
Contact your internal Business Central administrator.
-
For extension-specific issues, contact d365.Global support .
| Publisher | d365.Global |
|---|---|
| Support Website | https://d365.global/help |
| Extension Version | 1.0.0.3 |
| BC Compatibility | Business Central 25.x and above (Cloud/SaaS) |
| Dependencies | Purchase Requisition for BC by d365.Global (v1.0.0.9+) |
Providing Feedback
If you find a bug or have a feature request, you can use the thumbs down button on any Claude response or contact d365.Global directly via their Support Portal .