Monday, 4 February 2013

Difference Between OLTP and OLAP

OLTP:



  • Operational data; OLTP's are the original source of the data.
  • To control and run fundamental business tasks.
  • Short and fast inserts and updates initiated by end users.
  • Relatively standardized and simple queries Returning relatively few records.
  • Backup religiously; operational data is critical to run the business, data loss is likely to entail significant monetary loss and legal liability.




OLAP:



  • Consolidation data; OLAP data comes from the various OLTP Databases.

  • To help with planning, problem solving, and decision support.
  • Periodic long-running batch jobs refresh the data.
  • Often complex queries involving aggregations.
  • Instead of regular backups, some environments may consider simply reloading the OLTP data as a recovery method.


Thursday, 24 January 2013

Parsing XML in Dynamics Ax 2012:



 Today I will be sharing "How to parse XML in AX 2012 " . I have used  XPath for navigating through the elements and attributes in XML. By the use of XPath it becomes very easy to parse an XML for selected nodes only.

 
This was my XML and I have to fetch all the Ownership prefixes for Group node having name attribute set to "GFM" and within that only that team which has name attribute set  to "Public Sector SL1" . After fetching the values of Prefixes I have to insert all those values in a table of type (tempdb) .

Now , I will show how i achieved that..

That's how my project looks..


This is my simple Job that does that all for me..


I defined my XPath in a Macro (#node) and passed that (#node) to XmlGroupnameNodeList . Have a look at this XPath ('//Team[@name="Public Sector SL1"]/Ownership/@prefix') it looks for Team node any where in the document having its name attribute set to (@name="Public Sector SL1") and within that team node it looks for the values of Ownership prefixes (Ownership/@prefix) .

I believe it was helpful....




Thursday, 6 December 2012

Unit Of Work Implementation in Dynamics AX


UNIT OF WORK:

Unit of work keeps track of everything you do during a transaction that can effect the database. It keeps track of everything that needs to be done to alter the database as a result of your work.

There is a system class called UnitOfWork Class in X++ that implements the Unit Of Work Framework. Some of it's details are given below.

Clear
 Clears all the changes
DeleteonSaveChanges
 Deletes the record on commit/save changes
InsertOnSaveChanges
 Inserts the record on commit /save changes
UpdateOnSaveChanges
 Updates the record on commit /save changes
SaveChanges
 Save the changes on the server

Implementing the Unit Of Work:

In this example we will perform bulk insertion on tables , this is where the role of Unit of work comes into play . By means of it we can insert lines against a header record without creating the header first on the basis of the Rec Id that comes as a foreign key in the child table.

Example:


In this example you can see we have created two tables :
  • Candidate 
  • Exam
Where the Exam table behaves as the header table and the Candidate tables acts as the Lines.The Screen shot below shows the relation between them.


After this step we need to set the CreateNavigationPropertyMethods Property to Yes.  As Shown in the screen shot below.


After that we need to create a new class and add a Method in it that will perform all the calculations and insertions , as shown in the screen shot below.



 Finally we need to call this method in a job. The results can be seen by opening the tables.



In this way the DataSources can be grouped as a unit of work and Ax Client has great support for it.

I believe it was helpful.  


Tuesday, 4 December 2012

Work Flow in Dynamics Ax 2012


WORKFLOW:


A Work Flow can be defined as a sequence of steps where each steps follows the precedent without any gap or delay.It can also be defined as a movement of tasks within a process. The Dynamics AX Work Flow infrastructure enables user configurable workflows in Dynamics Ax application modules with specific focus on tasks and approval workflows.



A Work Flow is designed based on the company requirements then Configured by the administrator , and run by the user.

BASIC CONCEPTS:

Work Flow Type:

It is the basic building block that can be used to create customized workflows that enforce business policies. A Work Flow type defines :
  • The Work Flow document to use.
  • Tasks and approvals that can be configured by the User.
  • Workflow categories used to assign a workflow type to a specific module.
  • Menu item and Event Handlers to be used.

Work Flow Configurations:

These are created by the application administrators that use Dynamics Ax Work Flow editor. The administrator configures the:
  • Work Flow
  • Workflow Elements.
  • Approval elements to control the flow of business document through workflow process.

Work Flow Instances:

Created by the Work Flow run time when the workflow is activated.

Work Flow Elements:

These are created in the AOT and configured by the administrator. A Work Flow structure consists of a sequence of Work Flow elements that includes:
  • Tasks
  • Approval
  • Sub-Work Flow

Developer's Role:

A Developer adds Work Flow to an existing business document or Creates new document that support Work Flow. A developer performs these steps :
  • Creates a Query for Work Flow.
  • Creates a Work Flow Category.
  • Creates a Work Flow Type.
  • Creates Work Flow elements.
  • Enables Work Flow on a Form.

Creating Query For Work Flow:

An AOT Query can be simply created under the Queries node in AOT. Right click on the queries node and  Create New Query.


for further information on queries see  here

Creating Work Flow Category:

Expand the Work Flow node and right click on the Work Flow categories node to create a new Category.


In the Property Sheet for the newly created module set it's name and module properties.

Creating Work Flow Type:

To create Work Flow type we need to run a Workflow Type wizard.
AOT--> Work Flows--> Work Flow Type  right click and then go to addins and run Work Flow Type wizard.


Create Work Flow Elements:

To Create Work Flow elements we have multiple ways . For (e.g) In order to create an Approval Element for the workflow we can run an Approval wizard as shown below.


Or you can create tasks by these steps:
AOT--> Work Flow-->Tasks-->New Task

Enabling Work Flow on a Form:

Expand the form , expand it's designs node and on the design node right click properties. On the Properties window set the following properties:

Work Flow Enabled       :        ( Yes ) 
Work Flow Data Source:        (Data Source for the Query)
Work Flow Type            :        (Work Flow Type Created)








Thursday, 22 November 2012

Exceptions in Dynamics AX 2012



Exceptions:

       
A Situation in which the flow of a program is interrupted is called exception . A program must handle them For example: If a user requests a record to be fetched and that record doesn't exists then in that case system must throw an exception. There are many types of exceptions thrown depending upon it's cause . All of them can be caught so it's a developer's decision to decide which exceptions must be handled by the system.

Some common exceptions are listed below:







Try , Throw ,Catch & Retry Statements :


Try: 

       These statements indicate the start of the block of code that you are going to handle with X++ Exception handling system . Any exception thrown in this block can be caught in the associated catch statements.

Throw:

       These statements are used to explicitly throw an exception that can be caught by the Catch statement.

Catch:

       These statements define what code is going to be executed in case of an exception being thrown . These statements come after the Try statement. It is not necessary to catch each try statement But each Try statement must have a corresponding Catch statement.

Retry:

       These statements tell the system to go back to the Try statement and attempt to execute the code again , any data loaded before the Try statement remains the same where as any data loaded after the Try statement will be refreshed.

Optimistic Concurrency Control ( OCC ) :


It is a performance enhancing function within Dynamics AX . It assumes that a record retrieved from the database is not updated , until it is proven to be updated by the database which means that in case of updating a record the system compares the rec Version field of the record with the actual record in the database. The rec Version field is updated each time a record is successfully updated. There are two exceptions thrown in case of a record been updated in a transaction using Optimistic Concurrency Control.


 Handling Exception in Code:





























In the above example in the Try block an exception is thrown if the user lefts any dialogue field empty or if the AccountNum already exists. This Exception is then caught in the Catch Block later in the code .

I believe it was helpful.

  

Tuesday, 6 November 2012

Dynamics Ax 2012 Security


SECURITY :


       Role based security defines the access to Microsoft Dynamics Ax 2012 application and data . It relates to the job role that an end user has with in an organization . The role includes the duties, privileges and permissions required by that role.
  
        The maintenance of roles and duties is typically undertaken by the system administrator  where as the maintenance of privileges and permissions is performed by the developer.

BASIC CONCEPTS:


 Security Roles:

          It depicts the behavior that a person in an organization can play. A Security role includes one or more duties.
   

 Duties:

       A responsibility to perform one or more tasks. A duty requires one or more privileges in order to perform that duty.

 Privileges:

         The access required to perform a duty. A privilege includes one or more permissions.
  

 Permissions:

         The level of access associated with one or more securable objects that are required to perform the function associated with an entry point.

 Designing Role Based Security:         

  1.  First of all we need to set up a new user .
  2.  The end user is assigned one or more security roles.
  3.  Security role is assigned one or more duties.
  4.  Duties require one or more privileges.
  5.  A privilege contains one or more permissions.
Have a look at this example:



According to the above diagram the Accounts Receivable Manager Role has the duties of maintaining customer master and to inquire chart of accounts for which it requires privileges (i.e) delete access to customer form display menu item and create new address action menu item But in order to know the level of access it requires permissions on that form  (i.e) Read , Update , Create , Delete. 

I believe it was helpful ..

For further reading you can refer other useful links like:
  

Dynamics Ax 2012 FactBoxes


FactBoxes:

              A FactBox is used to display the data related to the currently selected record in the list page.
  
 There are three types of  Factboxes :

1) InfoPart.
2) FormPart.
3) Cues.

  • InfoPart: 
 It is very simple to create and can display limited number of controls. It has its own data source and can also be displayed in Enterprise Portal.  

  • FormPart:                                         

             It is a link to a Form and can  have the same controls as an standard form .It is displayed in the FactBox Section , So adding too many controls can crowd the form.

  • Cues:

               It is used to display the Count of number of records related to the current record in the list page.
                           
 For Further information you can read from here:
               http://msdn.microsoft.com/en-us/library/gg847986.aspx