Dynamics NAVAX

Similar to Set class, Map class allows you to associate one value (the key) with another value. Both the key and value can be any valid X++ type, including objects. The types of the key and the value are specified in the declaration of the map. The way in which maps are implemented means that access to the values is very fast. Below is a sample code that sets and retrieves values from a map. static void checkItemNameAliasDuplicate(Args _args) { inventTable inventTable; Map map; MapEnumerator mapEnumerator; NameAlias nameAlias; int counter = 0; ; map = new Map(Types::String, Types::Integer); //store into map while select inventTable { nameAlias = inventTable.NameAlias; if (!map.exists(nameAlias)) { map.insert(nameAlias, 1); } else { map.insert(nameAlias, map.lookup(nameAlias) + 1); } } //retrieve fro...

Video is from May but it gives you an appreciation of cloud computing and where dynamics products are heading. Launch NAV R2 streamed RTC client on May 19 2010

Microsoft released a troubleshooting document for workflow on customersource/partnersource. How to troubleshoot common workflow issues for Microsoft Dynamics AX 2009 https://mbs.microsoft.com/customersource/documentation/howtodocuments/ax2009_workflow_tips.htm

The Set class is used for the storage and retrieval of data from a collection in which the values of the elements contained are unique and serve as the key values according to which the data is automatically ordered. You can create a set of primitive data types or complex data types such as a Class, Record or Container. Below is sample of a set of records. static void _Set(Args _args) {     CustTable       custTable;     Set             set = new Set(Types::Record);     SetEnumerator   setEnumerator;     ;     while select custTable     {         if (custTable && !set.in(custTable))         {             set.add(custTable);         }     }     if (!set.empty())     {    ...

The workflow history form is designed in a way where if you are a user in the Admin user group, you get view 1. If you are a user that is not in the Admin group, then you get view 2. Workflow history - for admin Workflow history - for non admin Note:  It checks the user by looking for the first usergroup in their list. If there is a user group which sorts higher than "Admin" then it will think you are not an Admin.

Ola Hallengren has updated his site to take care of SQL2008R2. That is some great work he has done. Specially considering he is giving it out for free. http://ola.hallengren.com

The price fields on the purchase requisition are non-editable for catalogue items. It is expected that a trade agreement be created. The price fields are only editable for these conditions: Form is opened view AP -> Periodic -> Purchase Requisition -> All purchase requisition, or Line type is “Non-catalogue item”, or User is task owner. Ie. The task is assigned to the user. In other words he/she maybe the purchaser that gets the price. User is approval owner. Ie. The approval is assigned to the user. In other words he/she maybe the manager that approves the final requisition. For catalogue items on the purchase requisition line can only select between the vendor directly associated with the item and the cheapest vendor as found through the purchase price trade agreements. If another vendor is requested the vendor can be blanked and the user can enter a “Proposed vendor” in the proposed vendor field on the general tab page for the purchase requisition line.   NOTE: ...