Dynamics NAVAX

I had recently asked this question to Microsoft and thought I should share. Question: I am trying to make sense of the security AOT property ManagedBy. I can understand if I have to put something there to indicate it is being managed manually but why does best practice accept only the two values (that I found): Manual CodeAnalysis I have searched on msdn for more help but all it says is: ManagedBy Optional This property is for use by automation tools. http://msdn.microsoft.com/en-us/library/gg731858.aspx Answer: This property is used by one of our automation tools internally. We were using it simply so that we could write automations to help the feature teams to make sure they had all of the new security aspects covered for their objects. It could be used by a custom tool that checks the objects to make sure that all the security is implemented correctly for the objects by checking if the object should be managed manually or automatically.

The Business Operation Framework (BOF) lets you run services on Microsoft Dynamics AX using the Windows Communication Foundation (WCF) framework. The BOF uses an MVC programming pattern. What is a Model View Controller (MVC) Framework? MVC is a framework methodology that divides an application's implementation into three component roles: models, views, and controllers. Model:  The model manages the behavior and data of the application domain, responds to requests for information about its state (usually from the view), and responds to instructions to change state (usually from the controller). View: The view manages the display of information. Controller:  The controller interprets the mouse and keyboard inputs from the user, informing the model and/or the view to change as appropriate. Features of the Business Operation Framework Allows menu-driven execution or batch execution of services. Calls services in synchronous or asynchronous mode. Automatic...

These are simple code snippets to loop through a record from a data source. Using a while loop     salesLine_ds    = _salesLine.dataSource();     localSalesLine  = salesLine_ds.getFirst( true )   as   SalesLine;       if   ( localSalesLine )     {           while   (localSalesLine)         {                          //Do your thing             localSalesLine = salesLine_ds.getNext()   as   SalesLine;         }     } Using a for loop         salesLine_ds = _salesLine.dataSource();      for  (localSalesLine = salesLine_ds.getFirst( true ) ? salesLine_d...

When you compile and you get this error in AX 2012. "The element does not have an origin value. This element must have a non-null origin value." Just restart your AOS. That should sort it out.

This post is to highlight a pet project I have been working on. Working for a partner I frequently do new environment installations. AX 2012 allows you install multiple SSRS environments on the one machine but it can be tedious with the SSRS configuration file changes. http://technet.microsoft.com/en-us/library/hh389762.aspx I have scripted the process and loaded on here  http://dax2012ssrs.codeplex.com . Updated 26 March 2012: Added permission issue http://blogs.msdn.com/b/axsupport/archive/2012/02/02/microsoft-dynamics-ax-2012-reporting-extensions-error-system-security-permissions-environmentpermission-while-running-report.aspx Updated 21 January 2013: Added changes to be compatible with R2 http://dynamicsnavax.blogspot.com/2013/01/modify-microsoft-dynamics-ax-2012-r2.html