10-09-2019 01:08 AM - edited 10-09-2019 01:48 AM
Hi,
We are upgrading a customer from 2015, to 2018. Found problems with some of the reports in v 2018, which works fine in 2015.
In v2018, The error (pls see attachment) comes up whenever a telrik textbox refers to a Filter field in the form.
for eg: =Fields.FILTER_BETWEEN_L_REQ_DATE
We use this in the report header to show the user specified query. For eg: generate a transaction report for requests between date1 and date2.
Whats' the issue. ?
<FormReport name="DPS_REPORTING_LP_TRANSREP" label="Transaction Report" format="PDF,XLS" type="overview"/>
<FormTab name="Report_Tab" label="General">
<FormGroup name="DetailGroup" label="Details">
<FormField name="ID" type="textfield" datatype="guidstring" visible="hidden"></FormField>
<FormField name="CPR_NO" label="Request Number:" type="textfield" datatype="string" required="false" maxlength="40" visible="list"/>
<FormField name="REQ_DATE" label="Requested Date:" type="datepicker" datatype="date" required="false" maxlength="15" visible="list,filter" filter="ISBETWEEN" />
...
Thanks.
10-16-2019 04:40 AM
Hi mshameem,
Where is your definition for 'textbox24' or 'textbox25' in the report?
Maybe I am missing something here but I dont see where Fields.FILTER_BETWEEN_L_REQ_DATE is defined.
The report/workflow wasn't altered from 2015 to 2018 versions?
10-16-2019 07:10 AM
Hi sclow,
<FormField name="REQ_DATE" label="Requested Date:" type="datepicker" datatype="date" required="false" maxlength="15" visible="list,filter" filter="ISBETWEEN" />
..
It has visible "list,filter" so, it appears as one of the filter fields of the List view
The telrik report, can refer to the value in a filter field by = Fields.FILTER_{FilterFieldId}
Documentation reference > https://hexagongeospatial.fluidtopics.net/reader/rMZAmliqhWp7LKakCy9Pig/uisw96ejixCZSYcyf1h6SA
FieldId is REQ_DATE, Since it's a 'isbetween' filter, it would display 2 fields, and the lower side of the 'between' is referred to as =Fields.FILTER_BETWEEN_L_REQ_DATE , which works perfectly fine in v2015. But not, on 2018.