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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Problem with Data mana...
Finance | Project Operations, Human Resources, ...
Suggested Answer

Problem with Data managment Import after updating DataEntityView

(5) ShareShare
ReportReport
Posted on by Rudi Hansen 4,075
I am having a problem with Import after making changes to a Composite Data Entity.
 
The customer has a custom Composite Data Entity that used the Depriciated Data Entity SalesOrderHeaderV2Entity.
So on the Composite Data Entity, I changed the Data Entity SalesOrderHeaderV2Entity to SalesOrderHeaderV3Entity, and I also changed SalesOrderLineV2Entity to SalesOrderLineV3Entity.

I did a build and Sync Database, and also ran "Truncate entity list" and "Refresh entity list"
 
Then I tried importing an xml file that the customer used before, but I got this error:
<?xml version="1.0"?><Errors><Error><ErrorCode>-2146233088</ErrorCode><SubComponent>Microsoft.Dynamics.AX.Framework.Tools.DMF.SSISHelper</SubComponent><Description>DMF2060 -    at Microsoft.Dynamics.AX.Framework.Tools.DMF.SSISHelper.DMFXmlCompositePackageImport.AddDataFlowComponent(Package _Package)
   at Microsoft.Dynamics.AX.Framework.Tools.DMF.SSISHelper.DMFPackageControllerCompositeEntity.CreateAndExecutePackage()
   at DMFExecutePackage.PackageCreator.processCompositeEntity()
   at DMFExecutePackage.Program.Main(String[] args)</Description></Error><Error><ErrorCode>-2146233088</ErrorCode><SubComponent>Microsoft.Dynamics.AX.Framework.Tools.DMF.SSISHelper</SubComponent><Description>DMF2060 -    at Microsoft.Dynamics.AX.Framework.Tools.DMF.SSISHelper.DMFXmlCompositePackageImport.UpdateSourceProperties(IDTSComponentMetaData100 flatFileSourceComponent, CManagedComponentWrapper srcFlatFileInstance, String name, Package _Package)
   at Microsoft.Dynamics.AX.Framework.Tools.DMF.SSISHelper.DMFXmlCompositePackageImport.AddDataFlowComponent(Package _Package)</Description></Error><Error><ErrorCode>-1073676279</ErrorCode><SubComponent>Microsoft.SqlServer.DTSPipelineWrap</SubComponent><Description>Exception from HRESULT: 0xC0010009 -    at Microsoft.SqlServer.Dts.Pipeline.Wrapper.IDTSOutputColumnCollection100.get_Item(Object Index)
   at Microsoft.Dynamics.AX.Framework.Tools.DMF.SSISHelper.DMFXmlCompositePackageImport.UpdateSourceProperties(IDTSComponentMetaData100 flatFileSourceComponent, CManagedComponentWrapper srcFlatFileInstance, String name, Package _Package)</Description></Error></Errors>
Please ensure that the schema of the mapping matches that of the staging table and the import file. It is essential to verify that the import file contains the same fields as specified in the mapping for the data entity. If there are any columns set in the mapping that are not present in the import file, you have two options: either provide a value for the column in the import file, or remove the column from the mapping altogether. Additionally, if there is a field present in the mapping that does not exist in the staging table, it should be removed from the mapping to resolve the issue.
'0' 'CustomerSalesOrderCompositeEntity' record(s) inserted in staging
 
I have tried going through all the Mappings on the project and everything seems to be ok, and I also tried to Export the package from production, and go through the files in it making sure that any references to the V2 entities was changed to V3
Perhaps I also have to mention that the package contains an xsl file with transforms, and I also checked that file and everything seems to be fine.

So I am kind of stuck, since the error message mentions that perhaps I am having a problem with the mappings or missing fields, but does not mention witch mappings of field might be the problem.
And I have checked in the mappings that the fields there do exist.

Is there any way of debugging the process to get som actual help to what the problem might be?

 
Categories:
Dynamics 365 Finance
I have the same question (2)
  • AR-01121610-0 Profile Picture
    AR-01121610-0 4,967 Moderator on at
    Hy,
    my experience with the SO composite entity is quite the same and time consuming.
    After a long period of try and error I had sucess with the SalesOrderHeaderV3Entity and SalesOrderLineHeaderV2Entity.
    Reduced to a less fields as possible, and I set SalesOrdreNumber, LineNumber and INVENTORYLOTID to Autogenerated in the project.
     
    Hope this helps.
     
     
  • Suggested answer
    Alireza Eshaghzadeh Profile Picture
    Alireza Eshaghzadeh 14,686 Super User 2025 Season 2 on at
    Hi,

    The error message you provided is related to the DMF service connection. You need to verify if the service is up and running.

    The other issue is already addressed in Microsoft Learn. You can find more details here:

     Data management error descriptions and known limitations - Finance & Operations | Dynamics 365 | Microsoft Learn
  • Rudi Hansen Profile Picture
    Rudi Hansen 4,075 on at
    Alireza:
    The DMF Service is running, and the only thing I can find in the page you reference to is a description of the error i get.
    DMF2060 A mapped field isn't present in the import file or staging table. Remove the unused field from the mapping, or include it in the import file. When you customize an entity, you must add fields to both the entity view and its staging table.
     
    And again, that is not really helpful since it just says basically something is wrong, but not what and how to fix it.
    As I said I really need som help on how to get a more detailed description of what fields are the problem, some sort of way to debug the error.
     
    Andreasraithel:
    I have tried but the fields i have in my XML file are all needed and it also looks like they all ether exists in the staging tables, or has transforms to the right fields in the transforms file.
  • Suggested answer
    Waed Ayyad Profile Picture
    Waed Ayyad 9,039 Super User 2025 Season 2 on at
    Hi,
     
    Did you check the mapping in DMF and the Fields on your XML file?
     
    Try to export one Sales order and then compare it with your XML file that you want to import, also you should make sure about number seq fields like sales order number. If you don't set the value of it in the XML, you should change it to auto generated in the Mapping.
     
     

    Thanks,

    Waed Ayyad

    If this helped, please mark it as "Verified" for others facing the same issue

     
     
  • Waed Ayyad Profile Picture
    Waed Ayyad 9,039 Super User 2025 Season 2 on at

    Hi, 

    Is your issue resolved? If yes, mark the answers that helped you as verified. 

    Thanks,

    Waed Ayyad

  • Suggested answer
    Alireza Eshaghzadeh Profile Picture
    Alireza Eshaghzadeh 14,686 Super User 2025 Season 2 on at
    Hi,
    According to the latest error message, as Waed mentioned, please check the mapping in the import file. The error could be related to fields that lack values in the staging table, which might be causing the import to fail.
  • Rudi Hansen Profile Picture
    Rudi Hansen 4,075 on at
     
    I have looked at the files in the package, and I not so far been able to find any fields in them that is not in the staging tables.
     
    The CustomerSalesOrderCompositeEntity.xml has no fields in it that does not exist in the staging tables.
     
    I am currently looking through the tranform file, and it also does not look like that one had any problems.
    Resources\CustomerSalesOrderCompositeEntity\{F23A1DD1-D257-4CBD-A971-B66AE5267894}_CustomerSalesOrderCompositeEntityImportTransformV9.xsl
  • Sanny Profile Picture
    Sanny 10 on at
    Hi, I have the same issue. Was there something that solved this issue?
  • Suggested answer
    Sagar121 Profile Picture
    Sagar121 877 on at
    Hi, 
     
    Probably check the staging table here. You can also skip staging table it not at all required. 
  • Suggested answer
    Cyrille Nembot Profile Picture
    Cyrille Nembot 149 on at

    Based on your description, you're
    encountering issues after updating a composite data entity from V2 to V3
    entities. The error suggests a schema mismatch between your import file
    and the entity mapping, but doesn't specify exactly where the problem
    lies.

    From past experience, try the following:

    1. Validate the Entity Mapping

    • Check field mappings:
      Even though you've reviewed them, double-check that all fields in the
      V3 entities are properly mapped, especially any new required fields that
      might exist in V3 but not in V2.

    • Compare staging tables: The error mentions staging tables - verify that the staging table structure matches your entity mapping.

    2. Debugging Techniques

    Use the Data Import/Export Framework (DIXF) Logs

    • Check the Event Log
      in Dynamics 365 for more detailed error information (Event Viewer >
      Applications and Services Logs > Microsoft > Dynamics >
      AX-DIXF)

    • Look at the DMFExecutionLog table in the database for more detailed error information

    Enable SSIS Debugging

    1. In the DIXF parameters, enable Verbose logging

    2. Run the import again and check the SSIS logs for more detailed error information

    Schema Validation

    1. Export the current entity schema:

      • Go to Data management > Framework parameters > Entity settings

      • Select your entity and click "Download entity schema"

      • Compare this with your import file schema

    2. Generate a new template:

      • Create a fresh export of the V3 entity to get the correct schema

      • Compare this with your existing import file

    3. Specific Checks for Your Scenario

    1. XSLT Transformations:

      • Even though you checked the XSL file, validate that it's properly transforming all V2 field names to their V3 equivalents

      • Test the XSL transformation separately to ensure it works as expected

    2. Required Fields:

      • V3 entities might have new mandatory fields that weren't present in V2

      • Check the entity definitions for any new required fields

    3. Staging Table Cleanup:

      • Try truncating the staging tables manually before the import

      • SQL: TRUNCATE TABLE DMFSTAGING_[YourEntityName]

    4. Alternative Approaches

    1. Create a new composite entity from scratch using V3 entities and compare the mappings with your modified one.

    2. Use the OData endpoint for testing:

      • Try importing through the OData endpoint to see if you get better error messages

      • This can help isolate whether the issue is with the entity or the import process

    3. Break down the composite:

      • Temporarily simplify your composite entity to just one component entity to isolate where the problem occurs

    5. Technical Deep Dive

    The error 0xC0010009 typically indicates a column mismatch in SSIS. To get more details:

    1. SQL Server Profiler:

      • Trace the SSIS package execution to see exactly where it fails

    2. DTEXEC with logging:

      • If you can access the generated SSIS package, run it manually with detailed logging:

      text
       
    1. dtexec /f "YourPackage.dtsx" /l "*D.*"

    Final Recommendation

    The most likely causes are:

    1. A field in your mapping that doesn't exist in the V3 entity

    2. A required field in V3 that's not provided in your import file

    3. An XSL transformation that's not properly converting all V2 fields to V3

    Start
    by generating a fresh export from the V3 entity and compare its
    structure with your import file. This should highlight any schema
    differences that need to be addressed.

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Abhilash Warrier Profile Picture

Abhilash Warrier 677 Super User 2025 Season 2

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 442 Super User 2025 Season 2

#3
Martin Dráb Profile Picture

Martin Dráb 339 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans