What is a wildcard within the Job API "filter" argument for InputArguments?

I’m having an issue with using the Job API for this filter string:

(State eq 'Running' or State eq 'Pending') and ReleaseName eq 'xGL.OL.Approvals.Dispatcher_DEV-All Robots' and InputArguments eq '{"in_xGLInstanceName":"XGT1","in_olaStartDate":"*","in_olaLookAheadDays":"*"}'

What I have discovered is the Job Activity and Job API works both work when you have hard values for the filter criteria for InputArguments. As an example, this works:

(State eq 'Running' or State eq 'Pending') and ReleaseName eq 'xGL.OL.Approvals.Dispatcher_DEV-All Robots' and InputArguments eq '{"in_xGLInstanceName":"XGT1","in_olaStartDate":"04/01/2022","in_olaLookAheadDays":"29"}'

But … how do you do a search when you want to have one InputArgument with a specific value and the others are just wildcarded. Assuming odata.org still applies here and “*” seems to be a wild card specification but it’s not working in the above.

Anyone know if wildcarding for InputArguments is possible ?

1 Like

Hey @riverrat437

Just remove the property from the filter which will consider any values and use contains operator

Thanks
#nK

Thank you for the reply !! :slight_smile: Can you provide an example ?

1 Like

@Nithinkrishna, can you provide an example of this ? I don’t understand what you mean by your reply.

Thank you again for your reply :slight_smile:

1 Like

Hey @riverrat437

Something like below,

(State eq 'Running' or State eq 'Pending') and ReleaseName eq 'xGL.OL.Approvals.Dispatcher_DEV-All Robots' and Contains(InputArguments, '"in_xGLInstanceName":"XGT1"')

Thanks
#nK

1 Like

Thank you so much … Works great !

1 Like

Cool @riverrat437 :slightly_smiling_face::+1:

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.