A valid primary key was not found on the staging table for this entity ,Entity 'Packing slip' doesn't have primary or unique key. Staging table '' needs to be altered.

(0) Share

Report

Posted on by Vijay Yelmame VY

476

Hi Team,
I am getting warning while adding composite entity to export project.
I have created one header entity from CustPackingSlipJour table and another line entity from CustPackingSlipTrans. Refer below screen shot.

Created composite entity using above 2 entity.

Staging table alos updated and index already created.

Geting below warning while export.

Please suggest the solution.

I have the same question (0)

All responses (9)

Answers (0)

Martin Dráb 237,880 Most Valuable Professional on at

Like (0)

Report

The error message talks about staging table, but you didn't show us staging table at all, just entities.

Also, shouldn't the relation use the entity key of the header entity?

Was this reply helpful? Yes No
Vijay Yelmame VY 476 on at

Like (0)

Report

Hi Martin,

Thank you for the quick reply.

Please find below screen shot for staging tables.

you mean i need to use the entity key of header entity in the relation with line entity ?

Was this reply helpful? Yes No
Martin Dráb 237,880 Most Valuable Professional on at

Like (0)

Report

The error message says that there is no primary or unique key. Please look at it; you didn't mention nor show anytthing on this topic.

Yes, it looks very strange that you define an entity key and then ignore it and use completely different fields that aren't used in any unique key. The purpose of the entity key is uniquelly identify an entity record and you need the same thing in the relation. Ambigious relations are dangerous.

Was this reply helpful? Yes No
Vijay Yelmame VY 476 on at

Like (0)

Report

Hi Martin,
Thank you for the information given for the entity key.

The relation between 2 data sources is below so that I have created same relation on my line entity and the key are added on the entity are the primary key of their respective data sources.

Now i have changed as below but getting same error. I have kept entity refresh i will check once again, but please correct me if i did anything wrong.

staging table

Was this reply helpful? Yes No
Martin Dráb 237,880 Most Valuable Professional on at

Like (0)

Report

You keep ignoring what the error message actual talks about: indexes.

If you want to identify the header entity by SalesId, PackingSlipId and DeliveryDate, then why don't have these fields in the entity key?

Was this reply helpful? Yes No
Vijay Yelmame VY 476 on at

Like (0)

Report

Hi Martin,

I have added above mention fields in entity already.

for header entity

PackingSlipId

salesId

DeliveryDate

CustPackingSlipJourRecId - (Primary index of CustPackingSlipJour)

for Line entity

PackingSlipId

OrigSalesId

DeliveryDate

CustPackingSlipTransRecId (primary index of CustPackingSlipTrans)

On staging as well it is generated. but still i am not able to understand where you exactly telling me to add the above mentioned fields.

Was this reply helpful? Yes No
Martin Dráb 237,880 Most Valuable Professional on at

Like (0)

Report

I'm just saying that the relation should match the entity key.

The error is about an index on a staging table.

Was this reply helpful? Yes No
Vijay Yelmame VY 476 on at

Like (0)

Report

HI Martin,
I have debugged the code and found below from DMFQuickImportExportFormHelper::validateEntityV2()

It is always return false for composite entity because there is no EntityTable set for any composite entity(including standard entities).

Thank you for all the help.

Was this reply helpful? Yes No
Martin Dráb 237,880 Most Valuable Professional on at

Like (1)

Report

That's a for different thing - a validation of the entity. The validation this thread is about (index of staging table) seems to be in DMFEntity.verifyStagingPrimaryKey().

Was this reply helpful? Yes No