Hi everyone,
I am facing an architectural conflict with Info Windows and Report Parameters in iDempiere 8 and would love to hear your advice on best practices.
My Scenario:
I have a custom Report with a parameter pointing to M_Requisition_ID (Reference type: Search).
I need this report parameter to be able to search for all requisitions, including those with a Completed (CO) status.
The Problem:
When I click the search icon on the parameter, Completed records do not show up.
I found out that the M_Requisition table (AD_Table) has a custom Info Window assigned to it globally.
This custom Info Window has a strict WhereClause (docstatus not like 'CO') because it was designed for a different, specific operational process.
The Constraint:
Because AD_Process_Para does not have an AD_InfoWindow_ID column, my report parameter is forced to inherit the restrictive Info Window from the Table level. I cannot choose a different Info Window directly from the parameter setup.
My Question: What is the best practice to resolve this without breaking the other process that relies on the filtered Info Window?
Is there a hidden trick to assign a specific Info Window just for one Report Parameter?
Should I remove the custom Info Window from the Table level and handle the not like 'CO' filter for the other process using Dynamic Validation Rules instead?
Should I create a custom Database View (e.g., RV_Requisition_Budget) just to attach a different Info Window for this report?