http://shekhardiptiman.wordpress.com/2010/01/17/dynamics-ax2009-data-migration-%E2%80%93-import-multiple-addresses-of-vendors-customers-through-excel-template/#comment-148
Thursday 26 July 2012
Sunday 22 July 2012
Security in Ax
Four items control security in Microsoft Dynamics AX 2009:
• License codes include the company's purchased features. These
license codes enable the whole company access to those areas
purchased
• Configuration keys are used to enable or disable features in the
application. These keys control access for the whole company
• Security keys are assigned to user groups and control access to
features within Microsoft Dynamics AX 2009 at a user group level
• Record level security controls access to records in tables. This
means that different user groups can have different access to
different records in the same table
• License codes include the company's purchased features. These
license codes enable the whole company access to those areas
purchased
• Configuration keys are used to enable or disable features in the
application. These keys control access for the whole company
• Security keys are assigned to user groups and control access to
features within Microsoft Dynamics AX 2009 at a user group level
• Record level security controls access to records in tables. This
means that different user groups can have different access to
different records in the same table
Lable Files
Lable Files:
In Ax, it is recommended to use Lables instead of using static text.just because of re-usability and easy to modify when we need.
A label is the text that appears in the user interface. For example, the CustTable has a database field named CustAccount;however, the label in the application is Customer Account. This is done by defining the Label property for the
Extended Data Type That Is Used in the database field. Set the Label property at the Extended Data Type level to make sure it is inherited on all objects where Extended Data Type is used as a source.
When creating a label file, a reference is made to a label data file (.ald) in the file system that stores all the label files numbers and text. The label files are allocated numerically, such as @SYS120 and @SYS121. Label files are stored in the
application folder and use an extension of .ald. The .ald extension is an acronym for Microsoft Dynamics AX 2009 Label Data.
Working with lable file wizard:
This wizard is used to create lable files .To create follow these steps,
1. Navigate to Tools > Development Tools > Label, and select Label file Wizard. This opens the Label File Wizard.
2. Select the Create a new label file ID field. In this case, only create a new label file ID.
3. Create a label file ID named MBS. This is how the system references the new label file. This ID must be unique and contain only three letters.
4. Click Finish. Before writing any newly created label files, shut down Microsoft Dynamics AX 2009 and restart.
Lable File Editor:
Lable File Editor is used to add a new lable or edit already existing lables and also to view available lables .
and to view or edit follow this steps,
1. Type the name of the label in the Find what: field and then click Find now. The system searches all available label names to check if the label exists.If it exists, as long as the label is highlighted, the user can reuse it by selecting Paste label.If the label does not exist, create a new one by pressing CTRL + N.
2. Click the Advanced tab.
When creating a new label, select which label file ID to create the new labels in.
The new label file ID created in the Label file Wizard is available in the drop-down
list.
1. Select one or more languages to view translations of the current label
or create translations of the new label.
2. Select the Auto Search function for the system to automatically start
to search when the label dialog opens.
Assign Labels to Objects:
When a new application object is created, a label must be assigned in the
properties. In some places the feature is called “Label” (for Extended Data
Types), and in other places it is called “Caption” (Design node of forms). Reuse
labels whenever possible by searching for the label, finding it in another label
file, and using it for the object.
In Ax, it is recommended to use Lables instead of using static text.just because of re-usability and easy to modify when we need.
A label is the text that appears in the user interface. For example, the CustTable has a database field named CustAccount;however, the label in the application is Customer Account. This is done by defining the Label property for the
Extended Data Type That Is Used in the database field. Set the Label property at the Extended Data Type level to make sure it is inherited on all objects where Extended Data Type is used as a source.
When creating a label file, a reference is made to a label data file (.ald) in the file system that stores all the label files numbers and text. The label files are allocated numerically, such as @SYS120 and @SYS121. Label files are stored in the
application folder and use an extension of .ald. The .ald extension is an acronym for Microsoft Dynamics AX 2009 Label Data.
This wizard is used to create lable files .To create follow these steps,
1. Navigate to Tools > Development Tools > Label, and select Label file Wizard. This opens the Label File Wizard.
2. Select the Create a new label file ID field. In this case, only create a new label file ID.
3. Create a label file ID named MBS. This is how the system references the new label file. This ID must be unique and contain only three letters.
4. Click Finish. Before writing any newly created label files, shut down Microsoft Dynamics AX 2009 and restart.
Lable File Editor is used to add a new lable or edit already existing lables and also to view available lables .
1. Type the name of the label in the Find what: field and then click Find now. The system searches all available label names to check if the label exists.If it exists, as long as the label is highlighted, the user can reuse it by selecting Paste label.If the label does not exist, create a new one by pressing CTRL + N.
2. Click the Advanced tab.
When creating a new label, select which label file ID to create the new labels in.
The new label file ID created in the Label file Wizard is available in the drop-down
list.
1. Select one or more languages to view translations of the current label
or create translations of the new label.
2. Select the Auto Search function for the system to automatically start
to search when the label dialog opens.
Assign Labels to Objects:
When a new application object is created, a label must be assigned in the
properties. In some places the feature is called “Label” (for Extended Data
Types), and in other places it is called “Caption” (Design node of forms). Reuse
labels whenever possible by searching for the label, finding it in another label
file, and using it for the object.
Data migration and import excel to ax
http://community.dynamics.com/product/ax/axtechnical/b/daxit/archive/2010/01/17/dynamics-ax2009-data-migration-8211-import-multiple-addresses-of-vendors-47-customers-through-excel-template.aspx
Wednesday 11 July 2012
Where do we find this layes in AOT?
To select to view the application object layers for any object in the AOT:
1. Select Tools > Options.
2. On the Development tab click the drop-down box next to the
Application object layer field.
We have different options to select ,those are,
• Show no layers - No objects are labeled with a layer indicator
• Show all layers - All objects are labeled with layer indications for
all layers in which they exist
• Show highest layer - Shows only the highest layer where the object
has been modified
• Show corrected layers - Shows only objects modified in the current
layer or higher and labeled with indication of the highest layer
• Show all from corrected layers - Shows only objects modified in
the current layer or a higher layer, with an indication of all layers of
modification
1. Select Tools > Options.
2. On the Development tab click the drop-down box next to the
Application object layer field.
We have different options to select ,those are,
• Show no layers - No objects are labeled with a layer indicator
• Show all layers - All objects are labeled with layer indications for
all layers in which they exist
• Show highest layer - Shows only the highest layer where the object
has been modified
• Show corrected layers - Shows only objects modified in the current
layer or higher and labeled with indication of the highest layer
• Show all from corrected layers - Shows only objects modified in
the current layer or a higher layer, with an indication of all layers of
modification
Introduction to Ms Dynamics Layered Architecture.
Microsoft Given a seperate architecture which is more flexible to update and customize the application called as layering.In this architecture we find several layers based on their security and functionality.This looks like the following.
The Assumption behind this architecture is to secure the basic application and also the use of This is,
• Any user of the Microsoft Dynamics AX 2009 application can
customize the Microsoft Dynamics AX 2009 application
• The standard application is never overwritten
• Deleting an object removes it either in the current layer or the layer
above if the object exists in a higher layer. Every time an object is
opened, the system automatically searches for and uses the object
files needed in the highest layers first
Each layer is saved in a separate file that has an extension of .aod. For example,
Axsys.aod is the SYS layer. The aod extension is an acronym for Application
Object Data file.
The layers are designed for different Microsoft Dynamics AX 2009 developer
groups. Three groups have an interest in adding or modifying application objects:
• Microsoft Business Solution Developers who create the
standard application
• Business partners and developers who want to enhance Microsoft
Dynamics AX 2009
• Microsoft Dynamics AX 2009 end-users
The Assumption behind this architecture is to secure the basic application and also the use of This is,
• Any user of the Microsoft Dynamics AX 2009 application can
customize the Microsoft Dynamics AX 2009 application
• The standard application is never overwritten
• Deleting an object removes it either in the current layer or the layer
above if the object exists in a higher layer. Every time an object is
opened, the system automatically searches for and uses the object
files needed in the highest layers first
Each layer is saved in a separate file that has an extension of .aod. For example,
Axsys.aod is the SYS layer. The aod extension is an acronym for Application
Object Data file.
The layers are designed for different Microsoft Dynamics AX 2009 developer
groups. Three groups have an interest in adding or modifying application objects:
• Microsoft Business Solution Developers who create the
standard application
• Business partners and developers who want to enhance Microsoft
Dynamics AX 2009
• Microsoft Dynamics AX 2009 end-users
Introduction to AOT(Application Object Tree)
Introduction to AOT(Application Object Tree).
AOT (application object tree) ,is a tree stuctured window ,in which we have entire Ax objects .in
AOT (application object tree) ,is a tree stuctured window ,in which we have entire Ax objects .in
Basic Introdution or Working With Forms.
Creating a record:
Within each module tasks can be performed such as creating new records. For
example, in the Accounts Receivable module customers can be added and sales
orders created.
1. Open the customer form located in the Accounts Receivable module.
(Accounts Receivable/Common Forms/Customer Details)
2. Press CTRL + N to create a new blank row in the customer form.
3. Enter the following data into the fields:
o Customer account: 4099
o Name: Wholesale Foods
o Customer group: 30
The data is automatically saved into the database after moving away from the
new record
Sorting Records:
When working with data in a form it is sometimes necessary to change the sort
order of the data to find specific information more easily. Records can be sorted
in a form using three different methods.
1. Click the header of the sorting column. Records are sorted in
descending order. Clicking the header again sorts in ascending order.
2. Right-click on a field in the column to sort. The shortcut menu
appears with the options to sort in ascending or descending order.
3. Sort records by selecting either Sort Ascending or Sort Descending
from the Edit/Sort menu in the menu bar.
o To remove the sort order, click the Remove
filer icon.
Filtering of Records:
Sorting works well when working on a small set of data. However, to work
efficiently with large amounts of data, filter the data to work with a specific
subset of information.
There are three ways to filter data in the user interface:
• Current content of a field
• Using an inquiry dialog where the criteria for the filter is specified
• Filter by grid
To remove this filter, click the Remove Filter icon on the toolbar.
Finding Records:
Use the Global Search option to search for information across selected tables.
There are three ways to start a Global Search. From the “Menu Pane:”
• Select the ‘Find…’ option on the Edit menu
• Select the Binocular icon from the toolbar
• Press Ctrl + F
Within each module tasks can be performed such as creating new records. For
example, in the Accounts Receivable module customers can be added and sales
orders created.
1. Open the customer form located in the Accounts Receivable module.
(Accounts Receivable/Common Forms/Customer Details)
2. Press CTRL + N to create a new blank row in the customer form.
3. Enter the following data into the fields:
o Customer account: 4099
o Name: Wholesale Foods
o Customer group: 30
The data is automatically saved into the database after moving away from the
new record
Sorting Records:
When working with data in a form it is sometimes necessary to change the sort
order of the data to find specific information more easily. Records can be sorted
in a form using three different methods.
1. Click the header of the sorting column. Records are sorted in
descending order. Clicking the header again sorts in ascending order.
2. Right-click on a field in the column to sort. The shortcut menu
appears with the options to sort in ascending or descending order.
3. Sort records by selecting either Sort Ascending or Sort Descending
from the Edit/Sort menu in the menu bar.
o To remove the sort order, click the Remove
filer icon.
Filtering of Records:
Sorting works well when working on a small set of data. However, to work
efficiently with large amounts of data, filter the data to work with a specific
subset of information.
There are three ways to filter data in the user interface:
• Current content of a field
• Using an inquiry dialog where the criteria for the filter is specified
• Filter by grid
To remove this filter, click the Remove Filter icon on the toolbar.
Finding Records:
Use the Global Search option to search for information across selected tables.
There are three ways to start a Global Search. From the “Menu Pane:”
• Select the ‘Find…’ option on the Edit menu
• Select the Binocular icon from the toolbar
Basic Navigation
Basic Navigation includes 1)navigation pane and 2)area pane
When first opening Microsoft Dynamics AX 2009, the Navigation Pane appears.
This menu contains all the purchased modules in the license code. From here, the
user can browse to any module in Microsoft Dynamics AX 2009.
Area Page:
An Area Page is a Microsoft Dynamics AX 2009 navigation page that displays
menu items that link to list pages, content pages, forms, reports, classes, jobs, and
queries. To view an area page, click a module button in the Navigation Pane. The
area page opens in the client content pane that is automatically generated using
the menu information for that module.
When first opening Microsoft Dynamics AX 2009, the Navigation Pane appears.
This menu contains all the purchased modules in the license code. From here, the
user can browse to any module in Microsoft Dynamics AX 2009.
Area Page:
An Area Page is a Microsoft Dynamics AX 2009 navigation page that displays
menu items that link to list pages, content pages, forms, reports, classes, jobs, and
queries. To view an area page, click a module button in the Navigation Pane. The
area page opens in the client content pane that is automatically generated using
the menu information for that module.
MorphX
The MorphX Development Suite is the integrated development environment
(IDE) in Microsoft Dynamics AX 2009 used to develop and customize both the
Windows interface and the Web interface. An IDE integrates development
functions such as designing, editing, compiling, and debugging within a common
environment.
With MorphX, common operations such as building or modifying forms, menus,
and reports are done using drag-and-drop techniques with little or no coding.
(IDE) in Microsoft Dynamics AX 2009 used to develop and customize both the
Windows interface and the Web interface. An IDE integrates development
functions such as designing, editing, compiling, and debugging within a common
environment.
With MorphX, common operations such as building or modifying forms, menus,
and reports are done using drag-and-drop techniques with little or no coding.
IntelliMorph
IntelliMorph is the technology that controls the user interface in Microsoft
Dynamics AX 2009. The user interface is how the functionality of the application
is presented or displayed to the user. The same functionality can be displayed on
multiple platforms or devices that use the same application code; for example,
through the Web or through Mobile devices.
IntelliMorph controls the layout of the user interface and makes it easier to
modify forms, reports, and menus.
Dynamics AX 2009. The user interface is how the functionality of the application
is presented or displayed to the user. The same functionality can be displayed on
multiple platforms or devices that use the same application code; for example,
through the Web or through Mobile devices.
IntelliMorph controls the layout of the user interface and makes it easier to
modify forms, reports, and menus.
Application Object Tree (AOT)
The Application Object Tree (AOT) is a tree view of all the application objects
within Microsoft Dynamics AX 2009. The AOT contains everything needed to
customize the look and functionality of a Microsoft Dynamics AX 2009
application.
within Microsoft Dynamics AX 2009. The AOT contains everything needed to
customize the look and functionality of a Microsoft Dynamics AX 2009
application.
Tuesday 10 July 2012
What are the methods which gets affect when posting a Sales order or Purchase order?
What are the methods which gets affect when posting a Sales order and Purchase order?
Ans:
Whether It is PO or SO first the FormLetter class will be called and then based on whehter it is a PO or SO
the PurchFormLetter and SalesFormLetter Classes will be called. and then based on the stage of posting it will call different classes.
Eg: If you are positng a PO invoice PurchFormLetter_invoice class will be called.
If you wan to know the what are all the different classes and methods that are called during SO/PO posting - put a break point in FormLetter - new method
cust, cust,vendinvoicejour has some initfromsalestable method.the form letter class call this method and it will insert the header level records(sales table) to cust invoice jour and footer level(saless line) records to cust invoice trans(here it will call initfromsalesline)
and
Ans:
Whether It is PO or SO first the FormLetter class will be called and then based on whehter it is a PO or SO
the PurchFormLetter and SalesFormLetter Classes will be called. and then based on the stage of posting it will call different classes.
Eg: If you are positng a PO invoice PurchFormLetter_invoice class will be called.
If you wan to know the what are all the different classes and methods that are called during SO/PO posting - put a break point in FormLetter - new method
cust, cust,vendinvoicejour has some initfromsalestable method.the form letter class call this method and it will insert the header level records(sales table) to cust invoice jour and footer level(saless line) records to cust invoice trans(here it will call initfromsalesline)
and
Subscribe to:
Posts (Atom)