Data Migration Framework : Development consideration for custom entity

I have a issue while importing records using custom entity in Dynamics Ax 2012 data migration framework. The custom entity imports only one record from staging table to actual table out of many records.

I come across this blog which explains the resolution for the same:

AX2012R2 Data import/export framework (aka: DMF) import troubles

Database log in dynamics ax 2012

Point to remember,

If you are setting database logging on a table where the table property has "Save data per company = Yes", the log details can be found in the same company where the Create Update Delete operations are made.

If you are setting database logging on a table where the table property "Save data per company = No", the log details can be found in the DAT company.

Dynamics Ax 2012 Data Migration Framework Issue

When you have a  distributive environment whereas , AOS resides in one system and DB in another and you have installed DMF (Beta) tool in AOS system, you may come across an error during previewing the source file in Ax DMF.

Error      Message (10:55:14 am) System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.DTSRuntimeWrap, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.

File name: 'Microsoft.SqlServer.DTSRuntimeWrap, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'

   at Microsoft.Dynamics.AX.DMF.SSISHelper.DMFEntity.ShowPreview()

WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind failure logging.

To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

This error is because of unavailable components of MS SSIS in AOS system. If you look at AOT references:

It has a dependency on SSIS component. To get rid of this error, do the following steps:

1. Stop AOS service

2. Install SSIS components

3. Run the DMF setup wizard (Client and Server) again.

4. Start AOS service.

5. Run full CIL