Operational Report parameters can show a dropdown of values when linked to an existing API's Enumerate() method (like Pur_Order_Print_Option_API.Enumerate()), but there's no such method available for a needed field (like Org Code) — is there a way to build a custom, hardcoded dropdown list for a report parameter without writing a whole custom API package to mimic an Enumerate() method?

All FAQ questions / Reporting and analytics

Answer

Add an Enumeration Model directly in Developer Studio instead — an .enumeration file defines a named fixed list with a simple syntax (an enumerationname, a component, and a values block listing each allowed value), which you deploy like any other model file. Then, in the .report file itself, reference that enumeration as the parameter's type (for example, parameter ReportSection Enumeration<YourEnumName> with a default value), and generate/deploy the resulting .rdf as usual. This gives you a genuinely hardcoded, dropdown-driven report parameter without needing to build a custom API method that mimics an existing Enumerate() pattern.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Reporting and analytics questions