Search This Blog

Wednesday, November 30, 2011

Now, we had a requirement to output the file in utf-8 encoding format and the credit for this post goes to Super Mario (Read below to find who Super Mario is ;-) ..) for his tip which I'm sharing with you all.

Tip/Solution:

The UTF-8 encoding was achieved by using an additional parameter while calling the constructor for CommaTextIO class.The 3rd(optional) parameter is the codepage integer value. It was achieved as per below:

commaTextIo = new CommaTextIo(fileitemdata,#io_write, 65001);

65001 is the Codepage identifier for utf-8

What's interesting in Dynamics AX 2012 for UTF-8:

I was curious to know how UTF-8 is implemented in the new version of Dynamics AX 2012 and did a search at the AOT Level, found that now we have a placeholder for UTF-8 format in AOT > Macros > File

I compared the File Macro in AX 2009 and AX 2012, in AX 2009 there’s no macro for utf-8 but in AX
2012, we have a declaration for it in Macros > File

/*

UTF-8 Format

*/

#define.utf8Format (65001)

But surprisingly it's not used anywhere for e.g. if you see the EditorScripts Class in Dynamics AX 2012, it still uses the literal value 65001 and not the Macro which is defined above.

Thursday, November 24, 2011

Today, while writing a QueryRange, I had to pass a blank InventDimid. Initially, to make life easier ;-). I just put "BLANK".

Then, just did a bit of search and found that InventDim has a static method inventDimIdBlank which was exactly what I required. It returns "AllBlank". Many of you guys might be knowing this one, but just for the ignorant out there (including me) :-) this is a handy tip

One of my mates asked me how to retreive AOS Instance name through code. My first impression was that it should be somewhere in the Global Class. But, soon figured out I was wrong, then I jumped into Session Class which has a static method getAOSInstance() which retreives the instance number

The requirement here was to extract the instance name. Suddenly, it striked me, that in standard AX in Administration > Online Users form, the last column shows the AOS instance name.

So, the next step was to go through AOT > Forms > SysOnlineUsers > display method getAOSInstanceName() - here the key is serverSessions.aosId and serverSessions.Instance_Name - combination of both will give you the aos instance.

Tuesday, November 22, 2011

I wanted to do some User Permissions testing using Dynamics AX Client with different users using Run As Option. i.e. Right-Clicking the client and then bringing up the Windows challenge dialog wherein one can put the user name and password shown below

In previous versions of Windows, when you right-click it will bring up the Run as and you can put the user name and password, but with Windows 7, When you Right-Click it just shows "Run as Administrator"

If you need to "Run as different user" then you need to hold the SHIFT button and then Right-Click AX Client.

RapidStart Services is a configuration and setup cloud service from Microsoft that allows a fast and easy way to configure and deploy Microsoft Dynamics AX business processes and scenarios. The core benefits for you as our partner would be:

Thought to share with you, the latest whitepaper on Credit Card Processing in Dynamics AX 2012. At a high level, it shows how to setup Credit Card for AX 2012 which integrates with Dynamics ERP - Payment Services provider.

This whitepaper would serve beneficial for those who are planning to implement Credit Card integration with Dynamics AX 2012. Also, Microsoft has a hotfix for Dynamics AX 2009 which is mentioned in the whitepaper.

Monday, November 14, 2011

Apart from AX, In my current role, I have been extensively working on MOSS/Sharepoint Administration and Troubleshooting, Configuring Kerberos Authentication for SQL, MOSS Server and SSRS, Planning for Disaster Recovery, Troubleshooting SSRS.

This post is on my experience on setting up Kerberos for our standalone MOSS, SQL and SSRS Servers and troubleshooting IIS for Kerberos.

Logon to SSMS (staying in the same box) and fire the below SQL, if SPN’s are properly setup, then you should see KERBEROS in auth_scheme field.

Another way to test if Kerberos is being used as Authentication scheme is to bring up Central Administration site and now go back to TEST-DEV1 (the host box where SQL is running). Bring up the Event Viewer (check Security tab)

In the Security Log, you should be able to see Success audit record for Logon/Logoff category event

Check the Detailed Authentication information and should be able to see the Login mechanism as Kerberos which confirms our test that MOSS is communicating with SQL via Kerberos

Setup Kerberos for MOSS Server (TEST-DEV2)

Register SPN’s for MOSS Server (Service account) in the similar fashion as we did for SQL:

Register with NETBIOS name

Register with FQDN name as shown below

Browse to Central Administration website and confirm by going to the Event Viewer of the hostmachine in Security log, (similar to the steps we performed for SQL) that the authentication package here is Kerberos

Note:Tried both the options but Option A works fine with Option B, there’s this frequent system crash as I reckon it’s changing the applicationhost.config file settings. Need to check this behaviour in Production Server as Option B is more performance friendly and recommended approach

Troubleshooting tip: You may run into error rsaccessdenied: The account SHarepoint/System doesn’t have permissions to deploy the report. In order to troubleshoot this error, check if spn’s are properly registered with the sharepoint service account and there’s no duplicity of SPN’s.

Thursday, November 3, 2011

Got this run-time error during a full run of inventory settlement data - "Error executing Code: Overflow in internal run stack.

Troubleshooting Steps:

After some investigation, found out that this was being caused due to circular reference in one of the settlement transaction due to which the container fills up thereby resulting in run-time stack overflow.