https://community.sap.com/t5/application-development-and-automation-discussions/unable-to-get-data-from-extensible-entity-using-odata/m-p/453774#M13968 <P>No , Its a standard camel case notation in which the getter (and setter) are generated.As it is an extensible attribute odata need to understand this and get the attribute using the get/set method defined in eclipselink-orm.xml file..which is not happening</P> <P>Best regards</P> Tue, 25 Jul 2017 08:27:51 GMT former_member331791 2017-07-25T08:27:51Z https://community.sap.com/t5/application-development-and-automation-discussions/unable-to-get-data-from-extensible-entity-using-odata/m-p/453772#M13966 <P>We are working on implementing an application using Olingo (2.0.6) , Springboot (1.3.2) and eclipse link(2.5.0). </P> <P><BR />The application expects entities to be extensible the user should be able to add the columns to the entities in the runtime. <BR />I used the @VirtualAccessMethods as mentioned in the documentation (<A href="http://www.eclipse.org/eclipselink/documentation/2.5/solutions/extensible001.htm">http://www.eclipse.org/eclipselink/documentation/2.5/solutions/extensible001.htm</A>)<BR />The steps mentioned successfully adds the field to the entity in the metadata and also I'm able to save the data in the database programmatically. <BR /><BR />I am facing two issue with the implemention -<BR /><BR />• <STRONG><U>Issue 1 -</U> </STRONG>When I try to do a OData GET request on the extended entity I get an error saying the getter method for the field is missing in the entity. Though ,the extension map contains the data fetched from the database but it is not mapped to the field name in the metadata. <BR /><BR /></P> <UL></UL> <BR />Example --- I added a field 'thebirthplace' in my entity(General_data) mapping to a field EXT_1 in the table. When I make a GET request (localhost:8080/mdm/General_datas) I get the following error <BR />"org.apache.olingo.odata2.jpa.processor.core.access.data.JPAEntityParser:.mdm.entity.General_data.getThebirthplace(). " <BR /> <BR /> <BR />The question is do we need to do the reverse mapping too . Field name -&gt; attribute name. Or am I missing something? <P>Best regards</P> Mon, 24 Jul 2017 15:28:33 GMT https://community.sap.com/t5/application-development-and-automation-discussions/unable-to-get-data-from-extensible-entity-using-odata/m-p/453772#M13966 former_member331791 2017-07-24T15:28:33Z https://community.sap.com/t5/application-development-and-automation-discussions/unable-to-get-data-from-extensible-entity-using-odata/m-p/453773#M13967 <P>Does the case matter? </P> <P><IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/55617-case.jpg" /></P> Tue, 25 Jul 2017 03:59:16 GMT https://community.sap.com/t5/application-development-and-automation-discussions/unable-to-get-data-from-extensible-entity-using-odata/m-p/453773#M13967 Former Member 2017-07-25T03:59:16Z https://community.sap.com/t5/application-development-and-automation-discussions/unable-to-get-data-from-extensible-entity-using-odata/m-p/453774#M13968 <P>No , Its a standard camel case notation in which the getter (and setter) are generated.As it is an extensible attribute odata need to understand this and get the attribute using the get/set method defined in eclipselink-orm.xml file..which is not happening</P> <P>Best regards</P> Tue, 25 Jul 2017 08:27:51 GMT https://community.sap.com/t5/application-development-and-automation-discussions/unable-to-get-data-from-extensible-entity-using-odata/m-p/453774#M13968 former_member331791 2017-07-25T08:27:51Z