Hi friends, I have a problem when trying to using the Event trigger List Item Added.
When setting up the process in Studio, data types of Studio.Generated.TypedDataRow are created, and I can see them in the XAML as Studio.Generated.TypedDataRow1, Studio.Generated.TypedDataRow2, and so on. This causes an error when trying to publish the project to Orchestrator.
I can of course go into the XAML and manually remove this generated types, but really… should that be necessary? Also when I later activity, wham the generated types are back. What is going on here?
Using Orchestrator Cloud and Studio 2025.10.1 LTS.
Can you please mention exactly what error you are getting or you can share the screenshot of the error that you are getting while publishing the project to Orchestrator. It will help us to gain a better understanding of the issue.
The assembly compilation returned the following errors:
* (618,106): error CS0266: Cannot implicitly convert type 'System.Data.DataRow' to 'System.Data.DataRow3'. An explicit conversion exists (are you missing a cast?)
* (618,106): error CS1662: Cannot convert lambda expression to intended delegate type because some of the return types in the block are not implicitly convertible to the delegate return type
* (624,24): error CS0266: Cannot implicitly convert type 'System.Data.DataRow' to 'System.Data.DataRow3'. An explicit conversion exists (are you missing a cast?)
If I go into the XAML and manually removes all references to DataRow3 I can publish, but the moment I changes something I get new generated type is created (DataRow4, 5, and so on)… and then have to clean up XAML-again. Very cumbersome.
Let me know if you need some more information. Thanks.
It does generated these hard types because of the new change to sync with cross platform and studio web..but ideally it should not revert automatically
can you please delete the .local files and other folders starting with . in the project folder after changes and save and then reopen and check…
or to verify try to create a new xaml with same activity instead of creating the variable automatically try to add datarow variable and select it in the output field of the activty and see if that sorts the issue
Good morning,
I am using version 3.5.10 of Microsoft activities. Have tried several version, same issue.
As for why I am changing to normal System.DataRow:
We are working in a team, and checks in code to Bitbucket. If using DataRow3 etc, then someone else who checks out my code with DataRow3 will get an error on that type.
Also (if I remember correctly) I also got errors myself when trying to publish DataRow3, 4, 5, etc.
So just to clarify: I can change from DataRow3 to System.DataRow and the project runs fine locally, no problem. It is just when I am trying to publish to Orchestrator I get the error mentioned above. If I manually go into the XAML and edit it manually by removing all references to DataRow3, I can publish to Orchestrator and everything works fine. But the next moment someone changes this activity, wham another Studio.Generated.DataRowX is back, and we once again need to manually remove all references to DataRowX.
Why does it change to generated types? Why not use normal DataRow?
If possible, testing it out on one of the latest STS Studio releases would be really appreciated. There was work related to how those types are handled, and there is a chance it is already fixed.
Thank you. This would help us rule out certain possibilities of what could be wrong here. From the look of it, the Studio team might have already fixed it on the latest STS.
