1
2
3
4
5
6
7
8
9
10
11
12
13
14

static void JDO_ChangeLanguage(Args _args)
{
    info("@SYS1");
    infolog.language('nl-be'); // Change the language to nl-be
    info("@SYS1");
    infolog.language('fr-be'); // Change the language to fr-be
    info("@SYS1");
    infolog.language('it'); // Change the language to it
    info("@SYS1");
    infolog.language('de'); // Change the language to de
    info("@SYS1");
    infolog.language('en-us'); // Change the language to en-us
    info("@SYS1");
}

And the result is:

Caution: When you use this function make sure you get the current language before you use this function, so you can change it back when you don’t need it any more.

• static TempStr numeralsToTxt(real _num)
• static TempStr numeralsToTxt_EN(real _num)
• static TempStr numeralsToTxt_ES(real _num)
• static TempStr numeralsToTxt_FR(real _num)
• static TempStr numeralsToTxt_NL(real _num)

So you can just use these methods like this:

static void JDO_AmountInWords(Args _args)
{
    info(numeralsToTxt(123456789.12));
}

And you get the following result:

I know these methods aren’t perfect, but they can be a start and save you a lot of programming time.

I’ve put a break-point on my postload method and noticed the recId (this.recid of the HRMBenefitType table). This is always the 101090. When I check this in the tablebrowser, this does not match the actual RecId valule.
I checked the SQL-trace-log and noticed the following instruction:

SELECT A.HRMBENEFITTYPEID,A.DESCRIPTION,A.RECVERSION,101090 FROM HRMBENEFITTYPE A WHERE (DATAAREAID=?) ORDER BY A.DATAAREAID,A.HRMBENEFITTYPEID OPTION(FAST 1)

The solution to this problem is simple. Just change the CacheLookup property to EntireTable and the strange behaviour of the RecId-field stops.

You can find the tables I wil discuss under the AOT –> System Documentation –> Tables.

• AccessRightsList : This table is used to manage the authorization of the usergroups in Ax (Be carefull). The most important fields in this table are:
  • GroupId : Usergroup (UserGroupInfo)
  • RecordType : Type of accessRights Table, securityKey
  • Id : Internal Id of the object on witch access rights have been defined
  • AccessType: Granted access rights (No Access, Read, Change, Add, Full Control)
  • …
• CompanyDomainList : This table contains relation between companies and domains.
• Common : The is the table that describes all other tables. It conains some important fields that return in all other tables. For example RecId, TableId, CreatedDateTime, …
• DataArea : This table contains data about created companies.
  Important fields:
  • Id : Company Id
  • Name
  • IsVirtual : Defines if the company is real (0) or Virtual (1). You often use this while looping trough companies with changecompany.
  • …
• DataBaseLog : This table contains data about which tables and events to log.
• DomainInfo : Table that contains info about the domains you have defined.

It is not easy to find info about these tables, but I hop this helps you all a bit.

The big idea: Try to split up your gigantic batch in smaller pieces. Launch a batchjob that produces many smaller batchjobs (tasks) that can handle a subset of the data you need to process. For example you can create a batch that creates a batch with sub-tasks for each company.

How do you plan a batch from code?

1
2
3
4
5
6
7
8
9
10
11
12

BatchHeader batHeader;
BatchInfo batInfo;
TstRunBase rbbTask;
;
rbbTask = TstMyBatch::construct();
batInfo = rbbTask.batchInfo();
batInfo.parmCaption("MyBatch");
batInfo.parmGroupId("");
batHeader = BatchHeader::construct();
batHeader.addTask(rbbTask);
batHeader.save();
info(batInfo.parmCaption());

You can download a quick example I made. This is a job you can schedule and it will produce a new Batch job with a task for each company when you don’t select a company while shedualing (Class_TstRunBase.xpo). I hope this can help you.

Schedule the batch:

The result:

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.

Small example:

if (isConfigurationKeyEnabled(configurationkeynum(AIF)))
{
    // Do something...
}

• General (shortcuts I also use outside AX)
  • CTRL + S : Save.
  • CTRL + C : Copy text to clipboard.
  • CTRL + X : Cut text to clipboard.
  • CTRL + V : Past text from clipboard.
  • CTRL + A : Select all.
  • CTRL + LEFT / RIGHT ARROW : Next/Previous word.
  • CTRL + SHIFT + LEFT / RIGHT ARROW : Select one word to the left/right.
  • CTRL + HOME / END : Go to begin/end of the editor.
  • SHIFT + HOME / END : Select text from the cursor to the start/end.
  • SHIFT + PAGE-UP / PAGE-DOWN : Select the previous/next page. of the line.
  • TAB / SHIFT + TAB : Indent Selection / Remove Indent Selection.
  • CTRL + BACKSPACE : Remove previous word.
  • CTRL + F : Find.
  • F3 : Find Next.
  • CTRL + Z / Y : Undo / Redo.
  • CTRL (+ SHIFT) + TAB : Next/Previous tab-page.
• Ax specific
  • Current Line in the Code Editor
    • ALT + L : Select current line.
    • CTRL + L : Remove current line.
  • Breakpoints
    • F9 : Insert / Remove breakpoint.
    • SHIFT + F9 : Show all breakpoints.
    • CTRL +F9 : Enable / Disable breakpoint.
    • CTRL + SHIFT + F9 : Remove all breakpoints.
  • Compile / Run
    • F5 : run / execute current Job / Class / Form
    • CTRL + BREAK : Stop execution.
  • Lookup / More Info
    • CTRL + ALT + SPACE : Lookup label.
    • CTRL + SHIFT + SPACE : Lookup definition (go to the method).
    • CTRL + SPACE : Show syntax information.

And there are more shortcuts. You can find them on MSDN.

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(); }