"this" vs. "element" keyword in X++

axapta x++ dynamics-ax-2009
Michael Brown picture Michael Brown · Nov 23, 2010 · Viewed 9k times · Source

When writing code in X++ you sometimes need to reference this.functionYouWant() and sometimes it is element.FunctionYouWant(). Sometimes both are in scope. I often try one and if the function I want isn't there I try the other. Is there a rule that explains when to use this and when to use element?

Answer

Allan Iversen picture Allan Iversen · Nov 23, 2010

this can be used in any objects to reference the current object and member methods.

MorphX forms and reports are composite objects.

In forms the collection of objects is contained within a FormRun object. You can reference members in the outer FormRun object by using the element reference.

If your code is placed at the top level there are no functional difference between this and element.

If your code is placed in a FormDataSource this will reference the datasource but element will reference the FormRun.

Related questions

What is the .toString() varient in X++ or Dynamics AX?

Is there something similar to the famous toString() method of C# in Axapta? I try to run underlying code: info(this.dataSource()); But it gives me this error message: "Argument 'txt' is incompatible with the required type."

Read More
join multiple tables to the same table using query class

I'm using the query class to build a query that will have two or three tables join to the same table like this: qbds1 = query.addDataSource(tablenum(Table1)); qbds2 = qbds1.addDataSource(tablenum(Table2)); qbds2.relations(true); qbds3 = qbds2.addDataSource(tablenum(…

Read More
ComboBox in X++

In my ComboBox there are items like A B C D and bydefault the value is A where i want to make it as C something like comboBox.comboType(2) in the init form, but this doesnt seems to work. May …

Read More