# How to Attach and View Documents in M3 with IDM > Source: https://netray.co/erp-help/m3-idm-document-management-how-to > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## 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. ## Kind how-to ## System infor-m3 ## Erp Infor M3 (M3 Business Engine) ## Module Infor Document Management (IDM) ## Query How do I attach and view documents in M3 with Infor Document Management (IDM) ## Alternate Queries - M3 IDM integration how to - attach document to M3 order or item - M3 H5 paperclip icon documents not showing - IDM document class mapping M3 ## Applies To Infor M3 Business Engine 10.x-14.x with IDM integration, M3 H5 Client ## Steps ### Set up and use IDM document attachment in M3 **Items:** Confirm 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. Identify 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. In 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. Upload 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. To verify the attachment worked, close and reopen the record and confirm the document icon shows the attachment count or opens the correct document list. For 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. If 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. ## Sections ### How the key mapping actually works **Body:** 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 **Body:** 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 **Body:** 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. ## 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. ## Ai Angle 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. ## Faq ### Why does a document uploaded through IDM not show on the M3 order I opened it from? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms M3 IDM integration, Infor Document Management M3, M3 attach document order, M3 H5 document icon not showing, IDM document class key mapping, M3 IDM environment setup, IDM CONO company mismatch --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json