Andy,

I'm glad you were able to resolve the issue. Basically, the For Each command only accepts input as a collection of "something". In this case, the datatable is converted to a collection of datarows. Our inline coding functionality allows you to easily do this by employing the .Rows property.

Commands rename upgrades were not included in the release notes. However, hovering over the "Input Collection" field title, will show you a datatable example as: vMyDataTable.Rows. In addition, you can generate documentation for all commands by navigating to the Studio's toolbar > Options > Settings Manager > Generate Documentation.

Also, we are currently working on upgrading website documentation and videos to better assist users understand the updates and changes included in the latest OB Studio and Server.

Stay tuned!

Hello Nataly,

Yes, I was able to resolve the problem per my post late last night.

I checked the Release notes of v1.5 Studio and I don't see any notes on such updates. Is there any other documentation source I have can browse through?

Thanks, Andy

Hello Andy,

Yes, the Loop Collection command has been renamed to For Each command, to better represent its functionality. In order to loop through a datatable, you will need to convert it to a collection of rows.

For example, let's assume you have a datatable variable called DT1. In order to loop through it, you would use the For Each command and indicate the following fields:

Input Collection field: DT1.Rows
Output Collection Item Variable field: vDTRow

Where vDTRow is a datarow variable created to hold the current datarow value.

Let me know if you are able to reproduce the indicated steps!

Ok, I don't know if this is the only solution, but I had to import the System.xml from the Imports tab at the bottom and then use the For Each action in the following manner:

For Each excelRow in ExcelDT.Rows Access data as excelRow[x] to do whatever End For Each

I also installed the System.Xml.XmlSerializer package from the package manager. But I don't think that this is really required, but I will test this tomorrow to confirm.