Jobs created under Automation Central which contain property-based filters ( Custom Tag ) are not working in Aria Operations

I’ve been hearing some issues from the field and my colleagues regarding when a Job is created under Automation Central using property-based filters ( Virtual Machine Custom Attributes / Custom Tag ) would get saved as metrics. There is a published KB about this issue thanks to my colleague Murat Yılmazçetin, you can find the details below,

For Example:

• When creating a schedule job, set the filter criteria using the Custom Tag ( Properties -> Summary | Custom Tag – > Value ) and Save the Job
  

• Right after the save, job gets created. But the filter criteria parameters are immediately changed from ‘Properties’ to ‘Metrics’ ( Metrics -> Summary | Custom Tag – > Value )
  
  

This issue occurs when a job created in Automation Central using property-based filter ( Custom Tag ) are saved incorrectly in the database. This is a known issue with VMware Aria Operations (formerly known as vRealize Operations). There is currently no resolution an to work around the issue, use vSphere Tags instead of custom attributes at vCenter Virtual Machine to unblock them.

Cheers!