Client Access Log

http://blogs.msdn.com/b/axperf/archive/2011/10/14/client-access-log-dynamics-ax-2012.aspx

Cardinality and Related Table Cardinality

The Cardinality property corresponds to the notation on the child table (SalesLine in this case). So it should be ZeroMore (0...*). RelatedCardinality property corresponds to the notation on the parent table (SalesTable). So it should be ExactlyOne (1…1).

Semantically, Cardinality specifies how many instances of SalesLine row can be related to a single instance of SalesTable row. ZeroMore means that for every sale order, there can be zero, or more sales lines related to it. If the business requirement dictates that you need to have at least one sales line to be able to create a sales order, the Cardinality would be OneMore (1…*).

RelatedCardinality specifies how many instances of SalesTable row can be related to a single instance of SalesLine row. ExactlyOne means that every sales line should belong to one and only one sales order.

AX Forms

BI

Project and TimeSheet

From project --> Activity --> Scheduling and Resource Requirement, it allows skills to be added, and resources to be assigned.

At the project detail level, it also has scheduling and resource assignment fast tab.

Question is: how to bring in a resource to the project?

pack and unpack

The pack method must be able to read the state of the object and return it in a container. Reading
the state of the object involves reading the values of the variables needed to pack and unpack the
object. Variables used at execution time that are declared as member variables don’t have to be
included in the pack method. The first entry in the container must be a version number that identifies
the version of the saved structure.
container pack()
{
return [#CurrentVersion, #CurrentList];
}
Where #CurrentList is defined as:
#LOCALMACRO.CurrentList
TransDate,
Specification,
ProdJournal,
UpdateLedger,
#ENDMACRO

To run the business operation job on the server and push the dialog box to the client. When the job is initiated, it starts on the server, and the RunBase framework packs the internal member variables and creates a new instance on the client, which then unpacks the internal member variables and runs the dialog box.

On the client side, When the user clicks OK in the dialog box, RunBase packs the internal member variables of the client instance and unpacks them again in the server instance.

Client and Server Side Report

The MorphX framework is a proprietary client-side solution that is fully integrated
into the Microsoft Dynamics AX integrated development environment (IDE). In this model,
reports contain references to data sources that are bound to local Microsoft Dynamics AX tables and
views. They also define the business logic.

SSRS for Microsoft Dynamics AX, is a server-side reporting solution.
This framework takes advantage of an industry solution that offers comprehensive reporting
functionality for a variety of data sources. This platform includes a complete set of tools that you can
use to create, manage, and deliver reports. With SSRS, you can create interactive, tabular, graphical,
or free-form reports from relational, multidimensional, or XML-based data sources.