cancel
Showing results for 
Search instead for 
Did you mean: 

HCI error when we attempt to access ODATA entity

Former Member
0 Kudos

We get the below error in HCI when we attempt to access an ODATA entity:

  • com.sap.gateway.core.ip.component.odata.exception.OsciException: Bad Request : 400 : HTTP/1.1 <?xml version="1.0" encoding="utf-8"?><error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><code>COE_BAD_PROPERTY_EXPRESSION</code><message lang="en-US">[COE0003]Bad property expression: FOLocation/addressState; FOLocation/addressState is not viewable</message></error>

we get this error only with 1 single entity. We're able to access other entities without issues.

Thanks

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Sriprasad, We found out from the API guide, we were looking at the wrong entity. Once we changed the entity, we didn't see this error again. Thanks for taking the time.

Sriprasadsbhat
Active Contributor
0 Kudos

Hello,

Basically this is issue with your SuccessFactors configuration.Ask your SuccessFactors consultant to enable or mark it viewable the field at API level.

Got some KBA on enabling the visibility from API perspective( unfortunately not from field perspective) ,but you need to do it at field level.

https://apps.support.sap.com/sap/support/knowledge/public/en/2148306

Basically this setting needs to be done from SF side not from HCI end.

Regards,

Sriprasad Shivaram Bhat

Former Member
0 Kudos

Sriprasad, bear with the delayed response. Thanks for taking the time. I've requested our EC consultant to check the field properties. Meanwhile, I missed to include this in my initial note. We don't get this error in Boomi when we access the same entity and it works fine. Does HCI alone need this field property set?

Thanks