Tips to resolve issues of adding new data sources in list pages

Dear Friends,

As we all know, to include new fields in a list page, we need to work in the queries (at times adding a new data source, specifying the proper joins and relations) and also may need to work in the interaction class.

At times, doing this also, we do not get the newly added data source in the existing list page's data sources (after doing a "Restore" in the form as well); although for new forms, it gets properly displayed.

To overcome this, we need to do the following thing - 

• Right click on the data sources in the form.
• Re-select the query once again, and save the form.

Once it is done, the data source will get properly refreshed, and only then the design level changes can be achieved.

Tips of using LCS and Visual Studio Online for code upgrade functionality in Rainier

Dear Friends, 

We all are very much excited about Rainier, and quite a few of us have already started working on AX 7.0 (Rainier) technical previews (CTPs). In earlier versions of AX, using Life Cycle Services (LCS) was not a mandate, but now with Rainier, it seems to be a mandatory thing. Thought of sharing few important tips and steps related to integration of Rainier with LCS, for upgrading of codes from AX 2012 - 

• As of now, to connect LCS for obtaining the functionalities related to Rainier, one need to have an account on "OnMicrosoft" Azure domain account.
• Project needs to be created in LCS.
• VSO (Visual Studio Online) and LCS needs to be synchronized along with the project and get connected.
• LCS does have a "Code Upgrade" tool, where the model store needs to be uploaded. 
• It analyses, upgrades and creates Visual Studio project solutions (normally 2 solutions gets created, one for upgraded objects, and another one for upgrade conflict objects). 
• Each solution will have model and layer specific projects.
• As of now, LCS code upgrade facility is available only for AX 2012 codes.
• Developers need to analyze and fix the issues, so as to obtain an error free build.
• BP deviations also needs to be analyzed and needs to be addressed, depending upon the criticality and feasibility of the same.

Common issues and solutions while importing ISV license file

Dear Friends,

When we think about preparing an ISV solution, Microsoft Dynamics AX 2012 allows ISVs to create encrypted license files using x509 certificates, to protect their intellectual property. When customers deploy ISV modules to their environment, they are required to import the license file to enable the module. During the license import process, the certificate that is used to sign the file is checked against the root certification authority to verify its validity. In certain cases, however, the root authority may not be available in the system and thus requires an internet connection to check the validity through CA (Certificate Authority). The process steps are –

• Perform the standard installation.
• Import the certificate (this needs to be imported under “Trusted Root Certification Authorities”).
• Import the model or model store (certificate needs to be imported prior to this, as this will change the signature of model to “Yes”).
• Import the license file (the license file needs to be generated by the ISV partner, seeking the required details from the customer or partner, where ISV will be deployed; and providing the certificate related inputs).
• Synchronize the database.
• Compile and full CIL of the application.

But at times, in spite of importing the certificate and the model/model store; we get stuck while importing the license file. To achieve this, the following steps needs to be followed –

• Launch MMC.exe.
• Go to File > Add/Remove Snap In.
• Go to Certificates.
• Click “Add”.
• Select “Computer Account”.
• Click “Next” and “Finish”.
• Click Local Computer > Trusted Root Certification Authorities > Certificates > Import.
• Follow the wizard to import the certificate.
• Try importing the license file.