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.

Have fun with the http://www.axepclipboard.com.

After some research we discovered this issue occurred only with a few user groups and that the message only exists in the KTD-files, so it is kernel related. We checked the AccessRightsList-table for some inconsistencies but no luck. In the end we found a work-around that helped us solving this issue. When we make a export of the security and afterwards we import the export we just made, the issue disappeared by itself. Because there are a lot of user groups that could be infected with this issue, we automated this fix by running the import – export in a job.

The normal Url of the page: http://***/TSTReplacement.aspx?WCMP=TST

The Url for the rolecenter-view of the same page: http://***/TSTReplacement.aspx?WCMP=TST&RUNONCLIENT=1

The Url for the same page without any navigation: http://***/TSTReplacement.aspx?WCMP=TST&NONAV=1

You can find the logic behind this in the masterpage that Sharepoint is using. The masterpages can be found under C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\DynamicsAxEnterprisePortal\defaultax.master.

In the beginning of this file you see the methods runningOnClient() and hideNavigation():

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47

<%@Master language="C#"%>
<%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Register Tagprefix="Utilities" Namespace="Microsoft.SharePoint.Utilities" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Import Namespace="Microsoft.SharePoint" %>
<%@ Import Namespace="Microsoft.SharePoint.ApplicationPages" %>
<%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register TagPrefix="wssuc" TagName="Welcome" src="~/_controltemplates/Welcome.ascx" %>
<%@ Register TagPrefix="wssuc" TagName="DesignModeConsole" src="~/_controltemplates/DesignModeConsole.ascx" %>
<%@ Register Tagprefix="Dynamics" Namespace="Microsoft.Dynamics.Framework.Portal.UI.WebControls" Assembly="Microsoft.Dynamics.Framework.Portal, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" %>
<%@ Register Assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="System.Web.UI" TagPrefix="asp" %>
 
<%@ Assembly Name="Microsoft.Dynamics.Framework.BusinessConnector, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, Custom=null" %>
<%@ Import Namespace="Microsoft.Dynamics.Framework.Portal" %>
<%@ Import Namespace="Microsoft.Dynamics.Framework.Portal.UI" %>
<%@ Import Namespace="Microsoft.Dynamics.Framework.BusinessConnector.Session" %>
 
<script runat="server">
 
    bool runningOnClient()
    {
        return (Context.Request.Params.Get("RUNONCLIENT") == "1");        
    }
 
    bool hideNavigation()
    {
        return (Context.Request.Params.Get("NONAV") == "1");        
    }
 
    string getStyleRunOnClientDisplayStyle()
    {
        if (runningOnClient())
            return "";
        return "display:none;";
    }
 
    string getStyleRunOnBrowserDisplayStyle()
    {
        if (runningOnClient() || hideNavigation())
            return "display:none;";
        return "";
    }
 
    string getStyleRunOnBrowserBorderStyle()
    {
        if (runningOnClient() || hideNavigation())
            return "border-style:none;";
        return "";
    }
...

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.

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.

Anyone any idea?

Workaround:
When you edit your page in Sharepoint, you can remove the ‘Dynamics Page Title Web Part’ and replace it by the old ‘Page Title Web Part’

Explanation:
The reason why there are two Web Parts is mainly the “Page Title Web Part” is the old Web Framework (Dynamics AX 4.0) – and rendering takes part in X++ code while “Dynamics Page Title Web Part” is implemented completely in C#.

(Source: Microsoft)