The view details option can be a powerful and useful feature allowing users to quickly jump from one record to the master record. However when this feature is not available it can be frustrating.
Recently I had a client that this was not working for some users for the Item Number field. The problem is user permissions, but what do you need to add to the user’s role to make the view detail work for item numbers.
While testing some system configuration switches I had to re-synchronize the database a number of times. When I first synchronized the system I received the following error:
Failed to create a session; Confirm that the user has the proper privileges to log on to Microsoft Dynamics.
Trying to do an install of SSRS with AX2012 R2 and came across another endpoint issue. Looking at the AIF inbound ports found none of the services would start. Each one would report the following type error:
Object Server 01: System.OperationCanceledException: AIF service group not activated. Service group: BIService. Error: HTTP could not register URL http://+:8101/DynamicsAx/Services/ BIService /. Your process does not have access rights to this namespace (see http://go.microsoft.com/fwlink/?LinkId=70353 for details.
The design of your database, along with your indexes will determine much of the performance limitations of your system. The indexes are how the system will locate information, and if these are well designed can produce considerable performance improvements. This blog will look at the index field order and the system fields, and the effects it can have on your system.
When your current AX4 or AX2009 environment has more than 5 financial dimensions, you need to ensure you setup the AX2012 system so the existing data can map over to the new system.
There are eight extended data types that need to be changed in AX2012 to ensure the field mappings correctly configure to transfer the data between systems as part of an upgrade. These extended data types are: DEL_COSAllowDimensions, Dimension, DimensionAllocation, DimensionCriteria, DimensionKeepFromTransaction, DimensionPriorit, MandatoryDimension and XMLMapDimension.
For each of the extended data types you need to add the necessary Array Elements to ensure they cover the number of financial dimensions contained in the source system. The naming and labeling of the dimensions is not important as these fields are not used with the standard AX 2012 dimension structure, this is just for the purpose of upgrading the data from the earlier versions.
During a recent client upgrade from AX4 to AX2012, had a problem with performance with the upgrade wizard. On the Prepare Application for Preprocessing at the Prepare financial dimension framework step the bottom of the screen, dimension numbers, took 20+ minutes when pressing the upgrade validate button.
The client had 300+ companies, each with many financial dimensions, which resulted in building 180,000+ records in the migration tables. When reviewing the code that builds this information, class LedgerFrameworkSetupHelper, method setupDimensionMergeTable, the records were being read and inserted one at a time, and not using the bulk insert controls. this causes high load on SQL and is also very inefficient.
Changing the code to use the RecordInsertList so records could be bulk inserted, reduced load time by 94% to just over 1 minutes. This means the SQL server was much more efficiently being used, and the time spent waiting for data to be loaded significantly reduced.
So if you are planning to do an upgrade from AX4 to AX2012, and have lots of companies, then consider modify the code to use the bulk insert commands.
Getting the most performance out of SQL server is always important when using DAX. As a result I constantly read the SQL server articles looking to ensure everything has been considered.
SQL server reads and writes its data and log files in 64K blocks, so using a 64K block size for the hard drive format seems to make sense. But what effect will this have?