Creating 1-1 Nested CDT from Existing Tables--Avoiding Extra DB Column in Parent

RE: Creating 1-1 Nested CDT from Existing Tables--Avoiding Extra DB Column in Parent

Evan Rust — Wed, 05 Dec 2018 20:56:09 GMT

Thank you. I suspected that I would not be able to "pick" my parent in this situation. As a workaround, I have created a database view.

RE: Creating 1-1 Nested CDT from Existing Tables--Avoiding Extra DB Column in Parent

omere0001 — Wed, 05 Dec 2018 20:47:28 GMT

Unless your Person CDT/table has a field for accountID your Person CDT cannot be the parent. From what you listed it looks like your parent CDT would be Account and Person would be the nested CDT joined on the personId column.

Also, if you have a one to many relationship, you should keep cascadeType=REFRESH. If you use cascadeType=ALL and delete the parent entity, all the child entities will also be deleted.

RE: Creating 1-1 Nested CDT from Existing Tables--Avoiding Extra DB Column in Parent

anjannat — Wed, 05 Dec 2018 01:44:19 GMT

Hi, you can use @JoinColumn annotation in parent cdt to link between parent and child cdt

Below is sample one, you can change it accordingly if it is one-one,

<xsd:element maxOccurs="unbounded" minOccurs="0" name="person" type="tns:Account">

<xsd:annotation>

<xsd:appinfo source="appian.jpa">@OneToMany(cascade=CascadeType.ALL, indexed=false) @JoinColumn(name="personId")</xsd:appinfo>

</xsd:annotation>

</xsd:element>

Thank you,

Anji