Microsoft Dynamics Axapta 2012

AX 2012 SSRS - Unable to find appropriate service endpoint information in the configuration object

2016-01-02T14:44:00.000+05:30

AX 2012 – Reporting Services Extensions rollback - Unable to find appropriate service endpoint information in the configuration object

When I am trying to install the Dynamics AX Reporting Services Extension on the SQL server reporting server, installation is getting rollback due to the error. I continuously found following error message in log files.

Error: Unable to find appropriate service endpoint information in the configuration object.

Solution:

SQL Server reporting services communicate with dynamics AX through WCF Services. When I open the application integration framework in Dynamics AX -> System Administrator -> Setup -> Service and Application integration framework -> inbound ports ->BIservices are deactivated. So, I have followed the following steps to resolve it.

Activated the BIServices as shown in the below below mentioned screenshot.

Then, Open the AX Client Configuration in the Reporting services server and Refresh the business connector configuration.

That’s It!!!

AX 2012 - A call to the Microsoft Dynamics AX SRSFramework Service failed.

2016-01-02T13:08:00.000+05:30

SSRS Report Deployment in AX 2012 - A call to the Microsoft Dynamics AX SRSFramework Service failed.

When i was working on my AX 2012 production server configuration and try to publish the reports using the Microsoft Dynamics AX 2012 Management Shell using the following command

Publish-AXReport -ReportName *

Publishing the reports are failed and following error was thrown.

"A call to the Microsoft Dynamics AX SRSFramework Service service failed."

Solution:

To resolve the issue, perform the following steps

Stop the AOS Services(dynamics AX application service) in Application Server and Reporting server services in DB Server or separate reporting server.
Go to the Following path: C:/Users/UserName/AppData/Local
Take the Backup all AUC extension files from the local folder and delete these files from Local folder

4. Start the Reporting Server services and AOS Services

5. Now try to deploy the reports from powershell

Thats it!! now you can deploy the reports successfully...

AX 2012 Retail - Schedule and Automate backups of SQL Server databases in SQL Server Express

2015-12-26T20:02:00.000+05:30

Schedule and Automate backups of SQL Server databases in SQL Server Express

Dynamics AX Retail POS mostly uses SQL Server express per store database. SQL Express version is attractive because it provides a lot of value and free. This is especially true for retailers that have many stores as the cost of database software licensing would quickly become cost prohibitive. The use of SQL Express requires careful planning and consideration for ongoing maintenance and an understanding of how the database will grow.

SQL Server Express editions do not offer a way to schedule either jobs or maintenance plans because the SQL Server Agent component is not included in these editions. Therefore, you have to take a different approach to back up your databases when you use these editions.

This article describes how to use a Transact-SQL script together with Windows Task Scheduler to automate backups of SQL Server Express databases on a scheduled basis

Follow these 3 steps to back up your SQL Server databases by using Windows Task Scheduler:

Step 1:

Use SQL Server Management Studio Express to create the following stored procedure in master database:

USE [master]

SET ANSI_NULLS ON

SET QUOTED_IDENTIFIER ON

-- =============================================

-- Author: Microsoft

-- Description: Backup Databases for SQLExpress

-- Parameter1: databaseName

-- Parameter2: backupType F=full, D=differential, L=log

-- Parameter3: backup file location

-- =============================================

Create PROCEDURE [dbo].[sp_BackupDatabases]

@databaseName sysname = null,

@backupType CHAR(1),

@backupLocation nvarchar(200)

SET NOCOUNT ON;

DECLARE @DBs TABLE

(

ID int IDENTITY PRIMARY KEY,

DBNAME nvarchar(500)

)

-- Pick out only databases which are online in case ALL databases are chosen to be backed up

-- If specific database is chosen to be backed up only pick that out from @DBs

INSERT INTO @DBs (DBNAME)

SELECT Name FROM master.sys.databases

where state=0

AND name=@DatabaseName

OR @DatabaseName IS NULL

ORDER BY Name

-- Filter out databases which do not need to backed up

IF @backupType='F'

BEGIN

DELETE @DBs where DBNAME IN ('tempdb','ReportServer','ReportServerTempDB','master', 'model','msdb')

END

ELSE IF @backupType='D'

BEGIN

DELETE @DBs where DBNAME IN ('tempdb','ReportServer','ReportServerTempDB', 'master', 'model','msdb')

END

ELSE IF @backupType='L'

BEGIN

DELETE @DBs where DBNAME IN ('tempdb','ReportServer','ReportServerTempDB', 'master', 'model','msdb')

END

ELSE

BEGIN

RETURN

END

-- Declare variables

DECLARE @BackupName varchar(100)

DECLARE @BackupFile varchar(100)

DECLARE @DBNAME varchar(300)

DECLARE @sqlCommand NVARCHAR(1000)

DECLARE @dateTime NVARCHAR(20)

DECLARE @Loop int

-- Loop through the databases one by one

SELECT @Loop = min(ID) FROM @DBs

WHILE @Loop IS NOT NULL

BEGIN

-- Database Names have to be in [dbname] format since some have - or _ in their name

SET @DBNAME = '['+(SELECT DBNAME FROM @DBs WHERE ID = @Loop)+']'

-- Set the current date and time n yyyyhhmmss format

SET @dateTime = REPLACE(CONVERT(VARCHAR, GETDATE(),101),'/','') + '_' + REPLACE(CONVERT(VARCHAR, GETDATE(),108),':','')

-- Create backup filename in path\filename.extension format for full,diff and log backups

IF @backupType = 'F'

SET @BackupFile = @backupLocation+REPLACE(REPLACE(@DBNAME, '[',''),']','')+ '_FULL_'+ @dateTime+ '.BAK'

ELSE IF @backupType = 'D'

SET @BackupFile = @backupLocation+REPLACE(REPLACE(@DBNAME, '[',''),']','')+ '_DIFF_'+ @dateTime+ '.BAK'

ELSE IF @backupType = 'L'

SET @BackupFile = @backupLocation+REPLACE(REPLACE(@DBNAME, '[',''),']','')+ '_LOG_'+ @dateTime+ '.TRN'

-- Provide the backup a name for storing in the media

IF @backupType = 'F'

SET @BackupName = REPLACE(REPLACE(@DBNAME,'[',''),']','') +' full backup for '+ @dateTime

IF @backupType = 'D'

SET @BackupName = REPLACE(REPLACE(@DBNAME,'[',''),']','') +' differential backup for '+ @dateTime

IF @backupType = 'L'

SET @BackupName = REPLACE(REPLACE(@DBNAME,'[',''),']','') +' log backup for '+ @dateTime

-- Generate the dynamic SQL command to be executed

IF @backupType = 'F'

BEGIN

SET @sqlCommand = 'BACKUP DATABASE ' +@DBNAME+ ' TO DISK = '''+@BackupFile+ ''' WITH INIT, NAME= ''' +@BackupName+''', NOSKIP, NOFORMAT'

END

IF @backupType = 'D'

BEGIN

SET @sqlCommand = 'BACKUP DATABASE ' +@DBNAME+ ' TO DISK = '''+@BackupFile+ ''' WITH DIFFERENTIAL, INIT, NAME= ''' +@BackupName+''', NOSKIP, NOFORMAT'

END

IF @backupType = 'L'

BEGIN

SET @sqlCommand = 'BACKUP LOG ' +@DBNAME+ ' TO DISK = '''+@BackupFile+ ''' WITH INIT, NAME= ''' +@BackupName+''', NOSKIP, NOFORMAT'

END

-- Execute the generated SQL command

EXEC(@sqlCommand)

-- Goto the next database

SELECT @Loop = min(ID) FROM @DBs where ID>@Loop

END

Step 2:

In a notepad, write the batch file code depending upon your scenario. The SQL ID used for backup should have at least the Backup Operator role in SQL Server.

Example: Full backups of all databases in the local named instance of SQLEXPRESS by using Windows Authentication

//File Name: Sqlbackup.bat

//@backupType = 'F' : F means Full Backup

//If your instance is SQLEXPRESS use \SQLEXPRESS. If it is defaulut mention \ only

sqlcmd -S .\SQLEXPRESS -E -Q "EXEC sp_BackupDatabases @backupLocation='D:\SQLBackups\', @databaseName=’YOURDB’, @backupType='F'"

Similarly, you can make a differential backup of YOURDB by pasting in 'D' for the @backupType parameter and a log backup of YOURDB by pasting in 'L' for the @backupType parameter.

Step 3:

Schedule a job by using Windows Task Scheduler to Run the batch file that we created earlier in step 2. To do this, follow these steps:

1. On the computer that is running SQL Server Express, click Start, Serach for Task Scheduler, and then click Task Scheduler.

In the Task Scheduler click Create Task.

2. In General Tab, Type SQLBACKUP for the name of the task, Run whether user is logged in or not option.

3. In Trigger Tab then Click New, click Daily and Specify information for a schedule to run the task. (As recommend that you run this task at least one time every day.) Then slect enabled option, and then click Ok.

4. In Action Tab then click New, Click Browse, click the batch file that you created in step 2, and then click Ok.

5. Run the scheduled task at least one time to make sure that the backup is created successfully.

That's It!!!!

Make sure that there should be space on the drive to which the backups are being taken.

Source: Microsoft

What’s New in CU 10 for Microsoft Dynamics AX 2012 R3

2015-12-14T14:52:00.000+05:30

What’s New in CU 10 for Microsoft Dynamics AX 2012 R3

This Article describes new or changed functionality, and updates, that were included in AX 2012 R3 cumulative update 10. Most changes were made in the Warehouse management, Transportation management, and Retail areas of Dynamics AX.

Warehouse management enhancements

Improvements to replenishment

Wave demand replenishment now recognizes existing min/max replenishment work as supply when evaluating if it should create new replenishment work. Cancelling wave based replenishment work will now unblock sales order work automatically. Demand replenishment will now consider all lines in the replenishment template even with different directive codes in situations where the entire demand quantity is not assigned to a put location. The directive code on work templates with the work order type Replenishment is now editable.

Improvements when viewing inventory on hand

A new field called Available physical on exact dimensions has been added to the On hand by location form. This field shows the available physical quantity for all the dimensions displayed on the screen. There have been performance improvements to the on hand stored procedure to use better query plans and make sure it is only called when necessary. A new clean up job has been added under Inventory management > Periodic > Clean up > Warehouse management on-hand entries cleanup. This job will delete records in the InventSum and WHSInventReserve tables for closed on-hand entries.

Enhanced serial number functionalities

Items with a tracking dimension using serial numbers in the sales process can now be used with warehouse management processes. It is now possible to validate sales serials using the mobile device as well as the ability to indicate unreadable serial numbers. You can also enter sales serial numbers using the pack station and for sales order returns. Additionally, you can open the form that shows the recorded serial numbers from the Load lines tab on the Load details form. It is also possible to register serial numbers from the Picking list registration form, which will open the form for capturing sales serial numbers related to the sales line
In the manufacturing process, when consuming serialized components, it is now possible to postpone the registration of the serial number until production consumption. This will save time in warehouse processes as the serial will not be needed to be registered during receiving of serialized components.

Improvements to inbound processes

The behavior of the mobile device menu item with the work creation process set to License plate receiving has changed. It will now only register the arrival of a purchase order and create put away work. It will leave the created work in an open state. If you want to use the old process, where the put away work was also conducted at that point in time, use a mobile device menu item with work creation process set to License plate receiving and put away. During the process of put away work using the mobile device, we have added several new options for exception handling for the warehouse worker. Three new buttons have been introduced during put away work; Split put, Override LP and Skip. They can be used to split items to multiple locations, consolidate items on a license plate at a location, or skip the current work line and proceed to the next put away line. Additionally, the Cancel button will now be available in all put away screens.
During purchase receiving using the mobile device, the unit of measure will be defaulted to the UOM setup on the GTIN number. When using the Delivery schedule form on a purchase order line to split the delivery of a purchase order to different days, the load lines will also be updated. Performance when registering product receipt and querying for a put away location has been improved when using Volumetric and Stocking limits constraints for locations. Now the amount of full locations in the query should not affect performance.

Improvements to outbound processes

Over picking using the mobile device has been enabled during sales and transfer order picking work. Over picking will only be possible if there is enough inventory available at the current pick location and if it is not already allocated to other work. To enable over picking, both the work user and the mobile device must be set up to allow over picking.
During picking on the mobile device, you can now use the Full button any time during picking to indicate that you cannot pick any more lines. It is now possible to block release to warehouse and creation of work for sales orders that exceeds customers credit limit. Performance of closing of containers during pack operations have been improved by avoiding some client/server calls. Performance when having containerization as part of wave posting been improved and optimized when scaling number of sales lines per order

Improvements to work templates

A new section of parameters has been added to the Work template form called Work header maximums. They can be used to split a work header when the sum of work lines exceeds the quantity specified.

Integration to project and Integration to manufacturing

Transportation management enhancements

Create scheduled routes

Scheduled routes can now be generated from a route plan, where the segments of the scheduled route correspond to the hub configuration associated with the route plan. A batch job is used to create the scheduled routes depending on date range, particular days of the week and a load template. The scheduled routes can be used with Load building workbench in order to create optimal loads for the routes.

Improvements to auto-release to warehouse process

hen using the auto-release to warehouse process it is now possible to consolidate multiple transfer orders based on To warehouse and From warehouse into the same shipment.

Integration to project

Retail enhancements

Global refund tab on the Register form and the “Global refund check” report on the Retail store transactions and Online store transactions forms have been removed.
Variant specific sales price is shown when a product variant is selected during product search or inventory lookup in POS. Previously the product base price was shown.
This enhancement lets user select Infocode groups in open drawer store operation under AX functionality profile
Retail POS SDK now allows for customization of the item types that are allowed for return.
If the primary address on customer is marked as private address, the sales order created for a customer with this private address cannot be picked up at the retail store.
Print Gift Receipts in Modern point of sale (MPOS): Added gift receipt feature at MPOS for:

Sales Transactions
Show journal, both Gift receipt preview and print

The changes in the hotfix enable look up of another store's customers using real-time service.
Introduced alternative algorithm for calculating discounts, which is enforced if predefined max number of calculations steps/loops is exceeded. In this case, point of sale will switch to the marginal value algorithm, which does not guarantee the best discount but provides much better performance characteristics. This feature is configurable in Retail Parameters
Enable Extended Login registration in MPOS, This operation provides an interface that you can use to enroll or remove workers in extended logon using peripherals. Supported peripherals include barcode scanners and magnetic strip readers
Retail MPOS installation was not supported on the Windows 10 Long Term Service Branch. With this hotfix we have added this support extending the supported operating systems for MPOS to the following:

Windows 8.1 Update 1- Server 2012 R2 Update 1
Windows 10- Windows 10 Long Term Service Branch

Source: https://mbs.microsoft.com/files/public/CS/AX2012R3/WhatsNew_MicrosoftDynamicsAX2012-R3-CU10.pdf

SSRS Deployment Failed - The "DeployToReportsServerTask" task failed unexpectedly

2015-12-04T19:03:00.000+05:30

Error # 1:

The "DeployToReportsServerTask" task failed unexpectedly.
System.IO.FileLoadException: Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401)
at Microsoft.Dynamics.Framework.Deployment.Reports.DeployToReportsServerTask.Deploy(IEnumerable`1 transitiveReferenceClosure, DeploymentLogger logger, Boolean restartReportServer)
at Microsoft.Dynamics.Framework.Deployment.Reports.DomainBoundHelper.Deploy(IEnumerable`1 transitiveReferenceClosure, DeploymentLogger logger, Boolean restartReportServer)
at Microsoft.Dynamics.Framework.Deployment.Reports.DomainBoundHelper.Deploy(IEnumerable`1 transitiveReferenceClosure, DeploymentLogger logger, Boolean restartReportServer)
at Microsoft.Dynamics.Framework.Deployment.Reports.DeployToReportsServerTask.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext() C:\Program Files (x86)\MSBuild\Microsoft\DynamicsTools\Microsoft.Dynamics.Framework.Design.Reporting.Modeling.targets 466 6 VendorDetailsReport

Error # 2: An error occurred : Access is denied.

If User Account Control (UAC) is enabled on the machine, close the application, right-click the application, and then click Run as administrator. C:\Program Files (x86)\MSBuild\Microsoft\DynamicsTools\Microsoft.Dynamics.Framework.Design.Reporting.Modeling.targets 466 6 VendorDetailsReport

Error # 3: The deployment was aborted. You do not have privileges to deploy to server: SINGU-VIRTUAL. For deployment, you must have administrative rights to the SQL Server Reporting Services (SSRS) server. Contact your administrator to deploy. C:\Program Files (x86)\MSBuild\Microsoft\DynamicsTools\Microsoft.Dynamics.Framework.Design.Reporting.Modeling.targets 466 6 VendorDetailsReport

Solution:

Open Visual Studio with "Run As Administrator" and open the project. Try to re-deploy the solution again

Microsoft Dynamics AX Named User License Count - AX 2012

2015-04-12T13:54:00.000+05:30

If you want to compare the data, Based on your license purchase history with Dynamics AX user number, There is a report under System admiration > Reports > Licensing > Named User License Counts. This report contains information about the users who are assigned to security roles in Microsoft Dynamics AX. The report analyzes the roles and privileges that are assigned to each user and then calculates the number of licenses that are required for each user type.

Please follow the attached steps to Check/Count Named User in Dynamics AX 2012.

1. Go to the System Administration >> Setup >> System >> Server Configuration and Enable the Batch Server or define your Batch Server and enable it in case you have more than one AOS and you dedicate one of them as a Batch Server.

2. Define the Batch Group from System Administration >> Setup and Make Sure Batch Server is Running.

3. Click on Batch Jobs from System Administration >> Inquiries and Make Sure that the Batch Job “Named User Count” is available

4. If not, add the below job and then run it create the batch job.

static void LicenseMinerCreateBatchJob(Args _args)
{
SysUserLicenseMiner::createBatchJob();
}

5. Click on the Batch Task and Make Sure that the Batch Job is assigned to the Batch group you had enabled it in Step 1 and Click on the recurrence of batch job and configure it weekly or monthly once.

6. Then Run the Report under System Administration >> Reports >> Named User License Count

AX 2012 Performance - Configure SQL Server and Storage

2014-03-28T22:24:00.000+05:30

This Article provides information about how to configure database and windows server for Microsoft Dynamics AX. To achieve optimal Microsoft Dynamics AX performance, we must correctly configure the database infrastructure.

You must have knowledge in following areas:

· Windows Server administration.

· SQL Server administration. Specific areas of knowledge include advanced configuration options, memory management, performance management, and troubleshooting.

· Microsoft Dynamics AX system administration.

Recommendation on Tune DB operations:

#	Recommendation	Reference
1	Enabling trace flags 4136 ,1117 and 4199 on SQL server.	T-4136 : Disable parameter sniffing T-4199 : Activate query optimizer fixes T-1117 : DB files growth
2	Disabling index hints from AX configuration and thereby allowing SQL to decide the best way to process the query.	Best Practice
3	Making sure that entire table cache is not enabled for tables which get frequently updated.	Best Practice
4	SQL Server service account is not granted SE_MANAGE_VOLUME_NAME right	Best Practice - Space created by Delete to used
5	Reducing the MAXDOP setting to 1 and test it.	Best Practice
6	Change Minimum SQL to 0 to 60 GB	Best Practice
7	Making sure no of tempDB files = No of logical processors. It must be 24 data files	MS Best practice : ensuring Temp files used by DB for temp table operations

Recommendation on I/O Storage and Physical Structure tuning:

#	Recommendation	Reference
1	DB File Growth is having auto-growth setting to trend of increase in size and It recommended to set to 10%	Best Practice
2	Making sure we have primary key/clustered index on each table in AOT for enabling record caching.	Best practice : Ensuring table scans are avoided

IOPS for AX 2012:

Benchmark reports of Microsoft, which the performance study done in AX 2012 with SQL 2008 R2. Based on the report I have attached the snapshot of IOPS and CPU utilization.
The below study is done for 5000 users. I also attached the detailed report which has transaction details, hardware details and system configuration.

You can also see the same report from the below link,

http://technet.microsoft.com/en-us/library/hh536205.aspx

Recommendation on Platform related Tuning:

#	Recommendation	Reference
1	Disable 'Power Saving' setting on DB server and change to 'High Performance’. Taking reference from MS on performance improvement , power saving will reduce sql performance by 50%	Best Practice MS Support http://support.microsoft.com/kb/2207548
2	Exemption of AOS processes from real time antivirus scanning 1) AX32.exe 2) AX32serv.exe All the application folders	Best Practice
3	Disable Scalable Networking Pack on Application Servers
4	Install MS latest hot fixes on Applications servers to update Processor Driver.
5	Disable Debug Settings	Best Practice
6	Disabling Error Reporting in AOS servers	Best Practice

Minimal SQL Server infrastructure

The configuration of Windows Server and SQL Server greatly affects the performance of the Microsoft Dynamics AX database. This below recommendations for the configuration of Windows Server and SQL Server.

The configuration recommendations are based on the following assumptions:

· You are using a dedicated server that runs SQL Server.

· You are using a single instance of SQL Server that is dedicated to running the Microsoft Dynamics AX production database.

· MS recommend that you store your test and development databases on a separate server from the production database.

Configuring the Microsoft Dynamics AX database

Microsoft recommend the following settings for the Microsoft Dynamics AX database. we can use SQL Server Management Studio or the appropriate ALTER DATABASE statement to configure these settings.

· Set COMPATIBILITY_LEVEL to 100.

· Set READ_COMMITTED_SNAPSHOT to on. Performance testing has shown that Microsoft Dynamics AX performs better when the READ_COMMITTED_SNAPSHOT isolation option is set to on.

· Set AUTO_CREATE_STATISTICS and AUTO_UPDATE_STATISTICS to on. Set AUTO_UPDATE_STATISTICS_ASYNC to off. Performance testing has shown that Microsoft Dynamics AX performs better when the options have these settings.

· Make sure that the AUTO_SHRINK option is set to off. When database files are automatically shrunk, performance of the database degrades.

Configuring the server that runs SQL Server

For SQL Server, we recommend the following configuration settings for the SQL Server service.

· Run the SQL Server service under an Active Directory domain account that has the minimum necessary privileges.

· Confirm that the account for the SQL Server service has been granted the Lock pages in memory privilege.

· Configure the account for the SQL Server service for instant file initialization. Instant file initialization is only available if the account for the SQL Server service, MSSQLSERVER, has been granted the SE_MANAGE_VOLUME_NAME right. Members of the Windows Administrator group have this right and can grant it to other users by adding them to the Perform Volume Maintenance Tasks security policy.

· Enable the TCP/IP network protocol. Depending on the edition of SQL Server that you use, this protocol may be automatically installed during installation. For instructions,

Disable hyperthreading. This step must be performed in the BIOS settings of the server. For instructions, see the hardware documentation for your server.

Configuring the instance of SQL Server

Configuring max degree of parallelism

The max degree of parallelism option is a setting that affects the entire instance of SQL Server. Microsoft Dynamics AX workloads generally perform better when intra-query parallelism is disabled. However, the upgrade process benefits from parallelism, as do activities that are used exclusively for batch jobs or maintenance. Use the following settings when the system performs maintenance activities or an upgrade:

· Before an upgrade to a new release of Microsoft Dynamics AX, or before a large number of maintenance or batch activities, set max degree of parallelism to the smallest of the following values:

· 8

· The number of physical processor cores

· The number of physical processor cores per non-uniform memory access (NUMA) node

· When the Microsoft Dynamics AX database is used in a production environment, set max degree of parallelism to 1.

Use the following statements to set the value of max degree of parallelism.

Examine the output from the second sp_configure 'max degree of parallelism' statement, and confirm that the value has been changed. In the following query, the first sp_configure 'max degree of parallelism' statement sets the value of max degree of parallelism to 1. The second sp_configure 'max degree of parallelism' statement returns a value of 1.

EXEC sp_configure 'show advanced options', 1;

RECONFIGURE;

GO

EXEC sp_configure 'max degree of parallelism', 1;

RECONFIGURE;

GO

EXEC sp_configure;


Configuring max server memory
SQL Server dynamically acquires and frees memory as required. Typically, an administrator does not have to specify how much memory is allocated to SQL Server. However, the max server memory option can be useful in some environments. Make sure that sufficient memory is available for the operation of Windows Server. 



Monitoring available memory
Make sure that sufficient memory is available for the operation of Windows Server. For example, make sure that you run a dedicated instance of SQL Server on a server that has at least 4 gigabytes (GB) of memory. If the available memory for the server drops below 500 megabytes (MB) for extended periods, the performance of the server may degrade.



Allocating storage for tempdb
MS recommend that you determine the total size of the data files and transaction log files that are required for the tempdb database, and that you set a specific value. Do not use automatic growth, or autogrow, setting for space management. Instead, use autogrow as a safety mechanism, so that tempdb can grow if tempdb files use the space that was originally allocated to them. Follow this process to determine the number and placement of data files.



·        Determine the number of processors that are available to SQL Server. Unless you are using an affinity mask, this number is same as the total number of processors that you see on the Performance tab of Windows Task Manager. When hyperthreading is not enabled, each processor corresponds to a processor core. Affinity masks and processor cores are beyond the scope of this topic. 

·        Based on performance testing of the OLTP workload for Microsoft Dynamics AX, we recommend that you maintain one tempdb data file per processor. 

·      Isolate tempdb on dedicated storage, if you can. MS recommend that you move the primary data file and log file for tempdb to high-speed storage, if high-speed storage is available. The Microsoft Dynamics AX database runs in read committed snapshot isolation (RCSI) mode. In RCSI mode, row versions are stored in tempdb. By creating multiple files for tempdb data, even if these files reside on the same storage device, you can improve the performance of tempdb operations.

·        Determine the size of the tempdb data files and log files. You must create one primary data file and one log file. Determine how many additional, secondary data files you require for the tempdb data. For best results, create data files of equal size. The total number of data files must equal the total number of processor cores. The aggregate size of the primary data file and all other data files must equal the total data size that you determined for the tempdb database.

·        Resize the primary data file and log file for tempdb. Move the primary data file and log file to dedicated storage, if dedicated storage is available. The primary tempdb data file cannot be moved while the instance of SQL Server is running. To complete the move, you must use an ALTER DATABASE statement and restart the instance of SQL Server. 

·      If space is available on the drive where tempdb files are allocated, do not configure the autogrow property for data files and log files as a percentage. Instead, configure the autogrow property as a specific number of megabytes. If you can, configure the data files and log files to grow by 100 to 500 MB, depending on the available space. Monitor the data files, and when they grow, adjust the original allocation to prevent automatic growth later. If the autogrow property is configured in megabytes instead of as a percentage, the allocation of space is more predictable, and the chance of extremely small or large growth increments is reduced.

·        Monitor the tempdb data files and log files to make sure that theyare all sized correctly, and that all data files are of equal size. Use SQL Server Management Studio or a transact-SQL query to view the database properties. Verify that all the data files are of equal size, and that they have the same size as the value that you originally provided. If one or more files have grown, adjust the initial size of all files.

Plan database storage

1. Characterize the input/output (I/O) load of the application. The I/O characteristics depend on your business requirements, and on the Microsoft Dynamics AX modules and components that we deploy. To determine your I/O characteristics, answer the following questions:

· What is the read ratio versus write ratio of the application?

· What is the typical I/O volume, or I/O per second (IOPs)?

· How much of the I/O is sequential, and how much is random?

2. Determine the availability and performance requirements for the database system.

3. Determine the hardware that is required to support

4. Configure SQL Server properly.

5. Track the performance as the workload changes

Configuring physical storage

· Create the tempdb database files, data files for the Microsoft Dynamics AX database, and Microsoft Dynamics AX log files on disk arrays of type RAID 1, RAID 0 + 1, or RAID 10. Microsoft recommend RAID 10 for these files. Do not use RAID 5.

· Store the data files for the Microsoft Dynamics AX database on separate physical stores from the transaction log files.

· Store the tempdb data files on a separate physical store from the data files and log files for the Microsoft Dynamics AX database.

· Store other database files on separate physical stores from the data files and log files for tempdb and the Microsoft Dynamics AX database.

Reference from Technet articles and personal resources

Deploy AX 2012 default SSRS Issue

2013-12-23T13:20:00.001+05:30

ISSUE:

The deployment was aborted. You do not have privileges to deploy to server: XXXXX-01. For deployment, you must have administrative rights to the SQL Server Reporting Services (SSRS) server. Contact your administrator to deploy.

RESOLUTION:

Skip the reports from the admin check. we have to use the "SkipReportServerAdminCheck"command in publish AXReport comand line.

Command will be:

Publish-AXReport -ReportName * -SkipReportServerAdminCheck

Test Data Transfer Tool for Microsoft Dynamics AX 2012

2013-07-04T18:03:00.000+05:30

Test Data Transfer Tool for Microsoft Dynamics AX 2012

Reference: technet.microsoft.com and other sources

Microsoft has released the beta version of Test Data Transfer Tool for Dynamics AX 2012. Which is applies to Microsoft Dynamics AX 2012 Feature Pack and Microsoft Dynamics AX 2012.

This tool is a command-line tool that exports data from a Microsoft Dynamics AX 2012 transaction database in a production or non-production environment. The tool also imports data into a Microsoft Dynamics AX 2012 business database in a non-production environment. The non-production environment can be either a development or test environment. Microsoft strongly recommends not use this tool to import data into a production environment.

The Test Data Transfer Tool (beta) is a powerful tool for importing and exporting data. The test data transfer tool is useful when we required to import large set of data into other environment (Non production), move data in different environments with similar customization's and when data version is required. You must run the tool directly from the system that is hosting the database during import.

To use this tool you should have prior knowledge on SQL databases. To perform the activity using this tool you should be a database administrator or a developer who has experience and also have permission to read from or write directly to the Microsoft Dynamics AX database that you are working with, and to execute applications directly on the computer that is hosting the database. Before performing this activity you need to take the backup of source and destination databases.

Each and every operation that works with data has risks and also make sure that you understand which conditions are logged as errors during import. For example, you might try to import data for a table or column that does not exist in the target database. This attempt is not treated as an error by the tool, because the tool is designed to work seamlessly when the source and target databases have a different set of tables.

The Test Data Transfer Tool (beta) is available from the InformationSource Services download page.

Benefits:

The Test Data Transfer Tool (beta) uses the Microsoft SQL Server bulk copy tool (bcp). The Test Data Transfer Tool provides the following key benefits that other methods for importing and exporting Microsoft Dynamics AX data do not provide:

You can export or import data when an AOS instance is not running.
You can export or import Microsoft Dynamics AX data more quickly compared to other methods.
Only minimal changes are made to the data that you import. This feature helps guarantee that the data is stable over time. For example, the tool never renumbers RecIDs.
The data file format is text-based. Therefore, the data can be compared with earlier versions and stored in a version control system.
The data file format is a standard format that is produced by bcp.

The Test Data Transfer Tool (beta) adds the following features that work with bcp. These features make bcp an appropriate tool for managing data for Microsoft Dynamics AX.

Exported data can be filtered. Therefore, specified tables, columns, or rows can be easily excluded from the export.
Differences between builds of Microsoft Dynamics AX 2012 are found and corrected. These differences often occur during development. Because of this feature, data can often be imported without user intervention, even when the table definitions have changed. For example, tables or fields that have been renamed do not prevent import.
Entity IDs, such as table IDs, class IDs, and extended data type IDs, are updated to match the IDs of the target system.
The tool reads and correctly updates the SYSTEMSEQUENCES table.

Limitations:

The Test Data Transfer Tool (beta) does not make sure that data that you export is complete or coherent. However, the tool does export any data that you ask it to export.
The tool does not make sure that data that you import produces a complete or coherent database. However, the tool does import any data that you ask it to import.

The Test Data Transfer Tool (beta) imports and exports the data as-is. In some cases, you might exclude tables or records from either import or export. Nevertheless, the tool does not make sure that the data is complete or coherent when other tables contain references to excluded tables or records. Therefore, after import and export, you must make sure that the data that you are importing or exporting is coherent.

Tools for monitoring performance in AX 2012

2013-06-08T18:54:00.003+05:30

“Good performance requires good and continuous monitoring. If you find problematic processes early, you can optimize them without significantly affecting your end users. Remember that performance tuning is an iterative process. Often, you must complete more than one round of tuning to achieve the maximum improvement in performance.” - Microsoft Tech Net, May 29, 2012

Microsoft recommend the following tools for monitoring the performance of Microsoft Dynamics AX.

1. Performance Monitor
Performance Monitor is the basic tool for obtaining an overview of performance. You can review the CPU, disk, and memory counters to find performance issues. After you have identified a time frame during which your system may have experienced performance problems, you can add more specific counters to understand the problem in more detail.

Performance Monitor is a simple yet powerful visualization tool for viewing performance data, both in real time and from log files. With it, you can examine performance data in a graph, histogram, or report.

Membership in the local Performance Log Users group, or equivalent, is the minimum required to complete this procedure.

To start Performance Monitor

1.     Click Start, click in the Start Search box, type perfmon, and press ENTER.
2.     In the navigation tree, expand Monitoring Tools, and then click Performance Monitor. You can also use Performance Monitor to view real-time performance data on a remote computer. Membership in the target computer's Performance Log Users group, or equivalent, is the minimum required to complete this procedure.

To connect to a remote computer with Performance Monitor

1.     Start Performance Monitor.
2.     In the navigation tree, right-click Reliability and Performance, and then click Connect to another computer.
3.     In the Select Computer dialog box, type the name of the computer you want to monitor, or click Browse to select it from a list.
4.     Click OK.

For more details, follow the below links:

o Set up Performance Monitor counters

o Collect AX 2012 event traces with Windows Performance Monitor

2. Microsoft Dynamics AX 2012 Trace Parser

Trace Parser ships with Microsoft Dynamics AX. Trace Parser consolidates information from multiple sources, such as remote procedure calls (RPCs) and Microsoft SQL Server, to provide an integrated view of application performance at run time.

o Install the Trace Parser

o Tracing Cockpit Form

o Walk through major features of Microsoft Dynamics AX 2012 Trace Parser (Part 1)

o Walk through major features of Microsoft Dynamics AX 2012 Trace Parser (Part 2)

3. Performance Analyzer for Microsoft Dynamics AX (DynamicsPerf)

DynamicsPerf can be used to collect information from Microsoft Dynamics AX and SQL Server. DynamicsPerf consists of a database and a collection of scripts that collect information from SQL Server and Microsoft Dynamics AX. Based on this information, you can find issues such as expensive queries and locking/blocking. When you have gained experience, you can also use this tool to find inefficient code or business processes.

4. System Center Operations Manager Monitoring Pack for Microsoft Dynamics AX 2012

The Monitoring Pack can be used to monitor your system. The Monitoring Pack can automatically discover the servers in your environment, monitor server availability, and find violations of setup best practices.

5. Microsoft Visual Studio Profiling Tools

The Visual Studio Profiling Tools help you identify performance issues in source code and compare the performance of possible solutions. For more information, see the following resources:

o Find Application Bottlenecks with Visual Studio Profiler

o Beginners Guide to Performance Profiling

6. Intelligent Data Management Framework for Microsoft Dynamics AX

Intelligent Data Management Framework (IDMF) provides functionality that resembles the functionality of DynamicsPerf, and also includes a user interface. IDMF also provides tools for activities that are related to data management, such as archiving and purging.

IDMF Screenshots:

7. Performance Analyzer for Dynamics

Performance Analyzer 1.0 for Microsoft Dynamics is the tool used by Microsoft Dynamics support, Premier Field Engineers, and product team members to diagnose performance issues with Dynamics products. The following is a step-by-step guide to installing this tool set on your SQL Server environment.

This tool is delivered as a SQL Server solution file and can be downloaded from http://code.msdn.com/dynamicsperf. Once the file is unzipped the solution can be opened from within SQL Server Management Studio.

On the Menu, click File | Open | Project Solution

Choose the Performance Analyzer 1.0 for Microsoft Dynamics Solution file

To view the Solution Explorer in SQL Server Management Studio, click View | Solution Explorer or Ctrl - ALT-L.

The next step in deploying the tool is creating the database and the objects. In Solution Explorer, on the right hand side, select CreateDynamicsPerfDB.sql query.

This script will create a database called DynamicsPerf in the default location. It is initially 500Mb for the data file and 100Mb for the Transaction Log file for this database. Each data collection is approximately 500Mb to 1 GB in size. This varies widely depending upon total system memory and how much activity is occurring. To manage database size there is a job called DYNPERF_Capture_Stats_Purge. This job by default will run once per day at 6PM and delete data older then 7 days old. Adjusting the number of days to retain data in this job is the method for controlling the database size of the DynamicsPerf database.

The next step is to create all of the database objects and SQL Jobs used by Performance Analyzer. Select CreateDynamicsPerfObjects.sql query on the right hand side in Solution Explorer.

This script creates all of the Tables, Procedures, and SQL Jobs used by the tool in the DynamicsPerf database. In order to do blocking analysis, the script will set a configuration option called "Blocked Processes Report" to five seconds. (Setting up data gathering for blocking will be explained in another blog post.) After running the create object script the results returned from this script should look as follows:

Performance Analyzer is designed to capture all Query and Index data for one database. To make this easier to configure, all basic functionality to collect data has been provided in a set of SQL Jobs. In order to do basic data capture, the SQL Job called DYNPERF_Capture_Stats must be edited to define which database to collect performance data on.

Either double click this job, or right click and select properties. This should bring up the following dialog to edit the SQL job.

Click on the Steps page on the left hand side of this dialog

Click the Edit button to edit the single step in this job.

In the command of this job step, change the '<dbname>' to the name of the database to collect performance data from such as 'AX_Live'. Click the 'Ok' button to save the changes.

At this point, basic data collection has been setup for Performance Analyzer . By default data will be collected once per day at 5PM. This is the default schedule for the DYNPERF_Capture_Stats job, but you can edit it to find a time that better fits the data you're trying to collect.

Reference from : http://technet.microsoft.com/ and other MS materials...

Bank Integration with AX 2012 (Electronic Payments)

2013-05-30T17:45:00.000+05:30

Approach

This article provides the information about the Electronic Payment and the creation of bank files to make the payments has changed dramatically in Microsoft Dynamics AX 2012.

Overview of payment generation by using AIF

The CustPaymentsService and VendPaymentsService services expose payment information for the AIF outbound processing service. These services are based on Microsoft Dynamics AX queries. The queries capture all the data that is required to generate electronic payment files for customers or vendors. Developers can modify the service, document, and data object classes by using the AIF document service wizard.

First, set up the AIF transforms and then export payment data that is defined by the queries. An XSL transform can be applied to this data to transform the AIF XML file to the payment file for a specified format.

For every payment format that we intend to generate by using AIF, we must have a corresponding XSLT file. This XSLT file is based on the format that is specified by the bank. Several XSLT files are provided with Microsoft Dynamics AX. However, we can create our own XSLT file by using a text editor or XML editor.

For payment files that are not in XML format, we must apply an outbound transform to convert the XML results to a flat file. Outbound transforms can be of any file type, such as binary or XSLT. When we apply the outbound transform to the XML file that is generated by AIF, the XML tags are removed and the payment file is created in the format that is required by the bank.

In addition to the master data, payment-specific data might be required for each file, depending on the requirements of the bank. This data can be associated with outbound ports, and can be defined in the Payment processing data form by the system administrator. Then, when users generate payments, the users can enter values in the fields.

The following Diagram shows the steps that are required to configure and use payment formats by using AIF services.

Payment integration process flow:

Setting up an outbound payment format (XML)

In Microsoft Dynamics AX, we can use a service to create electronic payment files. Before we can use the service, we must configure an outbound integration port. Set up an outbound integration port for payments that use Application Integration Framework (AIF) and the payment format XSL transforms.

In this, we need to export an XML style sheet from the Application Object Tree (AOT), set up a batch job to generate XML files, and set up an outbound port for electronic payments. We have added an outbound transform, because of it’s a special XML format is required by the Banks that we are processing payments for.

Create a Directory to Export the XSLT file.

Select the file type as “XML Document” and the document in the created directory.

Outbound ports for electronic payments

Create a Directory to Export the XSLT file

Click the View -> Payment processing data button.

Click Area Page node: System administration -> Setup -> Services and Application Integration Framework -> Outbound ports.

Click the Outbound pipelines button-> Configure button

Click the Import XSLT button and provide XSL payment file.

Click the View button to view the uploaded XSL.

Click the Outbound transforms button.

Click the Manage transforms button.

Create transformation of type XSL and click the Load button and select transformation XSL.

Close manage transformation and select the newly created transformation under outbound transformation form.

Click the Close toolbar button and Transforms form.

Change the adapter to FTP adapter and provide the FTP path.

Set up a batch job to generate XML payment files

Accounts payable -> Journals -> Payments -> Payment journal.

A batch job runs periodically. We must set up a batch job that automatically processes documents that are created by the service.

Log on to Microsoft Dynamics AX as an administrator.
Switch to the legal entity that users will generate payments from.
Click System administration > Inquiries > Batch jobs > Batch jobs.
Press CTRL+N to create a batch job.
In the Job description field, enter a description.
Save the batch job.
Click View tasks.
Create the following tasks.

Task description	Company accounts	Class name
1	Select the legal entity that users will generate payments from.	AIFGatewaySendService
2	Select the legal entity that users will generate payments from.	AIFOutboundProcessingService

Close the Batch tasks form.
In the Batch job form, select the batch that we created in steps 4 and 5, and then click Recurrence.
In the Recurring pattern field group, select Minutes, and then enter the number of minutes in the Count field. For example, we might enter 1 to process payment files every one minute.
Click OK to close the Recurrence form.
In the Batch job form, select the batch that we created in steps 4 and 5, and then click Functions > Change status.
Select Waiting.
Close the Batch job form.

Create a payment journal

Accounts payable -> Journals -> Payments -> Payment journal.

This Document is based on the Single Euro Payments Area (SEPA) Credit Transfer xslt example as supplied by Microsoft.

Click the Lines button.

Click the Functions -> Generate payments menu button.

Select “Export payment using service” and select the new “Payment format.”

Click on OK.

Modify the “Payment processing data” of required and then click on “OK.”

Then, AIF services are running in batch, the document will be processed and exported to the specified FTP folder.

Happy Daxing... :)

MS Dynamics AX 2012 - ADFS

2013-02-09T16:45:00.002+05:30

Microsoft Dynamics AX 2012 - ADFS

Dynamics AX 2012 provides flexible authentication mechanism through the use of Active Directory Federations Services, Forms-based authentication or Windows Live options. Active Directory Federation Services (ADFS) is a feature of Windows Server that allows two companies that have close collaboration to allow their network domains to trust each other. This is commonly used for example where a business function might be outsourced and so the outsourced company users would be authenticated through ADFS to access Dynamics AX. This could also be used in scenarios where vendors log on Dynamics AX to manage inventory on your behalf. Windows Live is a common internet based authentication mechanism. This would be used where you have a large range of customers, vendors or external consultants that needs to access Dynamics AX for account management activities. Forms-based authentication validates credentials that are entered in a logon form.

The third major security enhancement in Microsoft Dynamics AX 2012 relates to authentication, which determines who is able to access the ERP solution. With the growing need to integrate more closely across the supply chain, authentication has become a pressing need for organizations that need their suppliers, partners, and customers to be able to directly interface with their ERP. Our new flexible authentication model makes it much easier for external users to securely access ERP data through the Enterprise Portal or other web-based applications.

Building on the Windows Identity Foundation, MS extended the authentication model in Microsoft Dynamics AX 2012 by using open-standard application programming interfaces (APIs). This simplifies administration of these external accounts by allowing authentication using Active Directory Federation Services (ADFS), Windows Live ID or other similar methods (e.g. Forms based Authentication), without requiring the external parties to be provisioned in an Active Directory domain.

MS introduce these enhancements, which dramatically simplify administration, offer greater flexibility and control over data access, and enhance the compliance, security, and privacy of your valuable business data. If you’re developing applications for Microsoft Dynamics AX 2012, MS recommends you to become familiar with the new security model and the development tools on the Development Center for MS Dynamics AX on MSDN.

AX 2012 R2 - New Features

2012-12-22T21:35:00.000+05:30

Microsoft Dynamics AX 2012 R2 New Feature

This article provides a summary of new feature list that have been implemented in Microsoft Dynamics AX 2012 R2.

Functional area	Feature
Accounting framework	Configure a recurring schedule batch job to clear purchase accrual for product receipt source documents
Accounts payable	Adjust taxes on an invoice line
Accounts payable	Integrate a payment calendar to control due dates for payments
Accounts receivable	Record charges on free text invoice lines
Business intelligence	Enterprise Portal Chart control for visualizing transactional and aggregated business data in Enterprise Portal
Business intelligence	Improvements to key performance indicators (KPIs)
Business intelligence	Support for data partitions in cubes
Business intelligence	Support for data partitions in reports
Business intelligence	Support for Power View
Business intelligence	Support for report servers running in SharePoint integrated mode
Business intelligence	Windows PowerShell commands for deploying cubes
Budgeting	Create and approve budget plans
Client and server	Enhancements to the Named user license count report (server)
Client and server	Microsoft Dynamics AX 2012 database split into two databases (server)
Data partitioning	Data partitions have been enabled to support data isolation
Enterprise Portal	Enterprise Portal in Microsoft Dynamics AX 2012 R2 supports Microsoft SharePoint 2013 Products and Technologies
Microsoft Office Add-ins	Localize data in the Microsoft Office Add-in
Microsoft Office Add-ins	Lock a template created by using the Office Add-in
Microsoft Office Add-ins	Microsoft Office Add-in enhancements
Sales and marketing	Cases are secured by case category
Sales and marketing	Generate a lead or opportunity record from a campaign or call list target record
Sales and marketing	Update the name of a party from the party record
Sales and marketing	Update, in bulk, the list of party records assigned to an address book
Sales and marketing	Updates to Sales and marketing Role Centers and the reporting information provided
Setup and upgrade	Data partition assignment for companies during upgrade

Indian Localization features in AX 2012 R2:

Country/region	Feature
India	Accounts receivable and accounts payable invoices
India	Assign financial dimensions to entries generated in the Transfer orders form
India	Automatic calculation of Tax Deducted at Source (TDS) when no Permanent account number (PAN) is registered
India	Bill of entry information is evaluated on a line-by-line basis
India	Cancellation of Bill of entry and invoice registration for India
India	Change to the item type for India
India	Changes to number sequences for Indian financial documents and incentive schemes
India	Changes to the electronic file format for TDS and TCS statements
India	Depreciation calculation for India
India	Duties and privileges added for user roles in features for India
India	Enhancements for purchase and sales orders for India
India	EXIM Advance Authorization (AA) incentive scheme
India	EXIM Duty Drawback (DBK) incentive scheme
India	EXIM Duty Free Import Authorization (DFIA) incentive scheme
India	EXIM Export Promotion Capital Goods (EPCG) incentive scheme
India	Expanded tax type support for project transactions, billing processes, and tax settlements
India	Expanded tax type support for service industry transactions
India	Financial dimensions for India
India	Fixed asset transfer for India
India	For India customs duty and Export Import Policy (EXIM), if the charge as expense ratio is used, the related customs duty is charged to the expense account
India	General ledger updates for India
India	Generation of financial statements in Microsoft® Excel for India
India	Global address book for India
India	Implementation of withholding tax calculation cache
India	Improvements to tax registration number assignments
India	Manual adjustment of taxes
India	Open customer invoices and settlement enhancements for India
India	Organizational model enhancements for India
India	Point of taxation
India	Recalculation of indirect taxes triggered by specific conditions
India	Sales and purchase orders enhancements for India
India	SLJL impact on the Indian custom duty functionality
India	SLJL impact on the Indian excise duty functionality
India	Standard Input Output Norms (SION)
India	Tax rate enhancements for India
India	The method of adjusting direct tax entries that are posted to the general ledger has changed. This feature replaces the feature for TDS and TCS adjustment, which is now deprecated.
India	Threshold exceeding error/warning message removed from India direct tax
India	Update tax information in a corrective free text invoice
India	Update to the Upgrade toolkit
India	Updates to general ledger and tax inquiry forms
India	Updates to import orders for India
India	Uptake of the subledger journal and distribution framework with Indian direct tax
India	VAT commodity codes on sales invoices
India	View and modify accounting entries before posting to the general ledger

Indian Localization in AX 2012 CPT - Oct 22-25

2012-11-03T16:46:00.000+05:30

Indian localization in AX 2012 R2...

Indian Localization Parameters – General Ledger

Stock Transfer activation parameter as part of Indian localization

Stock Transfer

Company Information – Tax details

Indian localization – General Ledger

EXIM -

Formula Designer:

Thank you and Happy DAXing... :)

The backup set holds a backup of a database other than the existing database

2012-11-03T12:28:00.000+05:30

The backup set holds a backup of a database other than the existing database.

Solution:

I have solved the Issue following the below steps.

§ Use WITH REPLACE while using the RESTORE command
§ Execute the following SQL Query

Alter Database MicrosoftDynamicsAX_model

SET SINGLE_USER With ROLLBACK IMMEDIATE

RESTORE DATABASE MicrosoftDynamicsAX_model

FROM DISK = 'D:\AX2012\MicrosoftDynamicsAX_model.bak'
WITH REPLACE

Thank you and Happy DAXing... :)

Updated Query:

ALTER DATABASE AX_IntegrationDB

SET SINGLE_USER WITH

ROLLBACK IMMEDIATE

RESTORE DATABASE AX_IntegrationDB

FROM DISK = 'D:\SIngu\AdrenalinSharedDB.bak'

WITH MOVE 'AX_IntegrationDB' TO 'C:\Program Files\Microsoft SQL Server\MSSQL11.DARWIN\MSSQL\DATA\AX_IntegrationDB.mdf',

MOVE 'AX_IntegrationDB_log' TO 'C:\Program Files\Microsoft SQL Server\MSSQL11.DARWIN\MSSQL\DATA\AX_IntegrationDB_log.ldf',

REPLACE

Step by step import with Data Migration Framework - AX 2012

2012-08-23T23:12:00.000+05:30

Continuation to my previous article “AX 2012 Data Migration Framework”

In this article, we are Importing the LedgerGeneraljournal into AX 2012.

Demo Files are available at:

C:\Program Files\Microsoft Dynamics AX 2012 Data Migration Framework (Beta)\DemoFiles

This is the beta release and therefore there will be bugs, issues and it’s not a complete offering. With that, when we start to look at the use of this framework, we must start with the types of sources we can work from. We do this from the Data Migration Framework > Setup > Source Data Formats.

Apart from flat file, MS is planning to add Ax and ODBC types to the framework.

We can see that there are plans then for allowing both ODBC source types, as well as enabling AX-to-AX, source-to-target usage of this framework. Since this is file based on source types for the Data Migration Framework, out-of-the-box usage for the framework is limited. It’s powerful, and has a lot of great possible value, specifically when the AX and ODBC types are fully added. DMF is work well with the file sources, as I have tested and imported some of the data. If your source data is in flat files then you can start getting a lot of use from the framework.

1. Click on Data Migration Framework > Setup > Source data formats to set up your source data format.

2. Applications: you can select your dimensions. The Dimension code lookup is a multiselection lookup (tick the selection box on the left of the lookup and ok).

3. Click on Data Migration Framework > Common > Processing group. Create a new record and give it a name and description

4. From the Processing group form, click on Entities.

Create a new record for the LedgerGeneraljournal. If we are selecting data from demo flat files, select the path in The Sample file path field or else you want to select (modify) the fields then leave The Sample file path field will be blank.

If you use the Demo files, then skip steps 5, 6 and 7. If you want to modify the columns, then do steps 5, 6 and 7, as it will ask you if you want to modify the existing file format.

5. Generate a sample file by clicking on Generate source file button. Follow the wizard and select the fields to import.

6. Then click the Generate sample file button. This will open up the sample file in notepad.

Click Finish when done.

7. Now fill in your data on the txt file.

8. Back on the main form click the Generate source mapping button. This will analyse the file and do the mapping between the file and the stagging table.

9. Now you can open and view the mapping by clicking on the Modify source mapping button.

It should looks something like this. The Source is your txt file and the Staging is your staging table in AX. If

your source file is messed up, you should be able to see it here.

10. Now validate the setup by clicking the Validate button on the main form.

11. View target mapping. This is a mapping between the Staging to the Target table. This should already be predefined. You can however modify the mapping.

The Function options on the left. These are predefined methods in the class to allow you to execute business logic. The example below, when you pass in a string of dimensions A-B-C, the GenerateDefaultDimension function splits the string up and generates a DefaultDimension RecId.

12. When we check the Entities from, Click the Preview source file button. This loads up the file, to give you a preview of your file.

13. In Processing group form and click the Get staging data. This opens up a dialog with the processing group, click OK. You will then get this form.

Click on the Run to run client side or Click on Run on AOS to run server side. Usually, the user account doing the import wont have access to SQL integration servers. Use the second option and it will run under the service account. This should run and complete with out errors.

14. Now you can see the staging table by going to the Execution history from the Processing group form. From there you click the View staging data button. You can modify the staging data before you process it to the target.

15. To process to the target, click on the Copy data to target button. Follow the options to execute the process.

It’s done, Now the data has been migrated to AX 2012.

That's it for now... :)

Importing Products into AX 2012 - Part 2

2012-08-18T15:07:00.001+05:30

Product master and a related Product variant

Continuation of the Importing Products into AX2012 - Part 1, here I am posting the Create product master, dimensions, variants and release them to the particular company.

Create a product master and a related product variant

To create a product master, use the EcoResProductService.create operation. Then use the EcoResProductMasterDimValue.create operation to associate product dimension values with the product master. Finally, use the EcoResProductService.create operation again, this time to create a product variant.

The code to create a product master is similar to the code that creates a distinct product. The primary difference is the code that associates the product master with a product dimension group (Size-Dim is given in below code).

Release products

A product must be released to a company before it can be used in that company. The ItemService and InventDimCombinationService services serve this purpose. The former can be used to release distinct products and product masters. The latter can be used to release product variants. A product master must be released before any of its product variants can be released.

Release product master

The only information required to release a product to a company is the ID of the product and the ID by which it will be represented in the company (ItemId). It is possible to add information to the ItemService service. In the following example, information about the units used for storage, purchasing, and selling is provided.

Release a product variant

A product variant can be released after a related product master has been released. When you release a product variant to a company, the product variant can be identified in two different ways:

• Use the product number of the product variant.

• Use the ID of the associated product master in the company (ItemId) and the InventDim structure, with the relevant fields set to the dimension values for the variant (the ItemId/InventDim approach).

Code:

using System;

using System.Collections.Generic;

using System.ComponentModel;

using System.Data;

using System.Drawing;

using System.Linq;

using System.Text;

using System.Windows.Forms;

using ProcutMasterImport.ProductDataImportService;

using System.IO;

using System.Text.RegularExpressions;

namespace ProcutMasterImport

{

public partial class Product : Form

{

internal static int ProdNumber = 0;

internal static int Searchname = 1;

internal static int ProdName = 2;

internal static int StorageDimGroup = 3;

internal static int SerialNumGroup = 4;

internal static int InventUnitID = 5;

internal static int PurchUnitID = 6;

internal static int SalesUnitID = 7;

internal static int ProdCompanyID = 8;

internal static int ItemGroup = 9;

internal static int ItemType = 10;

internal static int InventoryModelGroup = 11;

internal static int Baseprice = 12;

//internal static int InventWareHouse = 13;

//internal static int PurchWareHouse = 14;

//internal static int SalesWareHouse = 15;

internal static int Itemsalestaxgroup_PO = 13;

internal static int Itemsalestaxgroup_sales = 14;

internal static int Priceunit_purch = 15;

internal static int Dateofprice_purch = 16;

internal static int Totaldiscount_purch = 17;

internal static int Priceunit_inv = 18;

internal static int Dateofprice_inv = 19;

internal static int Priceunit_sales = 20;

internal static int Dateofprice_sales = 21;

internal static int Totaldiscount_sales = 22;

//Master Data

internal static int MasterProdNumber = 0;

internal static int MasterSearchname = 2;

internal static int MasterProdName = 3;

internal static int DefaultColor = 5;

internal static int DefaultConfig = 6;

internal static int DefaultSiz = 7;

internal static int BOMUnitID = 9;

internal static int InputWeight = 24;

internal static int ProductInstanceRelationType = 38;

internal static int Tareweight = 47;//Column Number in Excel = AV

internal static int TrackingDimGroupName = 49;

internal static int MasterStorageDimGroup = 50;

internal static int MasterProdDimGroup = 51;

internal static int MasterLanguage = 52;

internal static int MasterItemGroup = 53;

internal static int MasterInventoryModelGroup = 54;

internal static int MasterPriceunit_purch = 57;

internal static int MasterPriceunit_sales = 58;

internal static int MasterPriceunit_inv = 59;

internal static int MasterItemsalestaxgroup_PO = 60;

internal static int MasterItemsalestaxgroup_sales = 61;

internal static int MasterProdCompanyID = 62;

//Dim Import - Size

internal static int MasterProdIDSize = 0;

internal static int MasterProdSize = 1;

internal static int MasterProdSizeName = 2;

//Dim Import - Color

internal static int MasterProdIDColor = 0;

internal static int MasterProdColor = 1;

internal static int MasterProdColorName = 2;

//Dim Import - Config

internal static int MasterProdIDConfig = 0;

internal static int MasterProdConfig = 1;

internal static int MasterProdConfigName = 2;

//VariantaCreation

internal static int MasterVariantID = 0;

internal static int MasterVariantSearchname = 1;

internal static int MasterVariantProdMaster = 2;

internal static int MasterVariantName = 3;

internal static int MasterVariantConfig = 4;

internal static int MasterVariantSize = 5;

internal static int MasterVariantColor = 6;

internal static int MasterVariantCompanyID = 8;

//internal static int MasterVariantConfigName = 9;

//internal static int MasterVariantSizeName = 10;

//internal static int MasterVariantColorName = 11;

public static List<string[]> ParseCSVFile(string path, Boolean hasHeaders)

{

List<string[]> CSVRows = new List<string[]>();

int rowNumber = 0;

using (StreamReader inputFile = new StreamReader(path))

{

string line;

string[] line1;

while ((line = inputFile.ReadLine()) != null)

{

String pattern = ",(?=(?:[^\"]*\"[^\"]*\")*(?![^\"]*\"))";

Regex r = new Regex(pattern);

line1 = r.Split(line);

if (hasHeaders != true || rowNumber != 0)

{

CSVRows.Add(line1);

}

rowNumber++;

}

return CSVRows;

}

public Product()

{

InitializeComponent();

}

// //

//Create a product master and a related product variant //

// //

static void createMaster(string[] _product)

{

//Boolean ismastercreated;

//master definition

AxdEntity_Product_EcoResProductMaster productMaster = new AxdEntity_Product_EcoResProductMaster()

{

DisplayProductNumber = _product[MasterProdNumber],

ProductType = AxdEnum_EcoResProductType.Item,

SearchName = _product[MasterSearchname]

};

productMaster.Translation = new AxdEntity_Translation[1];

productMaster.Translation[0] = new AxdEntity_Translation()

{

LanguageId = "en-us",

Name = _product[MasterProdName]

};

productMaster.Identifier = new AxdEntity_Identifier[1];

productMaster.Identifier[0] = new AxdEntity_Identifier()

{

ProductNumber = _product[MasterProdNumber]

};

productMaster.ProductDimGroup = new AxdEntity_ProductDimGroup[1];

productMaster.ProductDimGroup[0] = new AxdEntity_ProductDimGroup()

{

Product = _product[MasterProdNumber],

ProductDimensionGroup = _product[MasterProdDimGroup]

};

productMaster.StorageDimGroup = new AxdEntity_StorageDimGroup[1];

productMaster.StorageDimGroup[0] = new AxdEntity_StorageDimGroup()

{

Product = _product[MasterProdNumber], //"Bulb60W",

StorageDimensionGroup = _product[MasterStorageDimGroup] //"Std-Dim"

};

productMaster.VariantConfigurationTechnology = AxdEnum_EcoResVariantConfigurationTechnologyType.PredefinedVariants;

AxdEcoResProduct axdProduct = new AxdEcoResProduct()

{

Product = new AxdEntity_Product_EcoResProduct[1]

{

productMaster

}

};

CallContext ctx = new CallContext();

EcoResProductServiceClient productService = new EcoResProductServiceClient();

try

{

productService.create(ctx, axdProduct);

}

catch (Exception e)

{

System.Console.WriteLine(e.Message);

System.Console.ReadKey();

}

// //

///master dimensions Size //

// //

static void createMasterDimension_Size(string[] _productDimsSize)

{

//master dimensions definition (two sizes, L and M)

AxdEntity_MasterDim_EcoResProductMasterSize sizeDimensionL = new AxdEntity_MasterDim_EcoResProductMasterSize()

{

SizeProductMaster = _productDimsSize[MasterProdIDSize],

Size = _productDimsSize[MasterProdSize], //"L",

EcoResSize = new AxdEntity_EcoResSize[1]

{

new AxdEntity_EcoResSize()

{

Name = _productDimsSize[MasterProdSize] //"L"

}

Description = _productDimsSize[MasterProdSizeName],

SizeProductDimensionAttribute = 3173

};

AxdEcoResProductMasterDimValue axdDimValue = new AxdEcoResProductMasterDimValue()

{

MasterDim = new AxdEntity_MasterDim_EcoResProductMasterDimensionValue[1]

{

sizeDimensionL

}

};

CallContext ctx = new CallContext();

EcoResProductMasterDimValueServiceClient masterDimensionService = new EcoResProductMasterDimValueServiceClient();

try

{

masterDimensionService.create(ctx, axdDimValue);

}

catch (Exception e)

{

System.Console.WriteLine(e.Message); System.Console.ReadKey();

}

// //

///master dimensions CONFIG definition (two sizes, L and M) //

// //

static void createMasterDimension_Config(string[] _productDimsConfig)

{

//master dimensions definition (two sizes, L and M)

AxdEntity_MasterDim_EcoResProductMasterConfiguration ConfigDimensionL = new AxdEntity_MasterDim_EcoResProductMasterConfiguration()

{

EcoResConf = new AxdEntity_EcoResConf[1]

{

new AxdEntity_EcoResConf()

{

Name = _productDimsConfig[MasterProdConfig]//_productDimsConfig[MasterProdConfigName]// "L"

}

ConfigProductMaster = _productDimsConfig[MasterProdIDConfig],

Configuration = _productDimsConfig[MasterProdConfig], //"L",

Description = _productDimsConfig[MasterProdConfigName],

//AdditionalDescription = _productDimsConfig[MasterProdConfigName],

ConfigProductDimensionAttribute = 3170

};

AxdEcoResProductMasterDimValue axdDimValue = new AxdEcoResProductMasterDimValue()

{

//SenderId = "3274",

MasterDim = new AxdEntity_MasterDim_EcoResProductMasterDimensionValue[1]

{

ConfigDimensionL//, ConfigDimensionM

}

};

CallContext ctx = new CallContext();

EcoResProductMasterDimValueServiceClient masterDimensionService = new EcoResProductMasterDimValueServiceClient();

try

{

masterDimensionService.create(ctx, axdDimValue);

}

catch (Exception e)

{

System.Console.WriteLine(e.Message); System.Console.ReadKey();

}

// //

///master dimensions Size //

// //

static void createMasterDimension_Color(string[] _productDimsColor)

{

//master dimensions definition (two sizes, L and M)

AxdEntity_MasterDim_EcoResProductMasterColor colorDimensionL = new AxdEntity_MasterDim_EcoResProductMasterColor()

{

ColorProductMaster = _productDimsColor[MasterProdIDColor],

Color = _productDimsColor[MasterProdColor], //"L",

EcoResColor = new AxdEntity_EcoResColor[1]

{

new AxdEntity_EcoResColor()

{

Name = _productDimsColor[MasterProdColor] //"L"

}

Description = _productDimsColor[MasterProdSizeName],

ColorProductDimensionAttribute = 3169

};

AxdEcoResProductMasterDimValue axdDimValue = new AxdEcoResProductMasterDimValue()

{

MasterDim = new AxdEntity_MasterDim_EcoResProductMasterDimensionValue[1]

{

colorDimensionL

}

};

CallContext ctx = new CallContext();

EcoResProductMasterDimValueServiceClient masterDimensionService = new EcoResProductMasterDimValueServiceClient();

try

{

masterDimensionService.create(ctx, axdDimValue);

}

catch (Exception e)

{

System.Console.WriteLine(e.Message); System.Console.ReadKey();

}

// //

////product variant definition//

// //

static void createVariant(string[] _productVariant)

{

//product variant definition

AxdEntity_Product_EcoResDistinctProductVariant productVariant = new AxdEntity_Product_EcoResDistinctProductVariant()

{

DisplayProductNumber = _productVariant[MasterVariantID], //"RunningShoeL",

ProductType = AxdEnum_EcoResProductType.Item,

SearchName = _productVariant[MasterVariantSearchname], //"RunningShoeL",

ProductMaster = _productVariant[MasterVariantProdMaster] //"RunningShoe"

};

productVariant.Translation = new AxdEntity_Translation[1];

productVariant.Translation[0] = new AxdEntity_Translation()

{

LanguageId = "en-us",

Name = _productVariant[MasterVariantName] //"Comfortable running shoe L size"

};

productVariant.VariantDimValue = new AxdEntity_VariantDimValue_EcoResProductVariantDimensionValue[3];

if (_productVariant[MasterVariantSize].ToString() != "")

{

productVariant.VariantDimValue[0] = new AxdEntity_VariantDimValue_EcoResProductVariantSize()

{

DistinctProductVariant = _productVariant[MasterVariantID], //"RunningShoeL",

ProductDimensionAttribute = 3173,//The ID of the EcoResSize table

Size = _productVariant[MasterVariantSize], //"L",

EcoResSize = new AxdEntity_EcoResSize1[1]

{

new AxdEntity_EcoResSize1()

{

Name = _productVariant[MasterVariantSize] //"L"

}

};

}

//added by imthiyaz - Color

if (_productVariant[MasterVariantColor] != "")

{

productVariant.VariantDimValue[1] = new AxdEntity_VariantDimValue_EcoResProductVariantColor()

{

DistinctProductVariant = _productVariant[MasterVariantID],

ProductDimensionAttribute = 3169,

Color = _productVariant[MasterVariantColor], //"L",

EcoResColor = new AxdEntity_EcoResColor1[1]

{

new AxdEntity_EcoResColor1()

{

Name = _productVariant[MasterVariantColor]

}

};

}

//added by imthiyaz - Config

if (_productVariant[MasterVariantConfig] != "")

{

productVariant.VariantDimValue[2] = new AxdEntity_VariantDimValue_EcoResProductVariantConfiguration()

{

DistinctProductVariant = _productVariant[MasterVariantID],

ProductDimensionAttribute = 3170,

Configuration = _productVariant[MasterVariantConfig], //"L",

EcoResConf = new AxdEntity_EcoResConf1[1]

{

new AxdEntity_EcoResConf1()

{

Name = _productVariant[MasterVariantConfig]

}

};

}

AxdEcoResProduct axdProduct = new AxdEcoResProduct()

{

Product = new AxdEntity_Product_EcoResProduct[1]

{

productVariant

}

};

CallContext ctx = new CallContext();

EcoResProductServiceClient productService = new EcoResProductServiceClient();

try

{

productService.create(ctx, axdProduct);

}

catch (Exception e)

{

System.Console.WriteLine(e.Message); System.Console.ReadKey();

}

// //

////Release a product master//

// //

private static void releaseMasterProduct(string[] _productRelease)

{

AxdEntity_InventTable inventTable = new AxdEntity_InventTable()

{

ItemId = _productRelease[MasterProdNumber], //"Bulb60W",

Product = _productRelease[MasterProdNumber], //"Bulb60W",

SalesPriceModelBasic = AxdEnum_SalesPriceModelBasic.PurchPrice, //(AxdEnum_SalesPriceModelBasic)Enum.Parse(typeof(AxdEnum_SalesPriceModelBasic), _productRelease[Baseprice]),//_product[Baseprice],

//SerialNumGroupId = _productRelease[SerialNumGroup],

Invent = new AxdEntity_Invent[1]

{

new AxdEntity_Invent()

{

ItemId = _productRelease[MasterProdNumber], //"Bulb60W",

UnitId = _productRelease[MasterPriceunit_inv] //"Box"

}

Purch = new AxdEntity_Purch[1]

{

new AxdEntity_Purch()

{

ItemId = _productRelease[MasterProdNumber], //"Bulb60W",

UnitId = _productRelease[MasterPriceunit_purch] //"Box"

}

Sales = new AxdEntity_Sales[1]

{

new AxdEntity_Sales()

{

ItemId = _productRelease[MasterProdNumber], //"Bulb60W",

UnitId = _productRelease[MasterPriceunit_sales] //"Pcs"

}

InventModelGroupItem = new AxdEntity_InventModelGroupItem[1]

{

new AxdEntity_InventModelGroupItem()

{

ModelGroupId = _productRelease[MasterInventoryModelGroup]

}

InventItemGroupItem = new AxdEntity_InventItemGroupItem[1]

{

new AxdEntity_InventItemGroupItem()

{

ItemGroupId = _productRelease[MasterItemGroup]

}

};

/*inventTable.StandardInventColorId = _productRelease[DefaultColor];

inventTable.StandardConfigId = _productRelease[DefaultConfig];

inventTable.StandardInventSizeId = _productRelease[DefaultSiz];*/

//default size, color, config cvon't be aasuigned here

inventTable.BOMUnitId = _productRelease[BOMUnitID];

inventTable.NetWeight = Decimal.Parse(_productRelease[InputWeight]);

inventTable.TaraWeightSpecified = true;

inventTable.MetalTypeSpecified = true;

inventTable.TaraWeight = Decimal.Parse(_productRelease[Tareweight]);

AxdItem item = new AxdItem()

{

InventTable = new AxdEntity_InventTable[1]

{

inventTable

}

};

CallContext ctx = new CallContext()

{

Company = _productRelease[MasterProdCompanyID] //"DMO"

};

ItemServiceClient itemService = new ItemServiceClient();

try

{

itemService.create(ctx, item);

}

catch (Exception e)

{

System.Console.WriteLine(e.Message); System.Console.ReadKey();

}

// //

///Use the ItemId/InventDim approach//

// //

private static void releaseProductVariants2(string[] _productVariantRelease)

{

AxdEntity_InventDimCombination releasedVariant = new AxdEntity_InventDimCombination()

{

DistinctProductVariant = "",

ItemId = _productVariantRelease[MasterVariantProdMaster],// "RunningShoe",

InventDimId = "",

InventDim = new AxdEntity_InventDim[1]

{

new AxdEntity_InventDim()

{

InventSizeId = _productVariantRelease[MasterVariantSize], //"M",

InventColorId = _productVariantRelease[MasterVariantColor],

ConfigId = _productVariantRelease[MasterVariantConfig]

}

};

AxdInventDimCombination inventDimCombination = new AxdInventDimCombination()

{

InventDimCombination = new AxdEntity_InventDimCombination[1]

{

releasedVariant

}

};

CallContext ctx = new CallContext()

{

Company = _productVariantRelease[MasterVariantCompanyID] //"DMO"

};

InventDimCombinationServiceClient inventDimCombinationService = new InventDimCombinationServiceClient();

try

{

inventDimCombinationService.create(ctx, inventDimCombination);

}

catch (Exception e)

{

System.Console.WriteLine(e.Message); System.Console.ReadKey();

}

private void ProductMaster_Click(object sender, EventArgs e)

{

List<string[]> ProdData = ParseCSVFile("D:\\ProductMasters.csv", true);

foreach (string[] ProdMasterData in ProdData)

{

createMaster(ProdMasterData);

}

private void CreateDims_Click(object sender, EventArgs e)

{

List<string[]> ProdDims_Size = ParseCSVFile("D:\\MasterDimSize.csv", true);

foreach (string[] MasterDimensions_Size in ProdDims_Size)

{

createMasterDimension_Size(MasterDimensions_Size);

}

List<string[]> ProdDims_Color = ParseCSVFile("D:\\MasterDimsColor.csv", true);

foreach (string[] MasterDimensions_Color in ProdDims_Color)

{

createMasterDimension_Color(MasterDimensions_Color);

}

List<string[]> ProdData_Config = ParseCSVFile("D:\\MasterDimConfig.csv", true);

foreach (string[] MasterDimensions_Config in ProdData_Config)

{

createMasterDimension_Config(MasterDimensions_Config);

}

private void CreateVariants_Click(object sender, EventArgs e)

{

List<string[]> ProdData_Variants = ParseCSVFile("D:\\ProductMasterVariants.csv", true);

foreach (string[] ProdMasterData_Variants in ProdData_Variants)

{

createVariant(ProdMasterData_Variants);

}

private void ReleaseAll_Click(object sender, EventArgs e)

{

List<string[]> ProdMasterData_Rel = ParseCSVFile("D:\\ProductMasters.csv", true);

foreach (string[] ProdMasterDataRelease in ProdMasterData_Rel)

{

releaseMasterProduct(ProdMasterDataRelease);//master products

}

private void ReleaseVariants_Click_1(object sender, EventArgs e)

{

List<string[]> ProdData_VariantsRel = ParseCSVFile("D:\\ProductMasterVariants.csv", true);

foreach (string[] ProdMasterData_VariantsRel in ProdData_VariantsRel)

{

releaseProductVariants2(ProdMasterData_VariantsRel);

}

Sample CSV:

Importing Products into AX 2012 - Part 1

2012-08-17T18:37:00.001+05:30

Distinct Product Import

Microsoft Dynamics AX is shipped with many standard document services that support common business processes. By using the capabilities that AIF provides, you can also customize existing document services or create your own document services.

We have had several questions on how to import items/products into AX 2012. Hope this helps!

Inbound port of the Product service

To call the service, you need to expose the service on a new inbound port in Microsoft Dynamics AX.

1. Click System administration >Setup > Services and Application Integration Framework > Inbound ports, and then click New.

2. Give the new port a name, such as Product Data Import Services.

3. Enter a description.

4. Under Service Contract Customizations, click Service Operations. The Select service operations form opens.

5. Select the all the product related operations, move them to the Selected operations pane, and then click Close.

6. In the Inbound ports form, click Activate.

You can now access the service externally by using the WSDL URI

Select the service Operations:

After Selection of the services, activate the Port:

Set up the Product data import service reference in Microsoft Visual Studio

1. Open Microsoft Visual Studio®, and create a new project.
2. Add a new service reference by using the WSDL URI for the product data import service from the Inbound ports form.
3. Add a Using statement for the service reference.

You are now ready to start coding against the Distinct Product service.

code to import Distinct products from a .csv file by using a Visual Studio service reference

This section provides the code that shows the correct order of operations to create a new products in Microsoft Dynamics AX 2012.

using System;

using System.Collections.Generic;

using System.ComponentModel;

using System.Data;

using System.Drawing;

using System.Linq;

using System.Text;

using System.Windows.Forms;

using ProductsImport.ProductDataImportService;

using System.IO;

using System.Text.RegularExpressions;

namespace ProductsImport

{

public partial class Product : Form

{

internal static int ProdNumber = 0;

internal static int Searchname = 1;

internal static int ProdName = 2;

internal static int StorageDimGroup = 3;

internal static int SerialNumGroup = 4;

internal static int InventUnitID = 5;

internal static int PurchUnitID = 6;

internal static int SalesUnitID = 7;

internal static int ProdCompanyID = 8;

internal static int ItemGroup = 9;

internal static int ItemType = 10;

internal static int InventoryModelGroup = 11;

internal static int Baseprice = 12;

internal static int Itemsalestaxgroup_PO = 13;

internal static int Itemsalestaxgroup_sales = 14;

internal static int Priceunit_purch = 15;

internal static int Dateofprice_purch = 16;

internal static int Totaldiscount_purch = 17;

internal static int Priceunit_inv = 18;

internal static int Dateofprice_inv = 19;

internal static int Priceunit_sales = 20;

internal static int Dateofprice_sales = 21;

internal static int Totaldiscount_sales = 22;

internal static int TrackingDimGroup = 23;

public static List<string[]> ParseCSVFile(string path, Boolean hasHeaders)

{

List<string[]> CSVRows = new List<string[]>();

int rowNumber = 0;

using (StreamReader inputFile = new StreamReader(path))

{

string line;

string[] line1;

while ((line = inputFile.ReadLine()) != null)

{

String pattern = ",(?=(?:[^\"]*\"[^\"]*\")*(?![^\"]*\"))";

Regex r = new Regex(pattern);

line1 = r.Split(line);

if (hasHeaders != true || rowNumber != 0)

{

CSVRows.Add(line1);

}

rowNumber++;

}

return CSVRows;

}

public Product()

{

InitializeComponent();

}

// //

//Create a distinct product //

// //

static void createDistinctProduct(string[] _product)

{

AxdEntity_Product_EcoResDistinctProduct distinctProduct = new AxdEntity_Product_EcoResDistinctProduct()

{

DisplayProductNumber = _product[ProdNumber], //"Bulb60W",

ProductType = (AxdEnum_EcoResProductType)Enum.Parse(typeof(AxdEnum_EcoResProductType), _product[ItemType]),//AxdEnum_EcoResProductType.Item,

SearchName = _product[Searchname] //"Bulb60W"

};

distinctProduct.Translation = new AxdEntity_Translation[1];

distinctProduct.Translation[0] = new AxdEntity_Translation()

{

LanguageId = "en-us",

Name = _product[ProdName] //"Transparent Bulb 60W"

};

distinctProduct.Identifier = new AxdEntity_Identifier[1];

distinctProduct.Identifier[0] = new AxdEntity_Identifier()

{

ProductNumber = _product[ProdNumber] //"Bulb60W"

};

distinctProduct.StorageDimGroup = new AxdEntity_StorageDimGroup[1];

distinctProduct.StorageDimGroup[0] = new AxdEntity_StorageDimGroup()

{

Product = _product[ProdNumber], //"Bulb60W",

StorageDimensionGroup = _product[StorageDimGroup] //"Std-Dim"

};

distinctProduct.TrackingDimGroup = new AxdEntity_TrackingDimGroup[1];

distinctProduct.TrackingDimGroup[0] = new AxdEntity_TrackingDimGroup()

{

Product = _product[ProdNumber], //"Bulb60W",

TrackingDimensionGroup = _product[TrackingDimGroup] //"Std-Dim"

};

AxdEcoResProduct axdProduct = new AxdEcoResProduct()

{

Product = new AxdEntity_Product_EcoResProduct[1]

{

distinctProduct

}

};

CallContext ctx = new CallContext();

EcoResProductServiceClient service = new EcoResProductServiceClient();

try

{

service.create(ctx, axdProduct);

}

catch (Exception e)

{

MessageBox.Show(e.Message);

// System.Console.ReadKey();

}

// //

////Release a distinct product //

// //

private static void releaseDistinctProduct(string[] _product)

{

/*if (_product[Dateofprice_inv].ToString() == "")

datetime;*/

AxdEntity_InventTable inventTable = new AxdEntity_InventTable()

{

ItemId = _product[ProdNumber], //"Bulb60W",

Product = _product[ProdNumber], //"Bulb60W",

SalesPriceModelBasic = (AxdEnum_SalesPriceModelBasic)Enum.Parse(typeof(AxdEnum_SalesPriceModelBasic), _product[Baseprice]),//_product[Baseprice],

SerialNumGroupId = _product[SerialNumGroup],

Invent = new AxdEntity_Invent[1]

{

new AxdEntity_Invent()

{

ItemId = _product[ProdNumber], //"Bulb60W",

UnitId = _product[InventUnitID]

, //"Box"

PriceUnit = decimal.Parse(_product[Priceunit_inv]),

PriceDate = DateTime.Parse(_product[Dateofprice_inv])

}

Purch = new AxdEntity_Purch[1]

{

new AxdEntity_Purch()

{

ItemId = _product[ProdNumber], //"Bulb60W",

UnitId = _product[PurchUnitID], //"Box"

TaxItemGroupId = _product[Itemsalestaxgroup_PO],

PriceUnit = decimal.Parse(_product[Priceunit_purch]),

//if(_product[Dateofprice_purch].ToString() != "")

PriceDate = DateTime.Parse(_product[Dateofprice_purch]),

EndDisc = (AxdEnum_NoYes)Enum.Parse(typeof(AxdEnum_NoYes), _product[Totaldiscount_purch])

}

Sales = new AxdEntity_Sales[1]

{

new AxdEntity_Sales()

{

ItemId = _product[ProdNumber], //"Bulb60W",

UnitId = _product[SalesUnitID], //"Pcs"

TaxItemGroupId = _product[Itemsalestaxgroup_sales],

PriceUnit = decimal.Parse(_product[Priceunit_sales]),

PriceDate = DateTime.Parse(_product[Dateofprice_sales]),

EndDisc = (AxdEnum_NoYes)Enum.Parse(typeof(AxdEnum_NoYes), _product[Totaldiscount_sales])

}

/* Invent = new AxdEntity_Invent[1] { new AxdEntity_Invent() { ItemId = _product[ProdNumber], UnitId = _product[InventUnitID] } },

Purch = new AxdEntity_Purch[1] { new AxdEntity_Purch() { ItemId = _product[ProdNumber], UnitId = _product[PurchUnitID] } },

Sales = new AxdEntity_Sales[1] { new AxdEntity_Sales() { ItemId = _product[ProdNumber], UnitId = _product[SalesUnitID] } },

InventModelGroupItem = new AxdEntity_InventModelGroupItem[1]

{

new AxdEntity_InventModelGroupItem()

{

ModelGroupId = _product[InventoryModelGroup]

}

InventItemGroupItem = new AxdEntity_InventItemGroupItem[1]

{

new AxdEntity_InventItemGroupItem()

{

ItemGroupId = _product[ItemGroup]

}

};

AxdItem item = new AxdItem()

{

InventTable = new AxdEntity_InventTable[1]

{

inventTable

}

};

CallContext ctx = new CallContext()

{

Company = "CEU"

};

ItemServiceClient itemService = new ItemServiceClient();

try

{

itemService.create(ctx, item);

}

catch (Exception e) { System.Console.WriteLine(e.Message); System.Console.ReadKey(); }

}

private void DistiunctProducts_Click(object sender, EventArgs e)

{

List<string[]> ProdData = ParseCSVFile("E:\\Products.csv", true);

//Create a Product for each row in the .csv file

foreach (string[] DistinctProduct in ProdData)

{

createDistinctProduct(DistinctProduct);

releaseDistinctProduct(DistinctProduct);//distinct products

}

}

Sample CSV:

Header	Record
ProductNumber	DAX2012BOM21
Searchname	MS Dynamics AX 2012
ProdName	MS Dynamics AX 2012
StorageDimGroup	STD-DIM
SerialNumGroup	CSIG
InventUnitID	GM
PurchUnitID	GM
SalesUnitID	GM
ProdCompanyID	CEU
ItemGroup	CDS
ItemType	Item
InventoryModelGroup	STD
Base price	PurchPrice
Item sales tax group(PO)
Item sales tax group(sales )
Price unit(purch)	1
Date of price(purch)	1/1/1900
Total discount(purch)	Yes
Price unit(inv)	1
Date of price(inv)	1/1/1900
Price unit(sales)	1
Date of price(sales)	1/1/1900
Total discount(sales)	Yes

AX 2012 Data Migration Framework

2012-07-28T15:47:00.001+05:30

Microsoft has released Microsoft Dynamics AX 2012 Data Migration Framework Beta.

You can download the beta release of MicrosoftDynamics AX 2012 Data Migration Framework (Beta) from information source with Partner/Customer login.

The Data Migration Framework for Microsoft Dynamics AX 2012 is an extension that helps you migrate data into Microsoft Dynamics AX. For Example: master data, open stock, and balances.

Architecture

The following diagram shows the architecture of the Data Migration Framework. Staging is a table that the Data Migration Framework creates in the Microsoft Dynamics AX database where the target entities reside.

Configuration

The following diagram shows the configuration steps that are required before you can migrate entities into Microsoft Dynamics AX.

The following entities available in the Microsoft Dynamics AX 2012 Data Migration Framework:

ü Bill of materials (BOM)

ü Contacts

ü Contact addresses

ü Customer

ü Customer addresses

ü Dimension

ü Employees

ü Employee addresses

ü Inventory journal

ü Ledger balances

ü Main account

ü Open invoices (accounts payable)

ü Open invoices (accounts receivable)

ü Open sales orders

ü Open purchase orders

ü Price disc

ü Product

ü Project

ü Unit of measure

ü Vendor

ü Vendor address

When you define a processing group, you must identify sample data for each entity. The sample data is used to validate the source to staging mapping.

If you do not have sample data, you can use the Data Migration Framework to help define a template for the data, and then enter sample data in the template.

Processing

The approach is de-normalize the datasets that make up the Data model in AX 2012 with targeted staging tables. Then you have X++ code that work against the staging tables, to fill the normalized, and sometimes super normalized, datasets of AX 2012.

The following diagram shows the processes that run when data is copied from source to staging, and from staging to target.

Source to staging processing

When an entity is copied from source to staging, a processing group that is associated with one or more entities runs as a job.

After processing has been completed, you should validate that the entity appears accurate in the staging table, and that the reference data is mapped correctly.

Staging to target processing

When data is copied from staging to target, a job that is already defined, and that is associated with a processing group, runs.

After processing has been completed, you should validate that the entity appears accurate in the target table.

After the migration has been completed successfully, we recommend that you delete the staging data.

Microsoft strongly recommend to delete the staging data after migration is complete. It may contain high business impact information.

After Downloading the files from Partner/Customer source. Click on the Setup file.

Setup should run on AOS Instance and on AX Client.

After Installation, increase the "Maximum buffer size" setting for your environment while you migrate data. Use the Server configuration utility to set the value.

When you open the Destination folder of installed objects, you can see the following files will be created.

Now we have to import the model file that came as part of the installation. Install the model file using the PowerShell command console.

Command: (If you have multiple instances on a single machine)

Install-AXModel -File c:\Program Files\Microsoft Dynamics AX 2012 Data Migration Framework (Beta)\ DataMigrationFramework.axmodel –config $AOSInstanceName

After Model file installation, if you open the instance the following screen will be displayed. Because of the model store has been modified.

Click on the compile and synchronization, after completion of compilation and synchronization from the application, need to generate the FULL CIL compilation.

After compilation of FULL CIL, AX 2012 instance has the Data Migration Framework Beta version is deployed.

In My Next Article I will Post How to Use "Microsoft Dynamics AX 2012 Data Migration Framework"

Data Import in AX 2012 - Employee

2012-07-23T19:12:00.000+05:30

HCMWorker (employee or worker) import

In Cumulative Update 2 for Microsoft Dynamics AX 2012, a new HCMWorkerImport service was added. This service can be used to import employees or workers into the system. When you use this service, your code will create new HCMWorker, HCMEmployment, and HCMEmploymentDetail objects, and will use dirPartyAddressView and dirPartyContactView, similar to the customer import sample code.

Expose an inbound port for the HCMWorker service

To call the service, you need to expose the service on a new inbound port in Microsoft Dynamics AX.

1. Click System administration > Setup > Services and Application Integration Framework > Inbound ports, and then click New.

2. Give the new port a name, such as HCMWorkerImport Services.

3. Enter a description.

4. Under Service Contract Customizations, click Service Operations. The Select service operations form opens.

5. Select the HCMWorkerImportService operations, move them to the Selected operations pane, and then click Close.

6. In the Inbound ports form, click Activate.

You can now access the service externally by using the WSDL URI.

HCMWorkerImport service to create an employee in Microsoft Dynamics AX 2012.

CSV:

Employee	EMP-0001-786
WorkerType	Employee
firstname	RACHNA
Middle name
LastName	Pandey
Title	ASSISTANT MANAGER
Birthday	6/4/1985
Street name	Opp: Maroli Bus Depot, Marol Maroshi,
ZIP/postal Code	220027
City	Mumbai
State	MH
Country/region	IND
Telephone	9966699914
Mobile phone	9966699914
Fax	022-456256236
E-mail	rachna.pandey@ragz.com
Personal Email Id
Salutation
Suffix
Date Of Joining	10/22/2007

Set up the HCMWorker service reference in Visual Studio

1. Open Visual Studio, and create a new project.

2. Add a new service reference by using the WSDL URI for the HCMWorker service from the Inbound ports form.

3. Add a Using statement for the service reference.

using System;

using System.Collections.Generic;

using System.ComponentModel;

using System.Data;

using System.Drawing;

using System.Linq;

using System.Text;

using System.Windows.Forms;

using Worker.HcmDataImportService;

using System.IO;

using System.Text.RegularExpressions;

namespace Worker

{

public partial class HcmWorkers : Form

{

internal static int Personalnumber = 0;

internal static int Employeetype = 1;

internal static int firstname = 2;

internal static int Middlename = 3;

internal static int LastName = 4;

internal static int Title = 5;

internal static int Birthday = 6;

internal static int Streetname = 7;

internal static int ZIPCode = 8;

internal static int City = 9;

internal static int State = 10;

internal static int Country = 11;

internal static int phone = 12;

internal static int mobile = 13;

internal static int Fax = 14;

internal static int Bemail = 15;

internal static int Pemail = 16;

internal static int sal = 17;

internal static int Suffix = 18;

internal static int Joindate = 19;

internal static int Gender = 20;

internal static int Maritialstatus = 21;

public static List<string[]> ParseCSVFile(string path, Boolean hasHeaders)

{

List<string[]> CSVRows = new List<string[]>();

int rowNumber = 0;

using (StreamReader inputFile = new StreamReader(path))

{

string line;

string[] line1;

while ((line = inputFile.ReadLine()) != null)

{

String pattern = ",(?=(?:[^\"]*\"[^\"]*\")*(?![^\"]*\"))";

Regex r = new Regex(pattern);

line1 = r.Split(line);

if (hasHeaders != true || rowNumber != 0)

{

CSVRows.Add(line1);

}

rowNumber++;

}

return CSVRows;

}

public HcmWorkers()

{

InitializeComponent();

}

public void createHcmWorker(String[] _WorkerData)

{

HcmWorkerImportServiceClient hcmSvcClient = new HcmWorkerImportServiceClient();

AxdHcmWorkerImport workerDocument = new AxdHcmWorkerImport();

AxdEntity_HcmWorker worker = new AxdEntity_HcmWorker();

AxdEntity_HcmWorker[] workerList = new AxdEntity_HcmWorker[1];

AxdEntity_HcmWorkerTitle workerTitle = new AxdEntity_HcmWorkerTitle();

AxdEntity_DirPerson_DirPerson person = new AxdEntity_DirPerson_DirPerson();

AxdEntity_DirPersonName personName = new AxdEntity_DirPersonName();

AxdEntity_HcmPersonDetails personDetails = new AxdEntity_HcmPersonDetails();

AxdEntity_HcmPersonPrivateDetails personPrivateDetails = new

AxdEntity_HcmPersonPrivateDetails();

AxdEntity_HcmEmployment employment = new AxdEntity_HcmEmployment();

AxdEntity_HcmEmploymentDetail employmentDetail = new

AxdEntity_HcmEmploymentDetail();

AxdEntityKey_DirNameAffix[] affix = new AxdEntityKey_DirNameAffix[2];

AxdEntity_DirPartyPostalAddressView[] postalAddView = new

AxdEntity_DirPartyPostalAddressView[1];

postalAddView[0] = new AxdEntity_DirPartyPostalAddressView()

{

LocationName = "EmployeeAddr",

BuildingCompliment = "EmplBuildCompliment",

City = _WorkerData[City],

State = _WorkerData[State],

ZipCode = _WorkerData[ZIPCode],

Street = _WorkerData[Streetname],

CountryRegionId = _WorkerData[Country],

Roles = "Home",

IsPrimary = AxdExtType_LogisticsIsPrimaryAddress.Yes

};

//Add the party Address to the person

person.DirPartyPostalAddressView = postalAddView;

//Create a contact for the person. You can add a loop and add as many address and

//types you want to here

AxdEntity_DirPartyContactInfoView[] contactList = new

AxdEntity_DirPartyContactInfoView[5];

contactList[0] = new AxdEntity_DirPartyContactInfoView()

{

LocationName = "Employee Telephone",

//Value of locator will vary by type.

Locator = _WorkerData[phone],

IsPrimarySpecified = true,

IsPrimary = AxdEnum_NoYes.Yes,

TypeSpecified = true,

Type = AxdEnum_LogisticsElectronicAddressMethodType.Phone,

Roles = "Business"

};

contactList[1] = new AxdEntity_DirPartyContactInfoView()

{

LocationName = "Employee Mobile",

Locator = _WorkerData[mobile],

IsPrimarySpecified = true,

IsPrimary = AxdEnum_NoYes.Yes,

TypeSpecified = true,

Type = AxdEnum_LogisticsElectronicAddressMethodType.Phone,

Roles = "Business"

};

contactList[2] = new AxdEntity_DirPartyContactInfoView()

{

LocationName = "Employee Fax",

Locator = _WorkerData[Fax],

IsPrimarySpecified = true,

IsPrimary = AxdEnum_NoYes.Yes,

TypeSpecified = true,

Type = AxdEnum_LogisticsElectronicAddressMethodType.Fax,

Roles = "Home"

};

contactList[3] = new AxdEntity_DirPartyContactInfoView()

{

LocationName = "Employee email",

Locator = _WorkerData[Bemail],

IsPrimarySpecified = true,

IsPrimary = AxdEnum_NoYes.Yes,

TypeSpecified = true,

Type = AxdEnum_LogisticsElectronicAddressMethodType.Email,

Roles = "Home"

};

contactList[4] = new AxdEntity_DirPartyContactInfoView()

{

LocationName = "Personal email",

Locator = _WorkerData[Pemail],

IsPrimarySpecified = true,

IsPrimary = AxdEnum_NoYes.No,

TypeSpecified = true,

Type = AxdEnum_LogisticsElectronicAddressMethodType.Email,

Roles = "Home"

};

//Add the contacts to the person

person.DirPartyContactInfoView = contactList;

personName.LastName = _WorkerData[LastName];

personName.FirstName = _WorkerData[firstname];

personName.MiddleName = _WorkerData[Middlename];

//Assign PersonName to DirPersonName

person.DirPersonName = personName;

person.HcmPersonDetails = personDetails;

DateTime convertedDate2 = DateTime.Parse(_WorkerData[Birthday]);

System.DateTime univDateTime2 = convertedDate2.ToUniversalTime();

personPrivateDetails.BirthDate = univDateTime2;

personPrivateDetails.BirthDateSpecified = true;

//Assign person private Details to the person

person.HcmPersonPrivateDetails = personPrivateDetails;

person.ProfessionalTitle = _WorkerData[Title];

//Assign the person to the worker

worker.DirPerson = person;

//Create the employment array for the worker

AxdEntity_HcmEmployment[] employmentList = new AxdEntity_HcmEmployment[1];

//Set the employment ValidTo and ValidFrom Fields

AxdExtType_HcmEmploymentValidFrom employmentValidFrom = new

AxdExtType_HcmEmploymentValidFrom();

//employmentValidFrom.Value = Convert.ToDateTime(_WorkerData[Joindate]);//UtcNow.AddYears(-5);

DateTime convertedDate = DateTime.Parse(_WorkerData[Joindate]);

System.DateTime univDateTime = convertedDate.ToUniversalTime();

employmentValidFrom.Value = univDateTime;

AxdExtType_HcmEmploymentValidTo employmentValidTo = new

AxdExtType_HcmEmploymentValidTo();

//Set the properties to the employment object

employment.ValidFrom = employmentValidFrom;

// employment.ValidTo = employmentValidTo;

employment.LegalEntity = "HYD";

employment.EmploymentType = AxdEnum_HcmEmploymentType.Employee;

//Create an employment Detail object and set the start date

AxdExtType_HcmEmploymentStartDateTime employmentStartDate = new

AxdExtType_HcmEmploymentStartDateTime();

// AxdExtType_Hcm transitiondate = new AxdExtType_EndDateTime();

//transitiondate.Value = DateTime.Parse(_WorkerData[]);

DateTime convertedDate1 = DateTime.Parse(_WorkerData[Joindate]);

System.DateTime univDateTime1 = convertedDate.ToUniversalTime();

employmentStartDate.Value = univDateTime;

employmentDetail.WorkerStartDate = employmentStartDate;

//Assign the Detail to the employment object

employment.HcmEmploymentDetail = employmentDetail;

//Assign the employment object to the employment list

employmentList[0] = employment;

worker.HcmEmployment = employmentList;

//Assign values to the worker title object

AxdExtType_HcmEmploymentSeniorityDateTime seniorityDateEDT = new

AxdExtType_HcmEmploymentSeniorityDateTime();

// seniorityDateEDT.Value = DateTime.UtcNow.AddYears(1);

// workerTitle.SeniorityDate = seniorityDateEDT;

workerTitle.OfficeLocation = "Room101";

//Assign worker Title to Worker

worker.HcmWorkerTitle = workerTitle;

//Set the Personnel number. This must be unique for each worker record.

worker.PersonnelNumber = _WorkerData[Personalnumber];//"ImportSVCNum1";

//worker.d = _WorkerData[ProdNumber];

affix[0] = new AxdEntityKey_DirNameAffix()

{

AffixType = AxdEnum_DirNameAffixType.PersonalPrefix,

Affix = _WorkerData[sal]

};

affix[1] = new AxdEntityKey_DirNameAffix()

{

AffixType = AxdEnum_DirNameAffixType.PersonalSuffix,

Affix = _WorkerData[Suffix]

};

//Create the worker element in the document

workerDocument.HcmWorker = new AxdEntity_HcmWorker[1];

//assign the worker to the document

workerDocument.HcmWorker[0] = worker;

workerDocument.DocPurpose = AxdEnum_XMLDocPurpose.Original;

workerDocument.DocPurposeSpecified = true;

//Call the create on the service with the worker document

EntityKey[] ek = hcmSvcClient.create(null, workerDocument);

}

private void button1_Click(object sender, EventArgs e)

{

//Read in your .csv file however you want to

//This is just provided as a reference

List<string[]> HcmData = ParseCSVFile("D:\\Employee_Singu.csv", true);

foreach (string[] HcmMasterData in HcmData)

{

createHcmWorker(HcmMasterData);

}

Data import in ax 2012 - Vendor

2012-07-23T18:46:00.000+05:30

Vendor import

Inbound port of the vendor service

To call the service, you need to expose the service on a new inbound port in Microsoft Dynamics AX.

1. Click System administration >Setup > Services and Application Integration Framework > Inbound ports, and then click New.

2. Give the new port a name, such as Vendor Services.

3. Enter a description.

4. Under Service Contract Customizations, click Service Operations. The Select service operations form opens.

5. Select the vendVendTableService operations, move them to the Selected operations pane, and then click Close.

6. In the Inbound ports form, click Activate.

You can now access the service externally by using the WSDL URI.

CSV:

Name	MMS Gen Merchants
KnownAs	MMS Gen Merchants
PhoneticName	MMS Gen Merchants
OrganizationName	MMS Gen Merchants
NameAlias	MMS Gen Merchants
CustGroup	IT
SalesGroup
DlvMode
InvoiceAddressType
PostalLocationName	Primary
Postalstreet	Marol Maroshi
PostalBuildingCompliment
PostalPOBox
PostalCity	Mumbai
PostalState	MH
PostalZip	2219099
PostalCountry	IND
PostalRoles	Delivery;Invoice;Business
IsPostalPrimary	Yes
ContactLocationName	Primary Phone
Locator
ContactType	Phone
ContactRoles	Business
IsContactPrimary	yes

Set up the vendor service reference in Visual Studio

1. Open Visual Studio, and create a new project.

2. Add a new service reference by using the WSDL URI for the vendor service from the Inbound ports form.

3. Add a Using statement for the service reference.

Code:

using System;

using System.Collections.Generic;

using System.ComponentModel;

using System.Data;

using System.Drawing;

using System.Linq;

using System.Text;

using System.Windows.Forms;

using Vendors.VendServiceReference;

using System.IO;

using System.Text.RegularExpressions;

namespace Vendors

{

public partial class Vendor : Form

{

internal static int NameIndex = 0;

internal static int KnownAsIndex = 1;

internal static int PhoneticNameIndex = 2;

internal static int OrganizationNameIndex = 3;

internal static int NameAliasIndex = 4;

internal static int CustGroupIndex = 5;

internal static int SalesGroupIndex = 6;

internal static int DlvModeIndex = 7;

internal static int InvoiceAddressTypeIndex = 8;

internal static int PostalLocationNameIndex = 9;

internal static int PostalstreetIndex = 10;

internal static int PostalBuildingComplimentIndex = 11;

internal static int PostalPOBoxIndex = 12;

internal static int PostalCityIndex = 13;

internal static int PostalStateIndex = 14;

internal static int PostalZipIndex = 15;

internal static int PostalCountryIndex = 16;

internal static int PostalRolesIndex = 17;

internal static int IsPostalPrimaryIndex = 18;

internal static int ContactLocationNameIndex = 19;

internal static int LocatorIndex = 20;

internal static int ContactTypeIndex = 21;

internal static int ContactRolesIndex = 22;

internal static int IsContactPrimaryIndex = 23;

internal static int VendAccountNum = 24;

internal static int VendCurrency = 25;

internal static int InvoiceAccount = 26;

internal static int UPSzone = 27;

internal static int SalestaxGroup = 28;

internal static int PricesInclSalestax = 29;

internal static int CalculateWithholdingTax = 30;

internal static int Warehouse = 31;

internal static int PurchaseOrderpricesAmount = 32;

internal static int Fax = 33;

internal static int Email = 34;

internal static int TermsofPayment = 35;

internal static int Methodofpayment = 36;

internal static int Mobilephone = 37;

internal static int InternetAddress = 38;

public Vendor()

{

InitializeComponent();

}

public static List<string[]> ParseCSVFile(string path, Boolean hasHeaders)

{

List<string[]> CSVRows = new List<string[]>();

int rowNumber = 0;

using (StreamReader inputFile = new StreamReader(path))

{

string line;

string[] line1;

while ((line = inputFile.ReadLine()) != null)

{

String pattern = ",(?=(?:[^\"]*\"[^\"]*\")*(?![^\"]*\"))";

Regex r = new Regex(pattern);

line1 = r.Split(line);

if (hasHeaders != true || rowNumber != 0)

{

CSVRows.Add(line1);

}

rowNumber++;

}

return CSVRows;

}

private void button1_Click(object sender, EventArgs e)

{

//VENDOR MASTER CREATION

VendTableServiceClient vendSvcClient = new VendTableServiceClient();

List<string[]> VendData = ParseCSVFile("D:\\Vendors.csv", true);

foreach (string[] vendor in VendData)

{

AxdVendTable AxdVendor = new AxdVendTable();

Vendors.VendServiceReference.AxdEntity_DirPartyTable_DirPartyTable dirPartyTable = new Vendors.VendServiceReference.AxdEntity_DirPartyTable_DirPartyTable();

AxdEntity_VendTable VendTable = new AxdEntity_VendTable();

AxdEntity_VendTable[] vendorList = new AxdEntity_VendTable[1];

EntityKey[] entityKey; Vendors.VendServiceReference.AxdEntity_DirPartyTable_DirOrganization org = new Vendors.VendServiceReference.AxdEntity_DirPartyTable_DirOrganization()

{

KnownAs = vendor[KnownAsIndex],

PhoneticName = vendor[PhoneticNameIndex],

OrganizationName = new Vendors.VendServiceReference.AxdEntity_OrganizationName[1],

NameAlias = vendor[NameAliasIndex],

Name = vendor[NameIndex]

};

Vendors.VendServiceReference.AxdEntity_OrganizationName orgName = new Vendors.VendServiceReference.AxdEntity_OrganizationName()

{

Name = vendor[OrganizationNameIndex]

};

//Assign organization name to the base organization.

org.OrganizationName[0] = orgName;

//Add an address to the org. You can add a loop and add as many address and types you want to here

Vendors.VendServiceReference.AxdEntity_DirPartyPostalAddressView[] postalAddView = new Vendors.VendServiceReference.AxdEntity_DirPartyPostalAddressView[1];

postalAddView[0] = new Vendors.VendServiceReference.AxdEntity_DirPartyPostalAddressView()

{

LocationName = vendor[PostalLocationNameIndex],

BuildingCompliment = vendor[PostalBuildingComplimentIndex],

City = vendor[PostalCityIndex],

State = vendor[PostalStateIndex],

ZipCode = vendor[PostalZipIndex],

Street = vendor[PostalstreetIndex],

CountryRegionId = vendor[PostalCountryIndex],

Roles = vendor[PostalRolesIndex],

IsPrimary =

(Vendors.VendServiceReference.AxdExtType_LogisticsIsPrimaryAddress)Enum.Parse(typeof(Vendors.VendServiceReference.AxdExtType_LogisticsIsPrimaryAddress), vendor[IsPostalPrimaryIndex])

};

//Add the party Address to the Organization

org.DirPartyPostalAddressView = postalAddView;

Vendors.VendServiceReference.AxdEntity_DirPartyContactInfoView[] contactList = new Vendors.VendServiceReference.AxdEntity_DirPartyContactInfoView[5];

contactList[0] = new Vendors.VendServiceReference.AxdEntity_DirPartyContactInfoView()

{

LocationName = vendor[ContactLocationNameIndex],

Locator = vendor[LocatorIndex],

IsPrimarySpecified = true,

IsPrimary = (Vendors.VendServiceReference.AxdEnum_NoYes)Enum.Parse(typeof(Vendors.VendServiceReference.AxdEnum_NoYes),

vendor[IsContactPrimaryIndex]),

TypeSpecified = true,

Type = (Vendors.VendServiceReference.AxdEnum_LogisticsElectronicAddressMethodType)Enum.Parse(typeof(Vendors.VendServiceReference.AxdEnum_LogisticsElectronicAddressMethodType), vendor[ContactTypeIndex]),

Roles = vendor[ContactRolesIndex]

};

contactList[1] = new Vendors.VendServiceReference.AxdEntity_DirPartyContactInfoView()

{

LocationName = "Fax",

Locator = vendor[Fax],

TypeSpecified = true,

Type = AxdEnum_LogisticsElectronicAddressMethodType.Fax,

Roles = vendor[ContactRolesIndex]

};

contactList[2] = new Vendors.VendServiceReference.AxdEntity_DirPartyContactInfoView()

{

LocationName = "E-mail",

Locator = vendor[Email],

TypeSpecified = true,

Type = AxdEnum_LogisticsElectronicAddressMethodType.Email,

Roles = vendor[ContactRolesIndex]

};

contactList[3] = new Vendors.VendServiceReference.AxdEntity_DirPartyContactInfoView()

{

LocationName = "Mobile phone",

Locator = vendor[Mobilephone],

TypeSpecified = true,

Type = AxdEnum_LogisticsElectronicAddressMethodType.Phone,

Roles = vendor[ContactRolesIndex]

};

contactList[4] = new Vendors.VendServiceReference.AxdEntity_DirPartyContactInfoView()

{

LocationName = "Internet address",

Locator = vendor[InternetAddress],

TypeSpecified = true,

Type = AxdEnum_LogisticsElectronicAddressMethodType.URL,

Roles = vendor[ContactRolesIndex]

};

//Add the contacts to the organization

org.DirPartyContactInfoView = contactList;

VendTable.AccountNum = vendor[VendAccountNum];

VendTable.Currency = vendor[VendCurrency];

VendTable.VendGroup = vendor[CustGroupIndex];

VendTable.DlvMode = vendor[DlvModeIndex];

VendTable.InvoiceAccount = vendor[InvoiceAccount];

VendTable.FreightZone = vendor[UPSzone];

VendTable.TaxGroup = vendor[SalestaxGroup];

VendTable.InclTaxSpecified = true;

VendTable.InclTax = (AxdExtType_InclTax)Enum.Parse(typeof(AxdExtType_InclTax), vendor[PricesInclSalestax]);

VendTable.TaxWithholdCalculateSpecified = true;

VendTable.TaxWithholdCalculate = (AxdExtType_NoYesId)Enum.Parse(typeof(AxdExtType_NoYesId), vendor[CalculateWithholdingTax]);

VendTable.InventLocation = vendor[Warehouse];

VendTable.PurchAmountPurchaseOrderSpecified = true;

VendTable.PurchAmountPurchaseOrder = (AxdExtType_PurchAmountPurchaseOrder)Enum.Parse(typeof(AxdExtType_PurchAmountPurchaseOrder), vendor[PurchaseOrderpricesAmount]);

VendTable.PaymTermId = vendor[TermsofPayment];

VendTable.PaymMode = vendor[Methodofpayment]; VendTable.DirPartyTable = new Vendors.VendServiceReference.AxdEntity_DirPartyTable_DirPartyTable[1];// AxdEntity_DirParty_DirPartyTable[1];

VendTable.DirPartyTable[0] = org;

//Add the specific customer to the list

vendorList[0] = VendTable;

AxdVendor.VendTable = vendorList;

//Set the header fields

AxdVendor.DocPurpose = Vendors.VendServiceReference.AxdEnum_XMLDocPurpose.Original;

AxdVendor.DocPurposeSpecified = true;

entityKey = vendSvcClient.create(null, AxdVendor);

}

AX2012 Cumulative Update 3

2012-07-15T17:59:00.000+05:30

Microsoft Dynamics AX2012 Cumulative Update 3

Cumulative Update 3 for AX 2012 is released on June 28, 2012. This release includes all previously released Cumulative Updates for Dynamics AX 2012 plus additional hotfixes.

installation of Microsoft Dynamics AX2012 Cumulative Update 3 (6.0.1108.670).

SALE ORDER from X++

2012-07-07T17:53:00.000+05:30

Create SALE ORDER from code in dynamics ax

static void createSalesTable(CustAccount _custAccount) {

SalesTable salesTable;

NumberSeq NumberSeq;

;

NumberSeq = NumberSeq::newGetNumFromCode(SalesParameters::numRefSalesId().numberSequence);

salesTable.SalesId = NumberSeq.num();

salesTable.initValue();

salesTable.CustAccount = _custAccount;

salesTable.initFromCustTable();

salesTable.insert();

}

static void createSalesLine(SalesId _salesId, ItemId _itemId) {

SalesLine salesLine;

;

salesLine.clear();

salesLine.SalesId = _salesId;

salesLine.ItemId = _itemId;

salesLine.createLine(NoYes::Yes, // Validate

NoYes::Yes, // initFromSalesTable

NoYes::Yes, // initFromInventTable

NoYes::Yes, // calcInventQty

NoYes::Yes, // searchMarkup

NoYes::Yes); // searchPrice

}

Posting Invoice from Sales order

The FormLetter classes define how to post different status updates against sales orders and purchase orders. When a posting is being performed is that the parm tables are Populated with data, and then the update itself is performed.

Post the Invoice from sales order

static void postSalesInvoice(Args _args)

// Define a classvariable according to the

// type of posting being performed

SalesFormLetter_Invoice invoice;

SalesTable salesTable;

// Select the salesTable to update

salesTable = SalesTable::find(“CEU-545352″);

// Create a new object of the SalesFormLetter_Invoice

// by using the construct-method in SalesFormLetter

invoice = SalesFormLetter::construct(DocumentStatus::Invoice);

// Post the invoice

invoice.update(salesTable,

SystemDateGet(),

SalesUpdate::All,

AccountOrder::None,

false,

true); // Set to true to print the invoice

The below picture shows the class hierarchy of FormLetter with all its subclasses: we can easily custamize the above logic to post different status updates against sales orders.

Sales (Confirmation, Picking list, Packing slip, Invoice )

Print Performa Sales Invoice

static void Test_SalesFormLetter(Args _args)

    SalesFormLetter letter=SalesFormLetter::construct(DocumentStatus::Invoice);

    SalesTable sale = SalesTable::find('ORDR00000229');

    ttsBegin;

    letter.update(sale, systemDateGet(), SalesUpdate::PickingList, AccountOrder::None,

true, true);

    ttsCommit;

Print Sales Invoice

public void printInvoiceReport(PurchId _purchId)

    ReportRun report;

    RecordSortedList List = new RecordSortedList(tableNum(VendInvoiceJour));

    VendInvoiceJour VendInvoiceJour = VendInvoiceJour::findFromPurchId(_purchId);

    PurchFormLetter PurchFormLetter;

    if (VendInvoiceJour.RecId)

        report = new ReportRun(new Args(ReportStr(PurchInvoice)));

        List.ins(VendInvoiceJour);

        report.args().object(List);

        report.query().interactive(false);

        report.report().interactive(false);

        report.args().parmEnum(0);

        report.args().parmEnumType(920);

        report.args().name("KeepSettings");

        report.args().caller(PurchFormLetter);

        report.setTarget(PrintMedium::Screen);

        report.printJobSettings().setTarget(PrintMedium::Screen);

        report.printJobSettings().preferredTarget(PrintMedium::Screen);

        PurchFormLetter     =   PurchFormLetter::construct(DocumentStatus::Invoice);

        PurchFormLetter.updatePrinterSettingsFormLetter(

  report.printJobSettings().packPrintJobSettings(),

  PrintSetupOriginalCopy::Original);

        PurchFormLetter.updatePrinterSettingsFormLetter(

  report.printJobSettings().packPrintJobSettings(),

  PrintSetupOriginalCopy::Copy);

        // print invoice

        VendInvoiceJour.printJournal(PurchFormLetter);

Create return Order from code

static void SR_CreateReturnOrderAfterInvoice(Args _args)

{

CustInvoiceJour _invoiceRec;

str _returnReason;

CustInvoiceTrans custInvoiceTrans;

SalesLine salesLine;

SalesTable newRetOrder;

CustInvoiceJour custInvoiceJour;

SalesTable createReturnOrderHeader(CustInvoiceJour invoiceRec)

{

SalesTable old, newRec;

boolean bChecksOk = true;

;

old = SalesTable::find(invoiceRec.SalesId);

newRec.initReturnFromSalesTable(old);

newRec.CustAccount = old.CustAccount;

newRec.initFromCustTable();

newRec.CustInvoiceId = invoiceRec.InvoiceId;

newRec.ReturnDeadline = today();

newRec.ReturnReasonCodeId = ’21′; // Defective

newRec.SalesType = SalesType::ReturnItem;

newRec.SalesTaker = SysCompanyUserInfo::current().EmplId;

if ( newRec.ReturnReasonCodeId == ” && CustParameters::find().ReturnOrdersReasonReq ||

newRec.ReturnReasonCodeId != ” && !ReturnReasonCode::exist(newRec.ReturnReasonCodeId) )

{

checkFailed(strfmt(“@SYS26332″, fieldid2pname(tablenum(SalesTable), fieldnum(SalesTable, ReturnReasonCodeId))));

bChecksOk = false;

}

if ( bChecksOk && newRec.validateWrite())

{

newRec.insert();

}

else

{

throw error(“@SYS18722″);

}

return newRec;

}

ttsbegin;

// first we need to create the sales order header for the return order

select custInvoiceJour where custInvoiceJour.RefNum == RefNum::SalesOrder && custInvoiceJour.InvoiceId == ’101231′;

newRetOrder = createReturnOrderHeader(custInvoiceJour);

while select * from custInvoiceTrans where custInvoiceTrans.SalesId == custInvoiceJour.SalesId

&& custInvoiceTrans.InvoiceId == custInvoiceJour.InvoiceId

&& custInvoiceTrans.InvoiceDate == custInvoiceJour.InvoiceDate

&& custInvoiceTrans.numberSequenceGroup == custInvoiceJour.numberSequenceGroup

{

// now we need to populate all the necessary fields for the new salesline

// using the existing invoice and the new sales order

salesLine.initFromCustInvoiceTrans(custInvoiceTrans);

salesLine.initFromSalesTable(newRetOrder);

// udpate the quantity

salesLine.ExpectedRetQty = -custInvoiceTrans.Qty;

if (salesLine.ExpectedRetQty > 0)

{

error(“@SYS53512″);

ttsabort;

}

// set the quantity and amount fields

salesLine.LineAmount = salesLine.returnLineAmount();

salesLine.SalesQty = 0;

salesLine.InventTransIdReturn = custInvoiceTrans.InventTransId;

//create the line

salesLine.createLine(true, false, false, false, false, false, false, false, salesLine.InventTransId);

// clear the buffer

salesLine.clear();

}

ttscommit;

info(strfmt(‘Newly created return order is %1′, newRetOrder.SalesId));

}

Referred from : http://msdax.wordpress.com/

AX 2012 Installation and Configuration

2012-07-03T17:05:00.001+05:30

AX 2012 Reporting services extensions and Analysis services configuration

AX 2012 - Reporting services extensions

Download the Microsoft Dynamics AX 2012 Feature pack from customer/partner source.

Click on the Validate sytem requirments

Select the option, which you want to install and verify all the pre requisites are installed properly.

After installation of pre requisite components, install the “Microsoft Dynamics AX Components”

Select the “Reporting services extensions” check box and proceed

Select the SQL Reporting services instance name.

If you want to deploy the reports after installation select the “deploy reports” option.

How to deploy SSRS reports Manually ?

Deploy reports using MS dynamics ax 2012 power shell:

Start -> All programs -> MS dynamics AX 2012 -> MS dynamics AX 2012 Management shell

execute the below mentioned command

AX 2012 - Analysis services configuration

Install the analysis services on SQL server instance and install the “analysis services configuration” from the AX 2012 setup

Complete the prerequisites

Select the SQL Server analysis service instance service name

Enter the business connecter proxy account username and password

Connect to AX 2012 Database to configure the Analysis services

Deploy the Analysis Services Project:

Select the deploy option and "Next"

If you have any quries regarding the Installation and configuration, let me know...

AX 2012 - What's New for Developers

2012-07-02T16:33:00.000+05:30

This Article describes the new and enhanced features for developers that are available in Microsoft Dynamics AX 2012. Updated and additional developer documentation for Microsoft Dynamics AX can be found at the Microsoft Dynamics AX Developer Center on the Microsoft Developer Network (MSDN).

Analytics for Developers in MS DAX 2012
Analysis services project wizard	Model data using tables and views make it easy to customize cubes
	It is easy to deploy the default cubes
	It is easy to create new analysis service project
Date Dimensions using gregorian calendars	Define gregorian Calendar in calender builder form in ax that you can use as date dimenssions in analysis service project

AOS and DB for Developers in MS DAX 2012
Valid Time State Tables	"ValidTimestateFieldType" proerty on table to make the table valide time state table. Ax will add the "ValidFrom" and "ValidTo" columns that track a date range in each row.
Unit of work Class	Mangae the operation sequence and transaction intigrity for row by row database deletes, inserts and updates.
Inheritance among the tables	Just as an X++ class could inherit from another X++ class in Microsoft Dynamics AX 2009, a table can inherit from another table in Microsoft Dynamics AX 2012. As in earlier releases, the Common table is still the base table of every table. A table that inherits from a base table is called a derived table. The terms parent table and child table describe foreign key relationships, not inheritance.
Full text index	Craete a full text index on a table
TempDB temporary tables	In the properties for a table in the Application Object Tree (AOT), the TableType property is now an enum property. The enum value InMemory is the legacy type of temporary table that is hosted in the client. The enum value TempDb is the new type of temporary table that is hosted in the TempDb database of the underlying Microsoft SQL Server. TempDB temporary tables can be joined with regular tables on the database tier. Joining TempDB temporary tables with regular tables often improves performance and simplifies the programming model.
Computed columns in views	Have a computed column in a view.
Filters in outer join	Filtering the result set from an outer join can reduce the number of rows that the database server must scan.
Add a Having Clause to a Query in the AOT	Use the AOT to add a having clause on the data source for a query.
Effect of Disabling a Table	Retain the table in the underlying Microsoft SQL Server database when the table is disabled in Microsoft Dynamics AX.


Best practices for Developers in MS DAX 2012
Best Practise	Best Practice Checks Changed from Warnings to Errors.

Client for Developers in MS DAX 2012
Forms	Set the Style property of a form. Use the table of contents pattern for small forms that display data on one or more tabs. Specify whether the query from the parent form is copied to a child form.
Controls	· Use a DropDialogButton control. · add an action pane strip that provides access to the actions that are associated with the form. · You can replace a surrogate foreign key with one or more data fields. · You can add and use .NET controls in forms. · To display data in a chart, you use the MSChart .NET control. · Disable or hide controls that are not used in a specified country or region.
Data sources	· The replacement fields are not loaded until they are visible. · Controls can be bound to fields from the derived tables in an inheritance hierarchy. · When you save a record that changes multiple tables, the changes are combined into a single transaction that is initiated by AOS.
Parts	· You can create or update a FactBox that appears on a list page or in a form. · Use an existing form as a FactBox. · Create a Cue in the Application Object Tree (AOT) that uses an existing query.
Search	To make a form or report appear in search results, you create a menu item, and add the search terms that you want to associate with the specified form or report.


Enterprise portal for Developers in MS DAX 2012
Microsoft SharePoint 2010	· Enterprise Portal uses SharePoint Foundation 2010 or SharePoint Server 2010. · Microsoft SharePoint 2010 provides core features that are used by Enterprise Portal, such as document libraries that store Enterprise Portal pages
Microsoft Visual Studio 2010	Enterprise Portal integrations are developed with Visual Studio 2010.
Support for Microsoft Dynamics AX 2012 Features	· Enterprise Portal supports tables that are structured into a table hierarchy. · Enterprise Portal supports tables that use surrogate keys. · Enterprise Portal uses the new security model.
List Page Framework	A list page can be created and used in both the Microsoft Dynamics AX client and Enterprise Portal.
Services Framework	Enterprise Portal uses the Microsoft Dynamics AX services to access data and metadata.
Search	Search for data in Microsoft Dynamics AX.
Pluggable Authentication	You can use Windows Live ID accounts for external users.
Proxy Support	Proxies can be used throughout Microsoft Dynamics AX. This includes Enterprise Portal
Cross-reference Support	The cross-reference tool supports Enterprise Portal resources.

Morph X Development for Developers in MS DAX 2012
Models and the Model Store	The following model features are new: · A model is a set of model elements in a specific layer. · Each layer consists of one or more models. One of the models is generated by the system. For example, VAR Model is the model that is generated for the VAR layer. · Each element in a layer must belong to only one model. · Models can be exported to a file artifact that is called a model file. Model files have an .axmodel extension. A model file is like an .aod file from earlier versions, but the names and numbers are not limited. Models in the model store can be exported to model files and imported from model files. Model files can be signed, and the signature is verified when the model files are installed. · Model files replace .aod files as installation artifacts. · Models in the SQL Server–based model store replace .aod files that were used at run time. · Development is performed in the current model in any given layer. All development work, such as creating a new class, becomes part of the current model in the current layer. You can change the current model by clicking the name of the current model on the status bar, similarly to the way that you change the current company. · Any element that is created in the current layer can easily be moved to another model in the same layer. · The Application Object Tree (AOT) shows you which model a particular element belongs to, in addition to the layer tags. · The additional folder capabilities for version control have been renamed models, and the capabilities have been extended. When you add an element to version control, the element is added to the version-model. · You can generate a MorphX project that contains all of the application objects in the model. A new Model management submenu on the Tools menu contains many tools that you can use to work with models and the model store. · The new SysModel* system tables provide a view of the metadata that is associated with models. These tables enable you to use model metadata in select statements in your X++ code. For example, you can use the SysModelElementLabel table to retrieve the string value for the label that is associated with a particular model element.
Object IDs	Object IDs are 32 bits long.
AxUtil Command-Line Utility and PowerShell Cmdlets	AxUtil is a command-line utility that you can use to import and export .axmodel files into the SQL Server model store. You can also use AxUtil to delete one or more models, create new empty models, and list all of the models in a layer. All of the capabilities of AxUtil are also exposed as PowerShell CmdLets.
Development Workspace	In Microsoft Dynamics AX 2012, the development experience is separated from the application experience as a new workspace. You now use the development environment when you write code in Microsoft Dynamics AX.
Some Layers Have Been Renamed	In Microsoft Dynamics AX 2012, 16 layers are supported. Because multiple solutions can be installed in parallel into the same layer, some layers have been renamed to emphasize the new usage.


MorphX Tools for Developers in MS DAX 2012
X++ Editor	The code editor is now based on the code editor for Visual Studio, and includes many of the same features and shortcuts. The following new and changed features are available: · The method list displays all methods in the class. You can scroll through the list by using the mouse, and the size of the list is resized. · Basic editing has improved. For example, you can comment or uncomment code, move code by using a drag-and-drop operation, swap characters, delete a whole line, and change text in many other basic ways. · Code navigation is more similar to code navigation in Visual Studio. For example, you can use the Home key, navigate line ends, and go to the next or previous word as you do in Visual Studio. · It is easier to select code by using the margin or by using block selection, and word selection is improved. · Code rendering is improved. For example, the value of a label is displayed when you rest the mouse pointer on the label, and an indicator in the margin tracks your changes. Additionally, line numbers are displayed, the font is improved, there is more syntax coloring, and you can view whitespace. · You can search for code incrementally. Search uses .NET regular expressions. · IntelliSense has been improved. IntelliSense now includes word completion, tooltips that display the XML documentation comments for a method or class, and help for multiline parameters. · Errors in code are underlined by using a wavy line. When you rest the mouse pointer on the wavy line, the error message for the compiler is displayed. Code breakpoints can be toggled in the margin.
Code Upgrade Tools	Use the Detect Code Upgrade Conflicts tool to analyze a system, and then create projects that contain the application objects that must be upgraded manually. Use the EDT Relation Migration tool to move the previous relations that are defined under the EDT nodes in the AOT to the table nodes.

Reporting for Developers in MS DAX 2012
Use labels in a report.	Using AX labels in reports, you no longer have to create a .resx file for each language which improves the time to deploy reports. Only one report definition per report is needed.
Use data on your report that is based on specific time periods.	Create a report that has data that is based on specific time periods. The reporting framework supports date effective data.
Define secure reports based on the role of the user	Report security is based on the user role and you can specify with more precision which data is displayed on a report.
Create an unlimited number of dimensions attributes.	Create an unlimited number of dimension attributes using the dimension framework. Additional flexibility is enabled by the ability to combine dimension attributes.
Access cross-reference information for a Reporting Services report.	You can see what data the report is using and what AOT objects are using the report.
AX_CompanyName report parameter has been updated to reflect changes in Ax 2012	You can add organization parameters to your report such as Operating Unit or Department. The AX_CompanyName parameter was created by the Microsoft Dynamics AX framework for queries that are company specific. This change reflects the organization hierarchy product wide feature
Use the improved drill-through functionality on reports.	Using table and field names reduces ambiguity and errors and Launching a new window for a linked report is consistent with expected behavior and improves the usability of reports that have links.
Modify queries used by reports	Allows you to filter and sort data on reports.
Control report destination settings	The PrintDestinationSettings class was added to allow you to programmatically change print settings such as saving to a file.
Create auto-reports	An auto-report is a report that is generated by clicking Print on a form. The data on the form is displayed on the report. Auto-reports are generated by using the Reporting Services framework for Microsoft Dynamics AX.
Print reports in a batchCreate auto-reports	You can use the Reporting Services framework to print a batch of reports, print a report on a recurring basis, and schedule a report to be printed during off peak hours.

Secuity for Developers in MS DAX 2012
Create security permissions on individual AOT elements.	The new security system takes less work to maintain as your business evolves. Security constructs can be reused more easily. Data that the user does not have permissions to see is never sent from Application Object Server (AOS) to the client, and appropriate security does not rely on forms for enforcement.
Implement security	Security policies can restrict access to table rows, based on foreign key relationships between tables. One security policy can replace several RLS specifications. After a security policy is created in the AOT and assigned to a user role, the system enforces the policy. Therefore, developers do not have to add calls to a security system in their code. The RLS feature will be removed from a future version of the product.


Services and AIF for Developers in MS DAX 2012
Services Enhancements	X++ classes and members can be exposed as services and service operations by using attributes.
	Any .NET or X++ native type (such as a str or an int) can be used as a data contract. Any class that uses the AIF data contract attributes can be used as a data contract.
	Data contracts can now use X++ container types and strongly typed X++ collections such as a Set or an Array.
Service Groups	A service group is a collection of services that are frequently consumed and managed together. All services in a service group are published in a single Web Services Definition Language (WSDL) file
Support for Data Model Changes	AIF fully supports data model features to make data contracts easier to use.
Support for Non-XML Files	AIF can work with non-XML data, and you can handle data transformations within Microsoft Dynamics AX.
Consume external web services from X++ without adding a service reference in the AOT.	The Service References node has been removed from the AOT. You add a service reference in a .NET project and then add that project to the model store. Then you can access the external service from X++ code.

Visual studio tools for Developers in MS DAX 2012
Application Explorer	The Application Explorer displays a view of the AOT within the Visual Studio IDE.
Managed Code Business Logic	You can write business logic in .NET languages and manage this code in Microsoft Dynamics AX just as you would with X++ classes.
Proxies	When you add an X++ class or table to a project by using the Application Explorer, a proxy for that class is created internally by the system. After the proxy is created, that type is then available as a strong type and features like IntelliSense are available.
Deployment	Managed code assemblies are deployed to the location that you specify: client, server, Reporting Services or Enterprise Portal. You can specify where the assembly is deployed by setting project properties in Visual Studio. After you deploy an assembly, you can then see the managed code classes via IntelliSense and call the managed code from X++.
Cross-Reference Tool	In order to see cross-references for a Visual Studio project, you must first add the project to the model store by using the Application Explorer. After you add a project to the model store, the project and its cross-reference information are updated every time you build the project.
Code Upgrade Tools	Microsoft Dynamics AX supports layer-based customizations for managed code. Therefore, the tools that enable developers to find and resolve conflicts that result from those customizations also support managed code. The code upgrade tools enable developers to detect and resolve conflicts between two versions of Microsoft Dynamics AX.

Workflow for Developers in MS DAX 2012
Advanced Workflow Controls	By using advanced workflow controls, you can create more complex workflows than you could in Microsoft Dynamics AX 2009.
Line Item Workflow	You can now create a line item workflow that is configured and instantiated for different types of line item records that are in a header-to-line relationship. For example, a header can be a sales order that has sales order lines, or a purchase order that has purchase order lines.
Automated Workflow	You can now create an automated workflow element. An automated workflow element is a type of workflow element that does not involve human interaction.
Workflow Editor	It is now much simpler to create a workflow by using a drag-and-drop user interface.
Workflow Templates Are Now Workflow Types	Workflow templates have been renamed workflow types. Workflow types are building blocks that can be used to create customized workflows that enforce business policies. Workflow types are defined in the Application Object Tree (AOT) at design time. The metadata from workflow types is used by the customer to create a workflow configuration. For example, workflow tasks can have metadata that indicates the class that is used when the due date of the task is calculated.

X++ for Developers in MS DAX 2012
.NET Proxies to X++ Classes	A .NET proxy is a .NET managed class that represents a class or table that exists in Microsoft Dynamics AX. Your managed program can call proxy methods, just as your X++ code can call methods on a table or class. The C# compiler detects errors in your calls to the proxy at compile time. You can use this early-bound programming model to fix errors in your code before the code is run. The internal logic of the proxy class uses the late-bound programming model of .NET Business Connector. However, the tools that generate the source code of the proxy have been rigorously tested.
X++ Attributes	X++ classes and methods can now have metadata in the form of attribute classes. An attribute class is any non-abstract class that inherits from the SysAttribute class. Detailed metadata is assigned through the constructor of the attribute class. Tables and interfaces can also have attribute classes.
New Expression Operators in X++ for Inheritance	When the is operator is used, your code can test whether a particular downcast assignment would be valid.
Events in X++	The event programming model can reduce the chance that your customizations are affected by upgrades to your program or to Microsoft Dynamics AX. The pre-method and post-method events are stable points at which custom code can run.
X++ Compiled to .NET CIL is Faster	Some X++ batch jobs can now complete in much less time. All X++ code that runs on the AX32.exe client still runs as interpreted p-code. However, all batch jobs now run as Microsoft.NET Framework CIL, which is often much faster than p-code. The X++ developer must now complete the extra step of compiling X++ p-code to CIL. To compile p-code to CIL, right-click AOT, and then click Add-ins > Incremental CIL generation from X++. Next, if the installation uses multiple instances of Application Object Server (AOS), all AOS instances must be stopped and then restarted. This causes the AOS instances to load the updated assembly. Finally, a service or a batch job must run the X++ code that was compiled to CIL. Services and batch jobs now run only as CIL.