Drillback from a dashboard to an application in Infor Ming.le

You can use an action to drill back from an Application Studio report to another application that is running in Infor Ming.le. For example, a drillback could display details of a specific sales order in ERP LN, when a user clicks that Sales Order ID in an Application Studio report.

For drillbacks from Application Studio to Infor Ming.le, the Drillback in Infor Ming.le action has these required parameters:

  • Logical ID: The ID of the core application within Infor Ming.le.
  • View ID: Specifies the ID of the screen that is opened in Infor Ming.le.
  • Accounting Entity.
  • IDs.

    Some View ID parameters have further IDs, which are optional. You can use them to add further context to a drillback. For example, the ChartOfAccountView view requires ID 1 (Accounting Chart ID), but ID 2 (NaturalAccount) is optional.

Drillbacks from Infor Ming.le to dashboards require only the Logical ID and ID 1.

This example uses the ERP LN Sales Order view. In addition to its required ID 1 (SalesOrder) the Sales Order view has an ID 2 (SalesOrderLineNumber) which is optional and can be used to add context to the drillback.

  1. Right-click a cell and select Define Action.
  2. Select Drillback in Infor Ming.le as the action type. Specify TRUE as the Condition and select a mode for the action.
  3. Specify the Logical ID of the system on which you are reporting. For example, ERP LN.
    The Logical ID must begin =lid://. For example: ="lid://erpln.mycompany.1"
  4. Specify the view ID of the view to drillback to.
    For example: ="SalesOrderView"
  5. Specify the Accounting Entity.
    For example: ="011"
  6. Specify the Location.
    For example: ="MyCity"
  7. Specify the value of the ID 1 of the chosen View ID.
    The ID 1 of SalesOrderView is SalesOrder. For example: ="SO-1001"
  8. Optionally, specify the value of further IDs of the chosen View ID.
    SalesOrderView has one optional ID. That is ID 2 - SalesOrderLineNumber. For example: ="SOL-001" .
  9. Optionally, create a second action type, such as a jump, to provide alternative report navigation if Application Studio is not running in Infor Ming.le.