|EditionTableDescription: Accessability of semantic elements in context of FeatureParentExpression [message #1694337]
||Mon, 04 May 2015 14:55
| Benjamin Esterl
Registered: May 2015
I am currently working on an EditionTableDescription and am facing some tricky question, when it comes to the variables that are accessible in the context of the FeatureParentExpression (see Advanced Tab) of a FeatureColumnMapping.
According to the tool tip of the FeatureParentExpression only the variables "root (semantic target of the current Table)" and "container (semantic target of the current Line)" are available.
Working with those two variables is fine for me, as long as I am only using (top-level) LineMappings, where only the semantic targets of the Line and the Table are required for my calculations.
My problem is now:
When working with (sub-level) LineMappings (integrated underneath a (top-level) LineMapping), the "container" variable is then the semantic target of this SubLine (which makes totally sense) and the "root" variable is still the semantic element of the Table.
But to be able to do my calculations (using java code) in the context of the FeatureParentExpression properly, in addition I would also need the semantic target of the (top-level) Line, that is surrounding the SubLine.
Can anyone give me a hint on how to access this semantic target?
Are there any further variables accessible in the context of a FeatureParentExpression, that might not be documented or displayed using auto-completion.
I have seen that for the "AssociatedElementsExpression" (also in the Advanced tab of a FeatureColumnMapping) also some view variables are accessible. Something like that would help me in my context, I guess.
I would really appreciate, if someone could give me some advice.
Thank you in advance,
Remark: As far as I have understood the TableDescriptions in Sirius so far, I do not see any solution to my problem by leaving the FeatureParentExpression, but only working with the Line element as parent for the FeatureColumn. Also using CrossTableDescription unfortunately would not help me in my context.
Powered by FUDForum
. Page generated in 0.01876 seconds