Skip to main content

Dynamics AX 2012 and Esri’s ArcGIS (Mapping)

Original post:

We have been busy recently, working on developing a GIS solution for Microsoft Dynamics AX 2012.

Esri’s ArcGIS is a geographical information system (GIS) solution for working with maps and geographical information. It is used for creating custom maps for viewing, editing, querying. For example, your local town or city will have a GIS solution that shows your housing plan, where the gas pipes are, where you water mains are, the roads, the traffic lights etc. The list is endless. A mining company may have a GIS solution to show where their Assets are, drawings of the mine site, their plant etc.

ArcGIS maps work as layers; you have your base layer which is a street map in my example below. Then you have feature layers, below I have an incidents feature layer showing where incidents have been reported, then a third feature layer plotting where the assets are.


I am not going to give away too much today. Convergence is just around the corner. My team will be at convergence at booth 2242 and also running a session. Below is some detail on what we are going to present.

SSAX009: Daxeam presents: Implement your equipment maintenance strategy with Microsoft Dynamics AX

Wednesday, March 5th from 12:30 pm - 1:30 pm    Room: A307

Speaker(s): Alan Flanders

Join us to see how implementing Daxeam for Microsoft Dynamics AX will improve the effectiveness of your maintenance department within an asset intensive organization. Learn how shifting from reactive maintenance to a reliability centered approach will reduce unplanned downtime and costs, minimize risks, manage inventory levels, and create more predictability within your maintenance department; and, explore how GIS integration can help implement a strategy to maintain assets spread out over large areas.

300 - Experienced

Audience: Business Decision Maker, End User, Power User, Prospect, Technical Decision Maker

Product: Microsoft Dynamics AX

Key Learning 1: Realize the benefits of GIS (mapping) integration

Key Learning 2: Learn more about maintenance strategies and approaches

Key Learning 3: Explore RCM - Reliability Centered Maintenance

Popular posts from this blog

AX - How to use Map and MapEnumerator

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

AX - How to use Set and SetEnumerator

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.add(custTable);         }     }     if (!set.empty())     {         setEnumerator = set.getEnumerator();         setEnumerator.reset();         while (setEnumerator.moveNext())         {             custTable = setEnumerator.current();             info(strfmt("Customer: %1",custTable.AccountNum));         }     } } Common mistake when creating a set of recIds

Import document handling (attachment) files #MSDyn365FO

Out of the box you have limited data entities for migrating attachments. If you search what is already in the AOT, you will see a few various examples. I suggest you look at the LedgerJournalAttachmentsEntity as it is the simplest and cleans to copy from. I wont go into detail but I will give a quick run down of what it looks like. Use the DocuRefEntity as your main datasource. It does most of the work for you. Set your table you want to import for as the child datasource Add the Key You will need to add the postLoad method. There is minor code to update the virtual field FileContents. Below is an export I did for the general journal attachments. The import zip structure should be the same way. It will create the usual artifacts such as the excel, manifest and package header xml files. You will see a Resources folder under that. If you drill down to the resources you will see the attachments. This is an export and it used the document GUID for uniqueness. The other thing is the extensi