Substructure assigning error

freek

Rank: #469

Substructure assigning error

Question

Reactive

I have the following assign:

When I select the User.id I get the error:

Internal Error

Compilation Error.

Actions.ActionDebtCollectionDossierComment_List.cs(74,67): error CS0103: The name 'ssENUser' does not exist in the current context

target.ssComment.ssAuthor = new STSTR_USERStructure(null){ ssId = ssENUser.ssId };

State: Second stage compilation

on 2020-12-08

Hans

Rank: #361

Hi Freek,

can you present us the flow as well? to see where User.Id should be defined.

Regards Hans

on 2020-12-08

freek

Rank: #469

Hi Hans,

The User table is joined in the query

on 2020-12-08

freek

Rank: #469

The problem is I think a list is being mapped to a sub level.

on 2020-12-08

freek

Rank: #469

Only solution I know is to do it like this but it's not the fix:

on 2020-12-09

3 replies

Last reply on 2020-12-10

Show thread

Hide thread

Dorine Boudry

Rank: #128

Hi freek,

first of all, I have tried this out, and it is indeed related to trying to map an attribute on a lower level. Both trying to do it with an assign and with an AppendAll will result in a compilation error.

My question is, what do you mean with "it's not the fix", for aesthetic reasons or functionally ?

on 2020-12-09

freek

Rank: #469

Replying to Dorine Boudry's comment on 09 Dec 2020 18:24:06

I'm doing the assig now like:

Well it's a bit crappy to do a foreach instead of directly in the listappendall, so I think not a fix but a work around..

on 2020-12-10

Dorine Boudry

Rank: #128

Replying to freek's comment on 10 Dec 2020 11:13:59

ok, agreed, it's about the optics, right? So an alternative, is to have a mapper function importing user record and exporting author record, and use that in the ListAppendAll on the user author entity level, but I'm not sure I like that much better..., unless it's something you need in several places, then it might be worth it. And then again, maybe that would be bad for perfomance, don't know.

on 2020-12-10

Mikko Nieminen

Rank: #239

Hi,

You are probably very correct with this "list being mapped to sub level" idea. Here's an explanation from Microsoft for your error: https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/compiler-messages/cs0103

From this, I'm inclined to think that when OutSystems generates .NET code from this piece of yours, inner assign (author) does not have access to the scope where aggregate results are defined and outer record (comment) is assigned. As this mapping is done directly in assignment properties, aggregate results and your target structure/record are probably passed in to some internal mapping function. I've bumped to this same issue where sub-item mapping causes a compilation error, because something in code generation is incorrectly handled and results are not available in sub-assign/mapping.

Using temporary (action/screen) variables will move this sub-assignment one level up (or to a common scope) and therefore the second solution you posted works.

It's "just" a code generator after all.

on 2020-12-09

Training

Documentation

Substructure assigning error