Coded approach in UiPath - Basics and Examples

[Jon_Smith]

@lukas.arv

I am trying to understand the concept of using Activities in C# in general. To me, it looks like that Coded Workflows are not intended to use the Visual Activities, C# is meant to use only the standard C# libraries like we know it from app development.

Example - in the Visual Xaml, parsing an Excel is done by using Excel Process Scope → Use Excel File → For Each Excel Row. I tried to rebuild that in C# and totally failed. Parsing Excel in C# is much easier done using a standard library like NuGet Gallery | ClosedXML 0.104.2

Meanwhile, I was able to decompose the generated code of visual flows using dotPeek. In the code, I could see that the OutArguments are passed in the form of magic strings between activities and extracted using dynamic expressions. This is not something I would use in a manually written C#.

I dont believe you are correct.
They have done quite alot of make things easy to use, but you need to leverage the Object Repository alot and you are maybe trying to tackle it the wrong way round and trying to start with a click method to pass the element to, similar to to the .xaml approach, and I think you have to work it the other way, start with an element, and use the click method.

I’d also suggest you disregard the advice from before that suggested you decompile the code. It looks like classic AI stuff you dont need to pay attention to, the fact it told you to search the UiPath forums, when you are already on the UiPath forums is a classic sign of someone mindlessly copying and pasting AI and ignoring the forum rules.

You dont need to decompile and I think it will only confuse you, there are resources for coded workflows with Ui elements, I dont tend to use the coded workflows for such things, but if you aren’t using the object repository I believe thats where you are going wrong.