Finance | Project Operations, Human Resources, ...

Data Entity throws error during export or import due to an incorrect method override

(1) Share

Report

Posted on by EK-26061005-0

100

I have ExternalItemId from CustVendExternalItem table in a custom data entity, which needs to insert a new CustVendExternalItem when a new id is entered in the field. I have overriden the postLoad method for this purpose with the following code:

    public void postLoad()
    {
        super();
        CustVendExternalItem custVendExternalItem;
        custVendExternalItem.ModuleType = ModuleInventPurchSalesVendCustGroup::VendGroup;
        custVendExternalItem.CustVendRelation = "Foreign";
        custVendExternalItem.ItemId = this.ItemId;
        custVendExternalItem.ExternalItemId = this.ExternalItemId;
        custVendExternalItem.InventDimId = InventDim::inventDimIdBlank(); // AllBlank
        if (custVendExternalItem.validateWrite())
        {
            custVendExternalItem.insert();
        }

    }

But now the data entity throws "The record already exists" error during export or import (It was working before the override).

All responses (2)

Answers (0)

Suggested answer

Mohamed Amine Mahmoudi 9,738 Super User 2024 Season 2 on at

Like (0)

Report
Data Entity throws error during export or import due to an incorrect method override

Hi,

Try to use write instead insert method.

custVendExternalItem.write();

Best regards,

Mohamed Amine MAHMOUDI
Martin Dráb 230,370 Most Valuable Professional on at

Like (2)

Report

Data Entity throws error during export or import due to an incorrect method override

postLoad() is a completely wrong method for your purpose. It's called for each record loaded from database, therefore your code is trying to insert an CustVendExternalItem record for every row to be exported. Which is a completely wrong thing to do and it's not what you wanted.

First of all, think about whether data management can't create the record for you. If you're sure you need code for that, the correct methods may be mapEntityToDataSource(), insertEntityDataSource() or so. Details depends on your requirements.