I try to make it possible to filter the results of a query using decimals, but it seems to accept only integers.
I tried using: @WHERE:PARAM:USER_DEF:float:cb_index@ but it doesn't seem to help.
Is it possible?
I think that float data_type is not possible to use as NSQL parameters, and integer and string are valid data_type for parameters.
I checked "User-Defined NSQL Constructs" section in CA PPM Studio Development manual and it says below.
All parts of the SELECT clause must use special NSQL syntax and be specified with an NSQL @SELECT@ construct.
The following data types are supported in NSQL. They are valid only as part of the Dimension, Properties, and Metrics columns, and cannot be used as parameters.
I have searched document which describes about valid data_type for NSQL parameters, but I have not got it yet.
Is there any reason why the NSQL has to have NSQL parameter, in your case, prpctcomplete?
Why can't you just push over the attribute required to be filtered into the Portlet Filter. For example, using prpctcomplete on prtask in a custom query, I was able to filter on 0.2 which returned tasks which are at '20%'. The only issue I experienced was that the filter automatically changed the display to be 0 in the filter, but it returned the required tasks which were at 20%.
In accordance with the above provided points, you may refer to the following thread -> NSQL: how to declare variables?
Some discussion has been carried out in similar topics
Retrieving data ...