Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Intelligence (Analytics)
SEVERE: Cannot set the string value (HAS_SUBSTRING) to parameter 1
santosh_br
BIRT GURU's,
Need an help. I'm new to BIRT designer. We're trying to port all our existing Crystal Reports to BIRT. We learnt that there is no way of auto converstion of the Crystal Reports to BIRT. So, we Started doing all from scratch.
Right now, BIRT 2.5.1 is used as this is in compatablity list of ClearQuest 8.0. Part of the designing script always I'm finding difficult in setting Parameter. It works on one instance and fails in another not sure what's wrong going here.
The Dataset is set with 2 Parameter (id_Operator) and (id_Parameter).
Always when the Bug ID has been given as argument to the above parameter a erro thrown as shown below.
SEVERE: Cannot set the string value (HAS_SUBSTRING) to parameter 1
Attached are the design file and the Error file.
Thx,
Santosh
Find more posts tagged with
Comments
Hans_vd
Hi Santosh
I couldn't open the report in my version but I did a search in your XML source and I found the string "HAS_SUBSTRING" as a default parameter value.
So you are trying to set the value "HAS_SUBSTRING" to an integer type parameter, which is not possible.
Hope this helps
Hans
santosh_br
<blockquote class='ipsBlockquote' data-author="'Hans_vd'" data-cid="109112" data-time="1346922755" data-date="06 September 2012 - 02:12 AM"><p>
Hi Santosh<br />
<br />
I couldn't open the report in my version but I did a search in your XML source and I found the string "HAS_SUBSTRING" as a default parameter value.<br />
So you are trying to set the value "HAS_SUBSTRING" to an integer type parameter, which is not possible.<br />
<br />
Hope this helps<br />
Hans<br /></p></blockquote>
<br />
Thanks Hans for the hint given. After tracing back the issue it was found that the ClearQuest query was not running with proper argument. After setting up the Filter in CQ backend queries all started working as expected. <br />
<br />
Thanks for your help.<br />
Santosh