Data Management Package - declare auto generated column

(0) Share

Report

Posted on by Community Member

We are importing a data package into the system via the Data Management Framework.

How do we define a column that is auto-generated within the package. It appears as though we can define it in the manifest.xml, but we don't know the schema definitions.

(our hunch is that is should reside in the <EntityMapList>.....just don't know how its supposed to look)

The package works fine if we manually define the auto-generated column mappings.....but our goal is to have the package stand alone without manual intervention.

Note: The import file is an XML-attribute file

Thanks and any help is appreciated

Categories:

Data Integration

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Daniel Weichsel on at

Like (0)

Report
It's in the manifest.xml as you suspect. Change the IsAutoGenerated value inside the EntityMap element corresponding to the field you want to auto-generate:

<EntityMap> <ArrayIndex>0</ArrayIndex> <EntityField>VENDORACCOUNTNUMBER</EntityField> <EntityFieldConversionList i:nil="true" /> <IsAutoDefault>false</IsAutoDefault> <IsAutoGenerated>true</IsAutoGenerated> <IsDefaultValueEqualNull>false</IsDefaultValueEqualNull> <UseTextQualifier>false</UseTextQualifier> <XMLField>VENDORACCOUNTNUMBER</XMLField> </EntityMap>

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
That's what we were hoping for..... here is the mapping that we created for the "Project Expense Journals" entity.

.... <EntityMapList> <EntityMap> <ArrayIndex>0</ArrayIndex> <EntityField>JournalBatchNumber</EntityField> <EntityFieldConversionList i:nil="true" /> <IsAutoDefault>false</IsAutoDefault> <IsAutoGenerated>true</IsAutoGenerated> <IsDefaultValueEqualNull>false</IsDefaultValueEqualNull> <UseTextQualifier>false</UseTextQualifier> <XMLField>JournalBatchNumber</XMLField> </EntityMap> </EntityMapList> .....

And here's a sample of our actual import file:

<Document> <ExpenseJournalHeaderEntity DESCRIPTION="test description" JOURNALNAMEID="test journal name id"> <ExpenseJournalLineEntity ...></ExpenseJournalLineEntity> </ExpenseJournalHeaderEntity> </Document

We're able to import the package but when viewing the mapping the JournalBatchNumber doesn't show.

So we also tried including a JournalBatchNumber tag with a blank string (JOURNALBATCHNUMBER="") ....but the autogenerated is never checked. We tried setting the other values to true....but it never seems as though the EntityMap definitions take.

Is there some other parameter or flag in the Manifest that needs to be modified so that the EntityMap is applied?

EDIT: We've been able to make this work with just the Project Expense Journal Header.....but doesn't seem to work with the composite entity of Project Expense Journals. Is there any way around this?

Was this reply helpful? Yes No
Rich 326 on at

Like (0)

Report

Appreciate this is an old post, but I'm just hitting the same issue attempting to import project expense journals. This thread from October 2019 suggests that the manifest file doesn't support auto-generation for composite entities. I've got it to work through the UI without issue, setting the header auto-generate before import, but package upload doesn't retain that mapping. Whilst logging a question with MS, Copilot pointed to the known limitations page, though I don't see it explicitly mentioned there.

Was this reply helpful? Yes No