Monday 31 December 2012

Microsoft Dynamics AX 2012 - Data Integrity

There are a number of concepts and features to consider when adding, modifying, or deleting data to ensure that the integrity and consistency of the data is maintained. These include:
  •     Using table DeleteAction elements.
  •     Using the forUpdate keyword correctly in select statements.
  •     Enabling transactions in your code.
  •     Avoiding deadlocks.
  •     Implementing Optimistic Concurrency Control (OCC).

My above blog is based on Microsoft's Official information.
 
I hope this blog about 'Microsoft Dynamics AX 2012 - Data Integrity' was informative. Please feel free to leave your comments.

Microsoft Dynamics AX 2012 - Tables, Views, and Maps

Tables, views, and maps are elements that X++ SQL statements can reference to read and write business data. These elements are specified in the Application Object Tree (AOT) under AOT > Data Dictionary.

The following describes these elements.
  • AOT element: Tables
Description: Tables store business data. Each table in the AOT has a corresponding table in the underlying Microsoft SQL Server database.
In Microsoft Dynamics AX, tables have advanced features beyond what tables might have in the underlying database. The advanced features include the following:
  1. Method members - A table can have methods, just as a class in X++ or C# can have methods.
  2. Table inheritance - A table can extend, or be derived from another table. That same table can be the base table for several derived tables.
  3. Valid time state - A table can be configured to track data relationships for specific date-time spans.
Tables are specified at AOT > Data Dictionary > Tables.
  • AOT element: Views
Description: A view is an X++ SQL select statement that is given a name that is reusable in other X++ SQL statements. The select statement of the view can reference one table, or it can join tables. Also, a view can reference other views, or a mix of views and tables. A view can also reference maps.

Developers are encouraged to consider using an AOT query element as the source of data for their view.

Views are specified at AOT > Data Dictionary > Views.
  • AOT element: Maps
Description: A map can unify the access to similar columns and methods that are present in multiple tables. You associate a map field with a field in one or more tables. This enables you to use the same field name to access fields with different names in different tables. Methods on maps enable you to create or modify methods that act on the table fields that the map references.

Maps are specified at AOT > Data Dictionary > Maps.
A query can use tables, views, or maps for its data sources. Queries are specified at AOT > Queries.

My above blog is based on Microsoft's Official information.
 
I hope this blog about 'Microsoft Dynamics AX 2012 - Tables, Views, and Maps' was informative. Please feel free to leave your comments.

Microsoft Dynamics AX 2012 - Types of Reports

The following describes the types of reports that you can create by using the reporting and analytical features of Microsoft Dynamics AX 2012.

Category:  Transactional reports

 

Transactional reports retrieve data from the transaction processing database for Microsoft Dynamics AX.

  • Tool that is used to create the report: Visual Studio 
Format of the report: Reporting Services report 
Type of user who typically creates this kind of report: Developer
  • Tool that is used to create the report:  Microsoft Dynamics AX list page
Format of the report: Excel worksheet
Type of user who typically creates this kind of report: System administrator, Application user
  • Tool that is used to create the report:  Microsoft Dynamics AX auto-report wizard
Format of the report: Reporting Services report
Type of user who typically creates this kind of report: System administrator, Application user
  • Tool that is used to create the report:  Microsoft Dynamics AX add-in for Excel
Format of the report: Excel worksheet
Type of user who typically creates this kind of report: System administrator, Application user
  • Tool that is used to create the report:  Management Reporter for Microsoft Dynamics ERP
Format of the report: Management Reporter report
Type of user who typically creates this kind of report: System administrator, Application user

Category:  Analytical reports

 

Analytical reports retrieve data from Microsoft SQL Server Analysis Services cubes.

  • Tool that is used to create the report:  Visual Studio
Format of the report: Reporting Services report
Type of user who typically creates this kind of report: Developer
  • Tool that is used to create the report:  SQL Server Business Intelligence Development Studio or SQL Server Data Tools
Format of the report: Key performance indicator (KPI)
Type of user who typically creates this kind of report: Developer
  • Tool that is used to create the report:  SQL Server Report Builder
Format of the report: Reporting Services report
Type of user who typically creates this kind of report: Developer, System administrator
  • Tool that is used to create the report:  Excel
Format of the report: Excel worksheet
Type of user who typically creates this kind of report: System administrator, Application user

My above blog is based on Microsoft's Official information.
 
I hope this blog about 'Microsoft Dynamics AX 2012 - Types of Reports' was informative. Please feel free to leave your comments.