After some research we found a reproduction how these methods suddenly disappeared:

1. Go tot the AOT and chose a form
2. Open the [FORM] -> Data Sources -> [TABLE] -> Fields -> [A FIELD] -node
3. Add a method (for example the modified-method)
4. Save your form
5. Go to the properties of the table in the datasource
6. Place your cursor in the table property (properties window)
7. Push ENTER

The result is that the table will be reloaded in the form and all methods you created on the fields will be gone. So here you have another reason why you shouldn’t write lots of code on your forms. You can only lose it by accident.

1
2
3
4
5
6

queryBuildRange.value(strFmt('((%1 == %2) || ((%1 == %3) && (%4 == "%5")))',
                    fieldStr(InventTable, ItemType),
                    any2int(ItemType::Service),
                    any2int(ItemType::Item),
                    fieldStr(InventTable, ProjCategoryId),
                    queryValue("Spares")));

(you can find more info on Axaptapedia: Expressions in query ranges)

Now there is a limitation to this way of working. When the generated string in the queryBuildRange.value is longer than 250 characters (the length of the range EDT), Ax cuts the generated string off when you open the ‘modify query’ dialog. I have tried to enlarging the EDT, but is not a good solution. The error does not occure when you open the ‘modify query’ dialog, but it occures when you close it.
A small (but limited) work-around could be to make the name of the datasources on the form/report where you want to apply this trick smaller. I hope to find a better solution, but this does the trick for now.

public int task(int _taskId)
{
    int ret;
    ret = super(_taskId);
    // write you're code here
    return ret;
}

Now you just need to check the _taskId, to know witch key you have stroke. You can compare this withe the values from the Task-macro.

// Task-ID values, to be used with formControl's
// return value from the method task()
//--------------------------------------------------------
 
#define.taskF1(257)
#define.taskCtrlQ(264)
#define.taskEnter(288)
#define.taskShiftEnter(307)
#define.taskNew(260)
#define.taskSave(272)
 
#define.taskShortCutMenuKey(519)
#define.taskAlt(520)
 
#define.taskCut(770)
#define.taskCopy(771)
#define.taskPaste(772)
 
#define.taskDeleteKey(773)
#define.taskSelectAll(778)
 
#define.taskUndo(769)
#define.taskRedo(791)
 
#define.taskArrowUp(1281)
#define.taskArrowDown(1282)
#define.taskArrowLeft(1283)
#define.taskArrowRight(1284)
 
// PgUp and PgDn are the numerical keyboard page up and page down commands.
#define.taskPgUp(1285)
#define.taskPgDn(1286)
 
#define.taskEsc(1313)
 
#define.taskNextRecord(2817)
#define.taskPrevRecord(2818)
 
#define.taskDeleteRecord(2832)
 
#define.taskPageDown(2819)
#define.taskPageUp(2820)
 
#define.taskTab(2827)
#define.taskNext(2827)
#define.taskPrev(2828)
 
#define.taskShortCutMenuFilter(2844)
#define.taskShortCutMenuFind(799)
#define.taskFilter(2837)
 
// max task id
#define.taskLast(8191)

public void executeQuery()
{
    ;
    super();
    info(int2str(SysQuery::countTotal(EmplTable_ds.queryRun())));
}

But when you want to do the same when you joined multiple data sources, you will actually have to loop trough the whole selection. You can do this easily by calling countLoops() on the SysQuery-class. Keep in mind that this has a serious influence on your performance.

public void executeQuery()
{
    ;
    super();
    info(int2str(SysQuery::countLoops(EmplTable_ds.queryRun())));
}

Step-by-step:

• Define a object of the type ‘NumberSeqFormHandler‘ in the ClassDeclaration of the form

  1 2 3 4

  public class FormRun extends ObjectRun {     NumberSeqFormHandler            numberSeqFormHandler; }

• Create a new method on your form that create a new instance of the ‘numberSeqFormHandler’ object or creates a new object when it isn’t instanciated.

  1 2 3 4 5 6 7 8 9 10 11

  NumberSeqFormHandler numberSeqFormHandler() {     ;     if (!numberSeqFormHandler)         numberSeqFormHandler = NumberSeqFormHandler::newForm(TestParameters::numRefTEST().NumberSequence,                                                              element,                                                              TestTable_DS,                                                              fieldnum(TestTable,TEST)                                                             );     return numberSeqFormHandler; }

• Complete some of the existing methods with the correct method of the ‘numberSeqFormHandler‘ object:
  • Table : Create() –> The user creates a new record in the data source.

    1 2 3 4 5 6 7

    public void create(boolean _append = false) {     ;     element.numberSeqFormHandler().formMethodDataSourceCreatePre();     super(_append);     element.numberSeqFormHandler().formMethodDataSourceCreate(); }

  • Table : Delete() –> The user deletes a record in the data source.

    1 2 3 4 5 6

    public void delete() {     ;     element.numberSeqFormHandler().formMethodDataSourceDelete();     super(); }

  • Table : Write() –> The user inserts a new record or updates an existing one.

    1 2 3 4 5 6 7 8

    public void write() {     ;     ttsbegin;     super();     element.numberSeqFormHandler().formMethodDataSourceWrite();     ttscommit; }

  • Table : validatWrite() –> new or updated record is to be written.

    1 2 3 4 5 6 7 8

    public boolean validateWrite() {     boolean ret;     ;     ret = super();     ret = element.numberSeqFormHandler().formMethodDataSourceValidateWrite(ret) && ret;     return ret; }

  • Table : linkActive() à The user selects a new record in a form that has a data source linked to another data source.

    1 2 3 4 5 6

    public void linkActive() {     ;     element.numberSeqFormHandler().formMethodDataSourceLinkActive();     super(); }

  • Close() –> The form is closed.

    1 2 3 4 5 6 7

    public void close() {     ;     if (numberSeqFormHandler)         numberSeqFormHandler.formMethodClose();     super(); }

Step-by-step:

• You add a new field to your table that extends from the ExtendedDataType ‘LineNum‘. This field has the type Real.
  
• You create a new index with this field
  
• On the form you add your table as a DataSource and set the following properties:
  • Index : the index with the lineNum-field
  • CounterField : your LineNum-field
    

Now automaticly when you create a new record, the lineNum gets the value ’1′. When you create a record at the end of the table it wil get the value ’2′, ’3′, … In the beginning of the table, the value’s will be ‘-1′, ‘-2′, …

If you create a new record between ’3′ and ’4′, the LineNum-value will be ’3.5′.

When you want a example of this, you need to look at the ‘SalesTable’-form and the DataSource ‘SalesLine’.

Solution:
Use the methods pageActivated() / allowPageDeactivate() instead.

Source / More info:
http://dynamics-ax.blogspot.com/2007/06/yellow-lock-in-dynamics-ax-401.html