Yes you are assuming right, I use a report definition rule. As far as I know there ist no html Control for this field in the report, but the report definition is used in a datapage as a source and this datapage (D_MyValueList) is used on the UI as the source for an autocomplete control. When I run the report on it's own, it already doesn't show up the zeros. I don't know where I can find the generated query by the report. The control for the property type is pxTextInput.
When you run the report manually, you can see the generated query in the clipboard - pyReportContentPage. You can also see the results in pxResults page list property under pyReportContentPage (this page will be under STANDARD thread).
Hello Rajiv, this is the statement SELECT "PC0".plzid AS "PLZID" , "PC0".ort AS "Ort" , "PC0".plz AS "PLZ" , "PC0".pzinskey AS "pzInsKey" FROM pegadata.pr_MSG_Data_PLZ "PC0" WHERE "PC0".pxObjClass = ? ORDER BY 1 ASC
where "PC0".plz AS "PLZ" is the wrong shown value. and it is already too short on the pxResult page. So what could I do to show it right?
Hello, thanks for your help. The property was on the db table marked as integer, although it was set to text (single line) on the page type screen. Strange situation. We set a new property explicitly text again, and imported the values on the new property column. now it works just fine.