Using unexposed properties without enabling CLR in SQL Server
How we can use unexposed columns in Report Definitions without enabling the CLR with SQL Server. Any ideas?
Hi Srujan,
You will not be able to use unexposed columns in a report definition without enabling CLR. CLR is necessary for UDFs to function, which will read the data stored in the blob. If you cannot enable CLR, any property that is needed for the report definition query will need to be exposed as you will not be able to get the property from the blob.
Pegasystems
IN
The alternative for reading BLOB content is using the obj-open method or obj-browse method.
https://community.pega.com/sites/default/files/help_v719/procomhelpmain.htm
Cognizant
US
Please can you provide more information regarding this. I am getting this issue when I use OOB Duplicate search cases subflow. How to handle it?
Pegasystems
IN
Please elaborate what the error is.
Pegasystems Inc.
IN
>>> OOB Duplicate search cases subflow...
- is the case match rule defined with all exposed properties of work table?
- the properties defined in case match rule will be consider for weighing the duplicate score evaluation
-
these properties will be referenced in a OOTB extensible Report definition template to retrieve result set.
- rule name can be learnt from tracer...
- rule name can be learnt from tracer...
-
so as Nick & Rajiv said...
- we will not be able to use unexposed columns in a report definition without enabling CLR.
- CLR is necessary for UDFs to function, which will read the data stored in blob
- UDFs are used in report definitions.
-
other way to read data from blob without UDF's is by referring to Obj- methods.
- but the OOTB duplicate case match flow wrapped in a smart shape needs to be re-written.
Please share your thoughts/observations/comments, Thank you!
psahukaru