Removal candidates are getting created with empty fields?

[kiran kumar m1]

I have created a reclamation rule for Microsoft with a threshold of two months , I have created two usage records with  more than two months of last used date , and when I ran the reclamation schedule job , its creating removal candidates but all the fields are empty.

[priyatam_pvp]

Verify Reclamation Schedule Job Execution

Run it manually and check the system logs (syslog) for errors. If the job runs but doesn’t populate fields, the rule might not be processing the data correctly

Check Field Mapping in the Reclamation Rule

Ensure that the fields like User, Device, Last Used Date, and Software Model are properly mapped in the rule. If any of these fields are missing, the system may create empty records.

Look for any Business Rules or Workflow that might be overriding field values in the samp_sw_removal_candidate table.

Mark it helpful if this helps you to understand. Accept the solution if this gives you the answer you're looking for
Kind Regards,
Priyatam Patchipulusu

[shivani42]

Hi Kiran,

did you get solution for the issue. We are facing the same issue, where the job  SAM- identifying new reclamation candidate creating record for low usage with empty product and publisher fields.

Regrads,

Shivani

[kiran kumar m1]

Hi @shivanit you have to create one reclamation rule per product , and make sure that for one product either you create last used type or total usage type , if you create both it will over ride one another and create empty records

[dreinhardt]

Hi @kiran kumar m1, @shivani42,

seems to be a SAMP issue and you should raise a support case, please keep us posted about the solutions.

I've found this KB about RC creation process and the filter criteria is very strict, so I think it's a bug that the support team has to solve.

How software removal candidates are created for a reclamation rule - Support and Troubleshooting

Best, Dennis