Entering a non-numeric value into a Number-type parameter for an Operational Report doesn't raise an error and lets the report execute anyway, unlike the equivalent parameter validation in the older on-premise product.

All FAQ questions / Reporting and analytics

Answer

The client actually does perform this validation visually (an invalid value gets a red underline), but if the user proceeds anyway and clicks Next/Finish, the invalid input is simply dropped/ignored rather than blocking the report or surfacing a clear validation error — the report then runs without that parameter value rather than throwing an error the way the older product did. This inconsistency between the visual validation cue and the actual submit behavior looks like a genuine bug rather than an intentional behavior change, so raising a support case referencing this exact symptom is reasonable if it matters for your reports.

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