Multi tenant cloud M3 APS235 IDM document/ image not visible in Related information with a Custom do

Hi All,

I have created a Custom document type with only a "Supplier Invoice number" as an attribute. Entity I am using the standard one "InforSupplierInvoice" in IDM Business context model.

I can view document/image uploaded on this custom document type in M3 programs APS110, APS210, APS230.

But I am not able to see the document/image from IDM in the M3 program APS235. Is it because in this program Supplier invoice number, supplier, payee and invoice year all are at header level and in all those above programs they are at line level. Is it due to that its causing the issue when I select the line in APS235?

But if I use standard entiry "InforSupplierInvoice" and std document type "M3_SupplierInvoice" and fill in the attributes in IDM the Supplier invoice number, supplier and invoice year which seems mandatory then I can view the image for the record in APS235 under related information widget.

Has anyone seen this kind of issue?

Thanks

Find more posts tagged with

Infor Document Management (IDM)

Comments

Maxime Richard

Hello,

Can you show us the JSON format of the context viewer widget when you select a line in APS235 ?

Legacy Contributor

Hi Maxime,

Thank you. Below is the json format of the context viewer. Currently image is visible for std entity and std document type of IDM. in APS235

{
  "type": "inforBusinessContext",
  "data": {
    "screenId": "m3_APS235_B1",
    "entities": [
      {
        "entityType": "InforSupplierInvoice",
        "accountingEntity": "780_AAA",
        "visible": true,
        "id3": "Y50001",
        "id2": "Y50001",
        "id1": "10040",
        "id6": "2011",
        "drillbackURL": "?LogicalId=lid://infor.m3.m3&program=APS235&tablename=FPLLOG&keys=ELCONO%2C780%2CELDIVI%2CAAA%2CELSPYN%2CY50001%2B%2B%2B%2B%2CELSUNO%2CY50001%2B%2B%2B%2B%2CELSINO%2C10040%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2CELINYR%2C2011%2CELACTO%2C10%2CELUSID%2C%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2CELACTD%2C20110906%2CELACTM%2C43629&option=5&panel=E&name=APS235%2FE"
      },
      {
        "entityType": "InforSupplierPartyMaster",
        "accountingEntity": "780_AAA",
        "visible": true,
        "id1": "Y50001",
        "drillbackURL": "?LogicalId=lid://infor.m3.m3&program=APS235&tablename=FPLLOG&keys=ELCONO%2C780%2CELDIVI%2CAAA%2CELSPYN%2CY50001%2B%2B%2B%2B%2CELSUNO%2CY50001%2B%2B%2B%2B%2CELSINO%2C10040%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2CELINYR%2C2011%2CELACTO%2C10%2CELUSID%2C%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2CELACTD%2C20110906%2CELACTM%2C43629&option=5&panel=E&name=APS235%2FE"
      },
      {
        "entityType": "InforVendor",
        "accountingEntity": "780_AAA",
        "visible": true,
        "id1": "Y50001",
        "drillbackURL": "?LogicalId=lid://infor.m3.m3&program=APS235&tablename=FPLLOG&keys=ELCONO%2C780%2CELDIVI%2CAAA%2CELSPYN%2CY50001%2B%2B%2B%2B%2CELSUNO%2CY50001%2B%2B%2B%2B%2CELSINO%2C10040%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2CELINYR%2C2011%2CELACTO%2C10%2CELUSID%2C%2B%2B%2B%2B%2B%2B%2B%2B%2B%2B%2CELACTD%2C20110906%2CELACTM%2C43629&option=5&panel=E&name=APS235%2FE"
      }
    ],
    "session": {
      "cono": "780",
      "divi": "AAA",
      "panel": "APA235BC",
      "iid": "fc3b320f8c85357fe219f7147bc3d350",
      "lng": "GB",
      "jobid": "79faf4c8cd7f4e83b10ddf435fe72f3a",
      "chgby": "",
      "url": "",
      "dsep": ",",
      "moddate": "",
      "user": "59b57d64-b",
      "userid": "59B57D64-B",
      "df": "YYMMDD",
      "regdate": ""
    },
    "program": "APS235",
    "panel": "B1",
    "screenIdBase": "APS235"
  }
}

Maxime Richard

Ok.

This is the standard business context model of APS235/B1:

I suppose that you have changed the document type with the custom one. Did you change also the XQuery ?

Legacy Contributor

Hi Maxime,

Yes Xquery also changed. But the json format i gave you was when I am using all std.

Below is my Business context model and custom document type created

Copyright © 2025 Infor. All rights reserved.