Closed
Solved
Date filters in report defintion for use with Elastic Search
Hi All,
Seems I cannot provide a date filter in a report definition intended to be used with Elastic Search. As soon as I do it falls back to SQL with the error UnexpectedResolutionFailureAlert.
com.pega.pegarules.data.internal.rd.resolve.UserResolveReportException: Filter operation not supported
It doesn't matter is you use equals or less than or any relationship same error regardless.
Can someone explain why we can't filter on a date field? I'm simply trying to use pxCreateDateTime.
Thanks
Craig
Accepted Solution
Posted: 1 year ago
Updated: 1 year ago
Updated: 9 Jan 2025 11:14 EST
MOD
Pegasystems Inc.
GB
@CraigA52 The issue you are experiencing with the pxCreateDateTime filter in a report definition for Elastic Search may be related to the limitations of using date/time properties as filters. When using a date/time property as a filter it can lead to unexpected results or errors such as the one you mentioned. It is important to ensure that the properties for reporting are correctly exposed and that the report definition is properly configured to work with Elastic Search. If the report runs fine directly against the database but fails with Elastic Search it may indicate that the report rule is not runnable against the Elastic Search index directly. You might want to consider using alternative approaches or reviewing the configuration of your report definition.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Microsoft SQL Server issues with date/time
ElasticSearch report not working on embedded data class