[jira] [Updated] (CAMEL-14480) camel-salesforce - Duplicate Properties between Relationship Name and Child Relationship Name
[ https://issues.apache.org/jira/browse/CAMEL-14480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14480: Summary: camel-salesforce - Duplicate Properties between Relationship Name and Child Relationship Name (was: Duplicate Properties between Relationship Name and Child Relationship Name) > camel-salesforce - Duplicate Properties between Relationship Name and Child > Relationship Name > - > > Key: CAMEL-14480 > URL: https://issues.apache.org/jira/browse/CAMEL-14480 > Project: Camel > Issue Type: Bug > Components: camel-salesforce >Affects Versions: 3.0.1 >Reporter: Dhimitraq Jorgji >Priority: Major > Fix For: Future > > > When two SObjects have a one-to-one relationship and one of the objects in > that relationship does not have a plural form the resulting DTO has duplicate > properties causing compilation to fail. Similarly when the SObject with no > plural form has a hierarchical child parent relationship with itself. > > EX: *Equipment__c_* _has a relationship with *Yard_Slot*__*_c*__, were they > both lookup to each other for a 1-to-1 relationship. *Yard_Slot_*_*_c.java_* > _DTO has duplicate properties because both its Relationship **and its Child > Relationship are named *Equipment*_*_r*. > > EX2: *Equipment__c_* _has a parent/child relationship with itself causing > both the Parent and Child relationship names to be *Equipment*_*_r.* > > **Salesforce allows and handles both these scenarios properly, however the > resulting DTO classes do not compile because of the duplicate properties and > duplicate getters. > > An easy fix would be to always append the suffix *List* on child relationship > properties in DTO. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14480) camel-salesforce - Duplicate Properties between Relationship Name and Child Relationship Name
[ https://issues.apache.org/jira/browse/CAMEL-14480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14480: Fix Version/s: (was: Future) 3.x > camel-salesforce - Duplicate Properties between Relationship Name and Child > Relationship Name > - > > Key: CAMEL-14480 > URL: https://issues.apache.org/jira/browse/CAMEL-14480 > Project: Camel > Issue Type: Bug > Components: camel-salesforce >Affects Versions: 3.0.1 >Reporter: Dhimitraq Jorgji >Priority: Major > Fix For: 3.x > > > When two SObjects have a one-to-one relationship and one of the objects in > that relationship does not have a plural form the resulting DTO has duplicate > properties causing compilation to fail. Similarly when the SObject with no > plural form has a hierarchical child parent relationship with itself. > > EX: *Equipment__c_* _has a relationship with *Yard_Slot*__*_c*__, were they > both lookup to each other for a 1-to-1 relationship. *Yard_Slot_*_*_c.java_* > _DTO has duplicate properties because both its Relationship **and its Child > Relationship are named *Equipment*_*_r*. > > EX2: *Equipment__c_* _has a parent/child relationship with itself causing > both the Parent and Child relationship names to be *Equipment*_*_r.* > > **Salesforce allows and handles both these scenarios properly, however the > resulting DTO classes do not compile because of the duplicate properties and > duplicate getters. > > An easy fix would be to always append the suffix *List* on child relationship > properties in DTO. -- This message was sent by Atlassian Jira (v8.3.4#803005)
