Fetch value of property from database | Varchar()

General
, , , , ,
1

Hello,

We are fetching some results using a Report Definition. In this Report Definition, we have a Text property and its values are getting saved into DB Table as a String with total 36 characters. For example - “6a921dcc-ebe2-4b2c-be55-23c74f4eec29”.

Problem : This report definition is able to fetch some other values of this property successfully; for example - “abc”, “123”, “321” and so on… but it is not able to fetch the text value “6a921dcc-ebe2-4b2c-be55-23c74f4eec29”.

What we tried : We checked the values of this property and tried searching from Report Definition Tab in Dev Studio and we found that there is a plus symbol just after this text value and it is fetching values like this - 6a921dcc-ebe2-4b2c-be55-23c74f4eec29+. We have tried changing the max length to 36 characters by optimizing the property. But this is still not fetching the any record.

Solution Required : Is there any way we an change the size of this property so that it will fetch the expected result? How we can make this possible?

2

@PritamJ5 Could you check below possible scenarios which might be the reason behind the issue.

Check if you have defined the property as text.

Check if there is any control defined in Column format in report definition.

Check if you have any max length configured in the property definition in advanced tab.

Check at the DB side if you have defined the column with any max length.

3

@SanthoshRanga We have checked this. But still it is not fetching any record. Any other alternative? We don’t have DB access.

4

@PritamJ5 Couldn’t get you when you mean not fetching any record ?

Are there any filters in report definition ?

5

@SanthoshRanga Thank you for your concern. This has been sorted. It was not displaying any record because of the Varchar length issue. We were trying to save a string with 36 characters against that property however the its Max Length was less than 36. I optimized this property and later ran Connect SQL to update the max length in DB. It worked. Thank you once again!