Invalid Prefix added on applying filter
Answered
On applying filter in yellowfin report, it adds prefix 'E' to the filter which makes the query invalid. Any idea what might be causing this to happen.
Example after applying filter on "Test Account", the query becomes:
Export SQLSELECT DISTINCT
"tbl_1"."ar_product_type",
"tbl_1"."ar_customer",
"tbl_1"."ar_date",
"tbl_1"."ar_product_type",
AVG("tbl_1"."ar_rating")
FROM "dev_db"."tbl_1"
WHERE (
"tbl_1"."ar_customer" IN (E'Test Account')
)
GROUP BY
"tbl_1"."ar_customer",
"tbl_1"."ar_product_type",
"tbl_1"."ar_date"
The same question
Hello,
Can you please tell us what version of yellowfin you are using (and build number)?
Can you also tell us if this is freehand SQL or it has been generated by the drag and drop system?
Best regards,
Pete
Hello,
Can you please tell us what version of yellowfin you are using (and build number)?
Can you also tell us if this is freehand SQL or it has been generated by the drag and drop system?
Best regards,
Pete
Current Schema Version:20130704Original Code Version:20150325Current Code Version:20160701Import Version:4.39Application Version:7.1
Current Schema Version:20130704Original Code Version:20150325Current Code Version:20160701Import Version:4.39Application Version:7.1
Its generated by a drag and drop system. Initially report shows fine. But on applying filter, it appends 'E' in the query and makes the query invalid
Its generated by a drag and drop system. Initially report shows fine. But on applying filter, it appends 'E' in the query and makes the query invalid
Any help appreciated
Any help appreciated
Attached is a screenshot of the bug...as u can see...the filter comes as E'filter_value'
Attached is a screenshot of the bug...as u can see...the filter comes as E'filter_value'
Hello,
I would suggest that you update yellowfin to the latest version in 7.1 (or more preferable move to 7.3 via 7.2)
This is likely a bug in this release.
Best regards,
Pete
Hello,
I would suggest that you update yellowfin to the latest version in 7.1 (or more preferable move to 7.3 via 7.2)
This is likely a bug in this release.
Best regards,
Pete
Replies have been locked on this page!