Data Import Export Framework – using validation in insert/update

While using the DIXF (data import export framework) tool, I noticed that my selection to use business logic upon insert/update was not happening as I had expected it to. There were two reasons for this.

Class method DMFProductEntityClass.insertUpdate has as input parameters, two booleans called _callInsertLogic and _callValidateLogic. This is all well and good until you see that in line 121, super is called without passing those parameters. Super, which is DMFEntityBase.insertUpdate, certainly expects them as input. So, modify line 121 to pass the parameters. I only see this in the Product entity.

Second, there is a second place where you can and probably should select this option, to validate your data. It is under Entity structure, see screenshot:

EntityLogic

I hope you are enjoying the tool. It’s way better than anything we’ve had before!

Happy DAXing!

Advertisements

About janeteblake

Dynamics AX developer
This entry was posted in AX2012, Bug, Data migration, Dynamics AX. Bookmark the permalink.

2 Responses to Data Import Export Framework – using validation in insert/update

  1. Seth Shaheen says:

    In my experience (without this modification), I had to select the “Run business logic in insert or update method” option on both the processing group entity AND the target entity structure in order for the logic to run.

  2. janeteblake says:

    Yes, Seth, thanks! That’s what I meant to say but didn’t express clearly. I agree!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s