Make automatic detection of TypeArgument in ForEach optional

[lukasziebold]

…or revert the whole thing for Studio. You can give it to the business users in StudioX, but we hate to lose control over the TypeArgument and are rolling back on System.Activities packages so we don’t have to deal with this non-sense.

The “feature” was introduced in UiPath Community 2022.4 Stable Release - Studio

Take a look at these threads:

For Each Activity (Community Version)

In regards to the For Each activity, in previous versions I could select the typeArgument. I upgraded to the newest version a few days ago and it doesn’t allow the TypeArgument to be set anymore. Defaults to System.Object, want to change it to something else. There is no place to change this either in Advanced Options. Am I missing something? Kind regards [For Each]

How to change TypeArgument in For Each activity in Studio Version 2022.10

After the Last studio update, the For Each activity no longer shows any properties in the properties panel. It just says that All properties are visible within the activity card. in the activity card, there is no option for changing the typeArgument of the current iteration item or even renaming it. Here is my case: I want to change the typeArgument for item variable to system.Net.MailMessage to be able to access mail messages properties like subject, body …etc. [Screenshot]

Not able to access Type Argument for For Each Loop

In current version (2023.4.0) of Studio I am not able to change the type argument of my collections. Please help.

Even MVPs recommend downgrading the System.Activities package.

@loginerror - may I get some info if this is on your radar?

Thanks and best regards
Lukas

[loginerror (Maciej Kuźmicz)]

@lukasziebold

@loginerror - may I get some info if this is on your radar?

It is @lukasziebold. We will definitely address this soon.

[Jon_Smith]

Can I make a suggestion that with alot of these new stuff you try out, that you typically make it something that can be ‘overidden’ or reverted? I realise that can mean dragging along some legacy stuff (like having classic activities still be a thing even though Modern Design in the intended way to use Ui Automation now) but I think its better at least at the beginning to allow bugs and issues to not be chronic.

Certain things I think just make sense to be optional. Like the If layout being vertical or horizontal. In the For Each I think it always makes sense to let the user override the suggested data type, even better, an option on the activity to allow it to automatically infer data types or not so I can turn off it trying to if I don’t want that.
Just give us choice, we’ll know how to use it

[loginerror (Maciej Kuźmicz)]

Just to close the loop on this topic. System 2023.10 package brings it back. It will still auto detect, but one can override the detection when needed.