Skip to main content

Posts

Showing posts from February, 2014

Dynamics AX 2012 and Esri’s ArcGIS (Mapping)

Original post: http://daxeamproduct.blogspot.com/2014/02/dynamics-ax-2012-and-esris-arcgis.html 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

User security role assignment report [AX 2012]

There isn’t a report that lists the users and their security roles. You can get this information fairly quickly through Excel add-in. 1. Go to the AOT and find the Query SysSecRolesForUser. 2. Duplicate it and remove the code (it has code in the init method to filter by current user). Then just go the organization > “Document data sources”. Select your query and activate it. 3. In Excel select the service, select the fields and run. You should see a nice list of user and their roles.

The given value of type String from the data source cannot be converted to type nvarchar of the specified target column.

If you are upgrading to a later cumulative update and try to import a model you may get this error if you haven’t followed the steps. You have to run the powershell command before you start the imports. This updates the model store schema to accept new models. Initialize-AXModelStore I wanted to find out what was changed in SQL. So, I ran an SQL trace to see which table caused the problem. Then I found that the ModifiedBy and CreatedBy fields where extended from 5 characters to 8 characters. Before (CU6) After (CU7)