Import data from another instance of Microsoft Dynamics AX
Important
This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.
Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
You can use the export operation in Microsoft Dynamics AX to export a subset of data from a single company. You can then use the import operation to move the exported data to another company. This company can be in the same partition, in another partition that is in the same instance of Microsoft Dynamics AX, or in another partition that is in another instance of Microsoft Dynamics AX.
Before you read this topic, we strongly recommend that you read the information in Plan data import, export, and migration.
Before you begin, make sure that the current company account is the account that you want to import data into.
Note
Microsoft Dynamics AX data export and import are designed to export and import tables in companies. The doInsert, doUpdate, and doDelete methods that are called by the export and import functionality cannot be overwritten. Therefore, any application logic that is written at the table level is not called during export and import operations.
For more information about how import operations are processed, see Use DAT and DEF files to export and import data.
Reliability and performance
Data import is a resource-intensive activity that can affect data integrity.
Warning
Data import operations cannot be rolled back.
Consider the following recommendations before you begin a data import:
If you plan to perform many import operations, we recommend that you put the data file and transaction log file for Microsoft SQL Server on separate spindles to minimize contention. For more information about best practices for the placement of SQL Server log files and data files, see Storage Top 10 Best Practices.
We recommend that you or the database administrator actively manage the size of the transaction log file after large import operations. During the import process, Microsoft Dynamics AX creates staging tables, and then drops them after the import is completed. Therefore, the transaction log file is likely to grow significantly during a data import. For more information about how to manage the size of the transaction log file, see Managing the Size of the Transaction Log File.
We strongly recommend that you shut down Enterprise Portal for Microsoft Dynamics AX and Microsoft SharePoint products during a data import, so that the import is the only active process that affects data. Otherwise, data can be corrupted.
Back up both the source data and the target data.
Perform all data imports outside core working hours.
Security for importing data
When you export or import Microsoft Dynamics AX tables, the folder that you store the tables in must have permissions that are appropriately restricted. Access to the data in the following tables can expose confidential information or security information:
SysConfig
SysUserInfo
UserInfo
Note
Tables that are protected by extensible data security are protected when they are exported. However, if the same policy is not set up on the system that you import the tables into, the tables are not protected when they are imported. We strongly recommend that you configure the same policies for extensible data security on both the system that you import tables into and the system that you export tables from, to help protect your data.
Import data
Click System administration > Common > Data export/import > Import.
On the General tab, select the definition group or data file that you want to import.
On the Advanced tab, select the options that meet your needs:
Include shared tables – Include tables that are not specific to company accounts.
Note
To import shared tables from a data file or definition group, you must select Include shared tables. Otherwise, even if the definition group or data file contains shared tables, the shared tables are not imported.
By default, Include shared tables is selected.
If you import a dataset that includes shared data more than one time, for different companies, the shared data for all companies is affected by the import operation.
Include system tables – Import data that is stored in system tables.
Note
In general, we recommend that you do not import system tables because the imported data can conflict with the data that is already configured in the Microsoft Dynamics AX environment.
To import system tables from a data file or definition group, you must select Include system tables. Otherwise, even if the definition group or data file contains system tables, the system tables are not imported.
Update existing record – Update data during the import.
The system checks whether each record in the import file already exists. If a record already exists, the existing data is overwritten with new data from the import file. This method is time-consuming, but it is useful when the purpose of the data import is to update existing information.
Tables that do not have unique indexes do not support the Update existing record option.
Important
If you are importing AIF or services-related tables, such as AifInboundPort, do not select Update existing record.
Note
If you select both Update existing record and Include system tables, cross-company data is updated.
On the Batch tab, select the batch group that you want the import file to be processed with. All import jobs are run as batch tasks.
Note
Batch tasks for data import are run on Application Object Server (AOS). Therefore, the AOS service account must have access to the file that you are importing from. Make sure that you place the file in a location that the AOS service account has access to.
When the data import is completed, the Infolog displays information about the number of records that were imported. The Select tables form also displays import information on the Log files tab.
Tables that you should not import data in to
Several tables cannot be exported from Microsoft Dynamics AX. These tables are known as blocked tables. Data can be imported into blocked tables. However, we recommend that you not import data into blocked tables because most of these tables contain metadata. Therefore, if you import data into these tables, your Microsoft Dynamics AX installation can be corrupted. The following list includes the tables that you should not import data in to.
LanguageTable |
SqlDictionary |
SecurableObject |
SqlParameters |
SecurityCondition |
SqlStatistics |
SecurityEntryPointLink |
SqlStorage |
SecurityPermission |
SysExpImpRecords |
SecurityRole |
SysInheritanceRelations |
SecurityRoleCondition |
SysLastValue |
SecurityRoleExplodedGraph |
SysLicenseCodeSort |
SecurityRolePermissionOverride |
SysOld2NewRecId |
SecurityRoleTaskGrant |
SysSetupLog |
SecuritySubRole |
SystemSequences |
SecuritySubTask |
SysTraceTable |
SecurityTask |
SysXppAssembly |
SecurityTaskEntryPoint |
TimeZonesList |
SecurityTaskExplodedGraph |
TimeZonesRulesData |
SecurityTaskPermission |
UtilElements |
SecurityTaskPermissionOverride |
UtilIdElements |
SqlDescribe |
UtilIdElementsOld |
UtilModels |