How to Attach and View Documents in M3 with IDM
How do I attach and view documents in M3 with Infor Document Management (IDM)
Also searched as
- M3 IDM integration how to
- attach document to M3 order or item
- M3 H5 paperclip icon documents not showing
- IDM document class mapping M3
Short answer
Infor Document Management (IDM) attaches to M3 through key-based document classes: each document is filed against a document class that maps to a specific M3 program and key fields (order number, item number, customer number), so the paperclip or document icon on that M3 panel shows only documents whose stored key values match the record you are viewing.
Applies to: Infor M3 Business Engine 10.x-14.x with IDM integration, M3 H5 Client
Set up and use IDM document attachment in M3
- 1Confirm IDM is connected at the environment level - the M3 H5 client needs the IDM environment/connection configured before any document icon will function on user panels.
- 2Identify or create the document class for the record type you want to attach documents to (for example customer order, item, supplier), which defines what key fields IDM expects for that class.
- 3In the M3 H5 client, open the relevant record (for example an order in OIS100 or an item in MMS001) and use the document icon on the panel to open the IDM attachment view for that record.
- 4Upload or link the document through the IDM panel - IDM automatically stamps the document with the key values (order number, item number, etc.) from the M3 record you opened it from.
- 5To verify the attachment worked, close and reopen the record and confirm the document icon shows the attachment count or opens the correct document list.
- 6For documents that should be visible from multiple related records (for example a certificate of conformance tied to both an item and a specific order line), check whether the document class supports multiple key mappings or requires separate attachments.
- 7If documents are not appearing, check that the key values on the document exactly match the M3 record's key (including company number and any leading zero or format differences) rather than assuming the document class configuration is wrong.
How the key mapping actually works
IDM does not embed documents inside M3 records - it stores them in the IDM repository and links them by matching index/key values to the M3 record's own key fields. A document class configured for customer orders, for example, expects index values such as company, order number and possibly order line to be stamped on the document; the M3 H5 panel then queries IDM for any document whose index matches the record currently open. This is why a document uploaded with the wrong company or order number simply does not appear anywhere useful, even though the upload itself succeeded without error.
Because the mapping is key-based rather than a direct foreign key in the M3 database, troubleshooting a missing attachment is almost always a matter of comparing the exact key values stored on the IDM document against the M3 record's key, field by field, rather than assuming the integration itself is broken.
Common reasons attachments do not show
The most frequent cause is a company number mismatch in multi-company M3 environments - a document indexed under the wrong CONO will never appear on the intended record. The second is a document class that was configured for the wrong M3 program's key structure (for example built for order header keys but the user is trying to attach at the order line level), which silently returns no results rather than an error. The third is a permissions issue in IDM itself, where the user's IDM security role does not grant read access to the document class or folder, which looks identical to a missing document from the M3 side.
Where IDM fits versus M3 native attachments
M3 has some native text and note capabilities separate from IDM (item text, order text records), which are stored directly in M3 tables and are not the same as IDM document attachments. Companies that need version control, retention policies, OCR/search across scanned documents, or a document that needs to be visible from several different M3 record types typically use IDM rather than native M3 text, since IDM is purpose-built for document lifecycle management while M3 text fields are simple free-text storage.
Try it here, free
Infor M3 H5 Script Review Checklist
A review checklist for H5 Client scripts covering design, coding, security, testing and upgrade risk.
Common pitfalls
- !Uploading a document from the wrong company (CONO) context in a multi-company environment, so it never appears on the intended record.
- !Assuming a missing attachment means the integration is broken, when it is almost always a key/index mismatch between the document and the M3 record.
- !Configuring a document class for the wrong key level (header versus line), causing uploads to silently not appear where users expect them.
- !Not checking IDM-side security roles separately from M3 roles - a user can have full M3 access and still be denied document visibility in IDM.
- !Relying on IDM for simple internal notes when M3's native text fields would be simpler and do not require an external document class mapping.
How an ERP-grounded AI assistant handles this
A grounded assistant that understands both the M3 record structure and the IDM document class key mapping for a specific company can diagnose a missing-attachment complaint in seconds - checking whether the document exists with a mismatched key, a wrong company number, or a permissions gap - instead of a support ticket bouncing between the M3 admin and the IDM admin to find where the link broke.
Frequently asked questions
Why does a document uploaded through IDM not show on the M3 order I opened it from?
The most common cause is a key mismatch - the document's stored index values (company, order number) do not exactly match the M3 record's keys, often because it was uploaded from a different company context or the wrong document class was used.
Is IDM the same as M3's native order or item text fields?
No, M3 native text is simple free-text stored directly in M3 tables, while IDM is a separate document repository linked by key mapping, used for actual files (PDFs, scans, certificates) that need version control, retention and cross-record visibility.
Can one document be linked to more than one M3 record?
It depends on the document class configuration - some classes support multiple key mappings so a single document (like a certificate of conformance) can show against both an item and a related order line, but this must be set up explicitly rather than assumed.
Who controls whether a user can see a document in IDM from M3?
IDM has its own security roles separate from M3 authorization, so a user can have full M3 access to a record and still be denied visibility of its attached documents if their IDM role does not grant access to that document class or folder.
Related
How to Add a Personalization Script to an M3 H5 Panel
M3 H5 lets an administrator attach a JavaScript personalization script to a specific panel of a specific program, using the MForms client API to read fields, react to panel and field events, and adjust the UI (hide fields, set defaults, validate input) without modifying the underlying M3 program. Scripts are written and attached through Personalization mode in H5, saved against the panel/program combination, and deployed to the users or roles who should see the behavior.
How-toHow to Create a New Item in M3 (MMS001)
A new item in M3 is created in two stages: item basic data in MMS001 (Item. Open), which defines company-wide attributes such as description, item group and unit of measure, then facility-level data in MMS002 (Item/Facility. Connect), which attaches the item to a specific warehouse or plant with purchasing, planning and costing parameters. An item is not usable for orders, purchasing or MRP until both stages are complete.
How-toHow to Enter a Customer Order in M3 (OIS100)
OIS100 (Customer Order. Open) is the primary M3 program for entering and maintaining customer orders, built as a header-then-line workflow: you first create the order header with customer, order type and delivery terms, then add order lines that each carry their own item, quantity, price and delivery date defaulted from customer and item agreements.
Error fixFix a Ming.le homepage widget that will not load
A blank or endlessly spinning Ming.le widget is usually a permissions, session, or backend availability problem, not a broken widget itself. Confirm the issue is widget-specific, check the user's Security Group access to the underlying app, and look at the widget's network calls in browser dev tools to see whether it is failing with 401/403 or simply timing out against a down service.
Error fixM3 API Error: Record already exist
Record already exist means the MI Add transaction you called is trying to insert a key that is already present in the target M3 table, most often because a prior call succeeded and was retried, or because the key fields you built do not match what you think they match. Read the errorField and errorFieldGroup attributes on the response to see exactly which key field M3 flagged, then either switch to the matching Chg (change) transaction or fix the key construction in the caller.
AdvancedPaging M3 API MI List Transactions Past the Default Record Limit
M3 List transactions (the read/browse transaction most MI programs expose, such as CRS610MI.LstByNumber or OIS100MI.LstOrderHead) cap the rows returned per call using the MaxReturnedRecords input field, and by default many clients leave it low or unset, which looks like the API silently truncating results. Set MaxReturnedRecords explicitly, then loop the call using the last key values from the previous page as the starting position until fewer rows than the limit come back.
AI for ERPInfor M3 AI: A Practical Path from MI Programs to a Private Assistant
Infor M3 AI explained: grounded natural-language answers over MI programs and MEC, agents for distribution and manufacturing, on-prem or EU private cloud.
AI for ERPAI Agents Over Infor ION API, BODs, and the Infor Data Lake
Build AI agents on Infor ION API Gateway, BODs, and Data Lake, alongside or instead of Infor's own GenAI features, with your choice of model and hosting.
Stuck on Infor M3 (M3 Business Engine)?
Talk to engineers who work inside Infor M3 (M3 Business Engine) every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- Infor M3 H5 Script Review ChecklistA review checklist for H5 Client scripts covering design, coding, security, testing and upgrade risk.
- Infor M3 H5 Script TypeScript Template GeneratorGenerate a starting H5 script class that reads a field on an M3 panel, calls an MI transaction and shows the answer on the panel, on load or before Enter.
- Infor M3 MEC Mapping Design TemplateA fill-in design document for an M3 Enterprise Collaborator mapping, from partner and flow to field rules and error handling.
ERP fixes and how-tos
- Infor M3 Business Engine upgrade checklist: customizations and integrationsPractical checklist for an Infor M3 Business Engine upgrade: inventory customizations, integrations, H5 personalizations, reports and a regression test plan.
- How to Change Division in Infor M3Change company and division in Infor M3: switch at runtime in H5, set the default in MNS150, and fix the authority problems that block a division change.
- How to Search and Upload Documents with the Infor IDM REST APIUse the IDM REST API through ION API to search by entity attributes, fetch a document resource and upload a new item with attributes. Request examples included.
Runs with your ERP
- TrueCommerce EDI and Infor M3TrueCommerce managed EDI for Infor M3 (also VISUAL and other Infor ERPs): documents, data flows, setup steps, pitfalls, alternatives and where AI helps.
- Infor M3 Scheduling Workbench and M3: finite scheduling explainedHow Infor M3 Scheduling Workbench schedules against capacity and materials and writes orders back to M3 via PSMI, with setup, pitfalls and AI help.
- Infor EDI Managed Service and Infor M3 over IONHow Infor's EDI managed service connects to Infor M3 through ION with pre-built trading partner links: data flows, setup steps, pitfalls and a private AI layer.
Guides
- Infor Document Management: Setup and ConfigurationConfigure Infor Document Management (IDM) for CloudSuite. Document types, workflows, retention policies, and integration with ERP transactions.
- Infor M3 H5 Client Personalization and Scripting GuideWhat the Infor M3 H5 client is and how to tailor it: personalization layers, JavaScript scripts, bookmarks and deployment, without touching the Business Engine.
- Infor M3 Technical Architecture Explained Layer by LayerInfor M3 technical architecture explained: M3 Business Engine, Infor Grid, database tables, H5 client, and integration layers for on-prem and CloudSuite teams.
AI on your ERP
- Infor M3 AI: A Practical Path from MI Programs to a Private AssistantInfor M3 AI explained: grounded natural-language answers over MI programs and MEC, agents for distribution and manufacturing, on-prem or EU private cloud.
- Infor M3 Customer Order Management With AI for Status, Allocation and Promise DatesAI for Infor M3 customer order management: answer order status, allocation and delivery date questions from OOHEAD and OOLINE data without exposing it publicly.
Integrations
- How to add document OCR to Infor M3Capture invoices, packing slips and certificates into Infor M3 with OCR and AI: IDM, ION, Invoice Matching APIs, confidence thresholds and on-prem processing.
- How to use ChatGPT with Infor M3How to use ChatGPT with Infor M3: exports, custom GPT actions over the M3 API or ION, enterprise data controls, and when a private model is the safer choice.