Delete key in JObject

[ppr (Peter Preuss)]

Kindly note as mentioned above

@ppr

Also do not use the same variable names for argument names / parameter names

[postwick (Paul Ostwick)]

Ok, that looks correct. Now, you have deserialized your JSON string into an actual JSON Object, and the datatype of the myJObj variable is Newtonsoft.Json.Linq.Jobject yes?

[postwick (Paul Ostwick)]

It’s perfectly fine to use the same name. The argument only has a local context, and in fact if they’re named the same UiPath will automatically pass the variable through to the argument. This is very useful in Invoke Workflow, for example. Say you have your Config dictionary in Main.xaml and call Sub.xaml with Invoke Workflow - as long as you create an argument named Config with the same datatype, UiPath will automatically pass Config through to Sub.xaml

[ppr (Peter Preuss)]

@postwick

as long as you create an argument named Config with the same datatype, UiPath will automatically pass Config through to Sub.xaml

is case as Argument is forwarded to Argument. However, everyone can decide by their own. No interest on a follow-up discussion. Coming back to the topic. We do see a ping-pong series with a length of 24, where much more above from two ends the working building block is shared. So now the topic should come to an end and get it done.

[Sahil_Garg1]

Actually, requirement needs an array as in input.

So above array expression is working fine, instead of invoke method for me