Open raniangamuthu opened 2 weeks ago
@selvakumarchandran @ashoksri0 Provide Fix deliverable update of this issue
as discussed with Praveen Kumar, this issue occurs when we try to apply retention with a specific case, where the query involves more than one table. Instead of using CONCAT(x.ADS_ID, ',', y.ADS_ID) as ADS_ID, the query had x.ADS_ID as ADS_ID.
However, this is working with the latest build. @Udhayanila8 (Srividhya), could you please confirm whether it is functioning correctly in the latest build (2024.10.45564_RC6) that was provided to you?
http://192.168.56.146:4081/ Version: 2024.10.45564_RC6 As discussed with Shalini and tried the below mentioned 4 different cases: Case 1: With concat query, In search result selected some records and applied retention Case 2: With concat query, In job management selected particular search and applied retention Case 3: Without concat query, In search result selected some records and applied retention Case 4: Without concat query, In job management selected particular search and applied retention
This issue is not replicating in 146 server, It is working as expected.
Screenshots: With concat query With concat query through job management Without concat query through search Without concat query through job management
And also tried rani mentioned scenario. Screenshots:
Applying duration type retention through search.
To Reproduce Steps to reproduce the behavior:
e91d8a60-b380-4f44-9504-4b42c1c16a00.log