Same error here. On platform 220.127.116.11, Lifetime or SC.
When publishing via Studio (18.104.22.168) the problem doesn't occur.
Pretty sure I reported this as a bug ages ago.
Same error here on 22.214.171.124
This problem was already fixed in the versions 126.96.36.199 and 188.8.131.52 (Platform Server .NET and Java).
The bug caused two different types in OutSystems (for example, Integer List and User Identifier List) to be translated to the same underlying type (in this case List<int>), resulting in a compilation error as you've seen. The error would occur when compiling a Solution or Application. If you publish the eSpace alone, it should not happen.
You can avoid the problem by using a Record List instead of List for the OutSystems type.
I hope this information can help you overcome the problem.
Thanks Cláudia, that's informative, and good news :).
Great news... Thanks
They aren't planning to upgrade here for a few weeks yet and I don't want to wait that long. Is there any way to *search* for List of <AnyKindOfIdentifier>? I've been over the processes, interface screen methods, actions and web services with what I thought was a fine-toothed comb, but I'm still getting the error.
There's no one way to search for that. I take it you have a huuuuge eSpace that you can't find the problem?
As Kilian says, there's no way to search for that exact pattern, but a possible approach is to go through each Entity of the module (references included) and use Find Usages (F12). Then sort the results list by Property, and look for the uses in properties named Data Type.
It's not perfect, but hopefully it can help narrow down your search.
I'll try that, Paulo. Obrigado :)
No luck with that either, though it did make a good double-check for my previous manual checks. I had already converted my List of <x> Identifier over to List of Integer.
I'm starting to wonder if there are leftover artifacts somewhere.
I'd suspect an extension, but you can't actually use lists of identifiers with extensions; it's all record lists.
Is there an equivalent of "Build->Clean Solution" somewhere? :)
Since it occurs only when publishing an entire solution, I think you'll have to use the workaround of publishing the eSpace manually.