web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Creating validation logic for excel import of Project Item requirements

(0) ShareShare
ReportReport
Posted on by 506

I need to create an import from excel facility for Project item requirements.

The data will be staged and validated before import. 

I have looked at the form in AX (ProjSalesItemReq) for creating item requirements and there is a lot of validation code.

The requirement is that the validation must be as per this form. What is the best approach?

At the moment I am running in debug and following the datasource.create() method on SalesLine which has taken me through a lot of data processing.

My next steps will be to change the values that will be imported and check the validation logic that is executed by the form.

By tracking the code I hope to implement the required validation logic myself. Is this the best approach?

I am fine with the import process, it is the design and implementation of the validation that I would like some advice on.

thanks.

*This post is locked for comments

I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    301,069 Super User 2025 Season 2 on at

    Hi _MGP,

    Did you have a look at the Data Import Export Framework? This has the technology to import in a staging and during staging to target run all (or selected) validations. I'm not sure if your version has this module and which exact entities are supported. If there is no entity for the item requirements, you can create a new one yourself.

  • _MGP Profile Picture
    506 on at

    Hi André,

    Thanks for your reply and suggestions.

    An existing excel import routine has already been built for a different data import using the RunBase framework to capture the excel file, display staged data with result of validation and allow import in another step. To make it consistent for users I was going to follow similar approach but tailor the validation class for Item requirements.

    I think Item requirements are just Sales Lines but the logic in the Sales order line entity does not directly (or indirectly) assist in creating them as the mappings are more or less generic here.

    Even if I followed a DIXF approach then perhaps I could customise the existing entity to create a line using the values from a staging record? However, I believe it would still require following my current approach of tracking the creation of IR's via the AX form to figure out the logic / data processing required to validate and setup the target data?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans