I am building a custom report that takes in a parameter 'p3' with a data type Money. There are another 2 parameters, 'p4' and 'p5' after this one, and I want to disable those parameters when 'p3' is equal to 0. I tried using the expression <<p3>> = 0 in the disable clause. However, when I initiate the report in Tessitura, I get the message "Expression types must match". So I'm guessing it's because it sees <<p3>> as money and 0 as an integer.
I changed the p3 data type over to number and it successfully disabled the parameters with that expression. However, I choose money for a reason so that they could enter in decimals if needed and number data type does not allow that. I changed <<p3>> to a string and tried IsNull(<<p3>>) , <<p3>> = '' and <<p3>> = "". It returned no error message but failed to disable the parameters.
I attempted to use the CONVERT or CAST functions to convert the 0 to a float, decimal, or money, but I'm unsure what data type infomaker would recognize in this scenario. However, regardless of the datatype, I always get a message that I'm missing either an opening or closing parentheses for the function.
Any thoughts on how to use a money parameter to disable other parameters?
Did you try 0.0? That sometimes works for me, albeit in different contexts.
Yeah, just tried that one. Still got the "Expression types must match message". Thanks for the idea though, hadn't tried that yet.
some thing like
select CAST(<<P3>> AS numeric(10,2)) ?
Jesse, did this work? I looked at all the disable_clause values in gooesoft_report_parameter, but didn't see anything that looked relevant as an example of checking a currency (data_type = 50) value.
Unfortunately no. With the 'select' it runs with an Invalid expression warning. Without the 'select' I still get the "')' expected to close expression after function" message.
Earlier I had discovered the DEC function to cast the 0 as a decimal. The report initiated with no error messages, but it was not successful in actually disabling the parameters. I had hoped to avoid this option, but I simply broke down and added another parameter of a Yes/No question using the TR_GOOESOFT_DROPDOWN table to disable the fields when I need them to be.