Hello, We are building a set of CDTs and we have the following case.

...nition of "xParent2".

Thanks.

Can you attach the xsd. Nesting beyond a single level is generally not recommended.

I have attached the XSDs of all the CDTs in the graph tree. The problem we are facing with the foreign key columns is in the database table of the CDT MA_PricingExceptions.

This is the structure of the graph tree of these CDTs:
MA_InterestInstalations
->MA_Solutions(Array)
->MA_ePos_Pricing
->MA_PricingExceptions(Array)
->MA_POS_Pricing
->MA_PricingExceptions(Array)

Today, we made changes to the MA_PricingExceptions, MA_ePos_Pricing and MA_POS_Pricing CDTs where we simply added an extra field in each of the 3 CDTs. After we executed the Impact Analysis on all these and all references were updated throughout the application, the Data Store would NOT be verified eventhough the added fields were added to the database tables. The reason the Data Store can not be verified is because it is adding an extra foreign key column to the MA_PricingExceptions table pointing to the MA_ePos_Pricing table. The MA_PricingExceptions table already has a foreign key column pointing to the MA_ePos_Pricing table.

I would like to know the logic behind creating foreign key columns from a CDT graph because in this case i fear that every time a change is made the Data Store will not be verified for the reason i described above.

As a note, the structure of the CDT graph, in terms of its relationships has not changed since Friday when I first posted this issue of ours.

MA_InterestInstalations.xsd

MA_Solutions.xsd

MA_ePos_Pricing.xsd

MA_POS_Pricing.xsd

MA_PricingExceptions.xsd

Hi thanosm, In MA_Solutions.xsd the relationship is not defined for MA_ePos_Pricing,

<xsd:element form="qualified" name="MA_ePos_Pricing" type="acquiring1:MA_ePos_Pricing"/>

Can you please check if we need to include the relationship like ..

<xsd:appinfo source="appian.jpa">
@OneToMany(indexed=false)
</xsd:appinfo>

It looks like you might need to include maxOccurs="unbounded" in your reference to MA_ePos_Pricing on MA_Solutions, as well as the reference to MA_POS_Pricing in MA_InterestInstalations

Hello, narasimhaadityac and tom.ryan thank for your input.
The MA_ePos_Pricing CDT has a OneToOne reference to MA_Solutions. The same holds for MA_POS_Pricing and MA_InterestInstalations. For that reason, in the XSDs you only see the field "MA_ePos_Pricing" being of type "MA_ePos_Pricing". In the database, the MA_Solutions table has a foreign key column that points to the MA_ePos_Pricing table and this relationship is fine. The same holds for the relationship between MA_POS_Pricing and MA_InterestInstalations.

Our problem is specific to MA_PricingExceptions and the relationships between this one type and the types MA_ePos_Pricing and MA_POS_Pricing. As you can see, MA_PricingExceptions is one level down in the tree and part of the types MA_ePos_Pricing and MA_POS_Pricing.