Tip for adding an element to an existing Base enum in AX 2012

Witnessed a scenario where an isv solution had modified an existing sys enum to add more values for its use and new elements value  was only increased by +1. This is a bad design practice and can cause issues further down the road when its time for an upgrade and Microsoft adds new elments to that enum so you do not want to be in that situation. Therefore the best practice is to add your element with a value that starts with +100.

So for example i have this ABC enum and its C element’s Enum value is 3:

enums.png

 

If my customization requires me to add values to this I should start at 103:

enums

This will prevent any future upgrade conflicts that can be a nightmare for someone doing an upgrade.

Destructive and Scripted Database Refresh

 

I’m often asked a question by customers on what we mean when saying we need a destructive refresh of the database or a scripted one for that matter. So here is a quick explanation.

 

A destructive refresh is basically make your environment be a copy of Another DB(Master, Prod, etc). In it I would take a backup of for example the Master DB and overwrite the DynamicsAX Trans DB.  Then I’d go in and change the pointers inside AX to point to your server instead of the Master server.

 

A scripted refresh keeps your pointers and some configurations, things like batch jobs and security, document handling and just copies most of the data from Master, going table by table.  Some tables are excluded in the scripted refresh, depending on what we are restoring.

 

Time taken: A destructive refresh will take about an hour to do, while a scripted refresh is 3-4 hours.

 

 

Resolving Visual studio tools 2013 installation error in AX 2012 R3 CU8

When trying to install visual studio tools the following error occurs “This installation package could not be opened. Verify that the package exists and that you can access it” This is mostly caused by VS tools folder missing inside the msi folder of your installation setup. If these folders are there then you might have a different issue. To resolve this for R3 builds follow the following blog by Microsoft support:

https://blogs.msdn.microsoft.com/axsupport/2015/04/21/how-to-slip-stream-ax-2012-r3-cu-8/

After this simply run your installer again and add the visual studio component, worked like a charm for me!

 

Time taken: 40mins

Understanding Inventory Dimensions In Microsoft Dynamics AX 2012

Microsoft Dynamics Ax 2012 gives us the ability to assign a good level of detail to our inventory.

Following are the 9 inventory dimensions that are available in Ax 2012, you can always customize to add more upon your needs :

  1. Size
  2. Color
  3. Configuration
  4. Site
  5. Warehouse
  6. Location
  7. Pallet ID
  8. Serial number
  9. Batch number

To assign these dimensions easily they have been broken down into three dimension groups which can further have the choice of activating/deactivating any particular dimension for that group. The three groups are:

1. Product Dimension group

By default this group contains the following inventory dimensions

  • Size
  • Color
  • Configuration

Style was added to this client to meet their requirements.

2. Storage Dimension group

By default this group contains the following inventory dimensions

  • Site
  • Warehouse
  • Location
  • Pallet ID

3.  Tracking Dimension group

By default this group contains

  • Batch number
  • Serial number

Inventory profile, Owner, GTD number were all added for this client after customization. I have purposely shown you screen shots that have more than just the default inventory dimensions so it can be clear that inventory dimensions can be customized to add more dimensions as needed.

For any questions, feel free to leave me a comment below.