Skip to main content

Hi All

Even when non-numeric values are entered into a Number-type parameter for an add-on report, it can still be executed without resulting in an error.
(In APP9, an error would occur due to the standard functionality.)

For IFS Cloud, there is no error.

For APP9, there is an error.


Q1, In the Cloud version, is it expected behavior that entering non-numeric characters into a Number-type parameter during Order Report input does not trigger an error?

Q2, Is it possible to cause an error for incorrect data type input without adding custom validation in the add-on?


Thanks ＆Best regards,
Feng

It does give a red indicator, that the value is invalid but I agree that it might be a bug that you can continue with an invalid value - so worth trying to raise a case!

 

What QFLAGS have you set for that attribute/parameter? I suspect that you will want the QFLAGS to be either "-CS--" (if not mandatory) or "MCS--" (if mandatory). This should also have an impact on the behaviour.

See description of QFLAGS on this page in the documentation

https://docs.ifs.com/techdocs/24r1/060_development/025_operational_reporting/048_data_assembly/#the_report_definition_file

Hi @Jonas Feigl 

Thanks so much!

It’s “O-S--”, I can’t find the description of “O” or “S” from the document page, do I should set it to "MCS--" or "-CS--"?

 

Best regards,

Feng

@feng Yes, O-S--- is correct. 

Now it seems the client is validating this but the only indicator you are given is the red underline of the field if the value you have entered is invalid (as can be seen in your screenshot). If the user then clicks Next/Finish with such an invalid value, the user input is simply ignored and not passed to the report. 

It might be worth raising a case for this as this might be a bug!

Actually you might want to use “M-S---” to make the parameter mandatory :)

Hi @Jonas Feigl 

Thank you very much!

Best regards

Feng

Reply


Terms & ConditionsCookie settings