Skip to main content
Question

CASCADE References in Data Migration Manager error

  • November 5, 2024
  • 0 replies
  • 48 views

msurasky-price
Sidekick (Customer)
Forum|alt.badge.img+8

The following print-screen show the state of one of my Output Containers, as you can see:

  1. It refers to IDENTITY_PAY_INFO
  2. It’s key (COMPANY, IDENTITY, PARTY_TYPE_DB) is: TESTCO, ABC0001 and CUSTOMER (respectively)
  3. Is in Approved state

In addition to that, IDENTITY_PAY_INFO is referred by another table PAYMENT_WAY_PER_IDENTITY. On that table, It is expected that the field PARTY_TYPE_DB should exist in IDENTITY_PAY_INFO, as you can see in this Target Table Definition.

With this information in mind… then why this row in PAYMENT_WAY_PER_IDENTITY failing if the corresponding record already exist in  IDENTITY_PAY_INFO when I validate basic data?

To me the information is already there, so it shouldn’t fail.

Also, what does the word “CASCADE” represent in the Reference column in the target table definition (as in this case where the reference is “IdentityPayInfo(company,identity)/CASCADE”)?

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings