Execute Macro Activity Vs Invoke VBA Activity

So i am starting to experiment with macros in my automation and i was just wondering what is the best practice to use the Execute Macro or Invoke VBA activity? Is there any difference between them? Are there cases where you would use one over the other?

1 Like

In UiPath, the Execute Macro and Invoke VBA activities are both used to run VBA code in an Excel workbook. The main difference between them is that Execute Macro is used to run a macro that is stored in the workbook, while Invoke VBA is used to run VBA code that is written directly in the activity.

The Execute Macro activity is best used when you want to reuse a macro that is already defined in the workbook. This can be convenient if you have a macro that you use frequently and want to be able to run it from multiple places in your automation process.

The Invoke VBA activity is best used when you want to run a small piece of VBA code that is specific to a particular task and does not need to be reused elsewhere. This can be convenient if you only need to run the code once and don’t want to create a separate macro for it.

In general, it is a good practice to use Execute Macro when running a macro that is already defined in the workbook, and to use Invoke VBA when running a small piece of VBA code that is specific to a particular task. However, the choice between the two activities will depend on your specific requirements and how you want to organize your VBA code.

1 Like

Try to go through this Execute Macro vs Invoke VBA video on Youtube for further understanding.

Thank you :smile: