Question Re: Invalid Key Name in Key predicate when updating data from SMP offline Native application in Technology Q&A

Invalid Key Name in Key predicate when updating data from SMP offline Native application

Former Member — Fri, 24 Jun 2016 08:33:48 GMT

Hi Experts,

We are developing an SMP based offline Native Android application (SMP 3.0; SDK SP 10 PL10). We are able to

1. Successfully create data in offlinestore (deep insert using batch processing).

1a. Create Object in offlinestore with Temp Object key ID

2. Successfully update the same object header information (example description) in offlinestore (using etags and resourcepath mapping).

3. Following the local create and local update process, we invoke offlinestore.flush() which sends 2 batch request to SAP

3a. SAP OData Service is successfully accepting the create request and creating the Object in SAP tables with actual ID

3b. The second batch request i.e Update request results in error stating "Invalid key name in Key predicate"

Attached screens for reference

Screenshot 1: (Ref: Step 2 above) Data successfully updated in Android native app offline store using eTags and Resourcepath

Screenshot 2: (Ref: Step 3b above) Error in OData service

Can you please suggest way forward

Regards

A Rathi

Re: Invalid Key Name in Key predicate when updating data from SMP offline Native application

Former Member — Thu, 01 Sep 2016 13:24:03 GMT

Hi Anup,

We are facing this issue as well. Did you get a resolution for this issue from SAP? If yes, could you share it with me.

Thanks,
Aditya

Re: Invalid Key Name in Key predicate when updating data from SMP offline Native application

patty_1982 — Wed, 05 Oct 2016 09:13:11 GMT

Hi,

I have the same problem, did you solve it?

Thank you

Patrizia

Re: Invalid Key Name in Key predicate when updating data from SMP offline Native application

Former Member — Wed, 05 Oct 2016 19:07:33 GMT

Hello Patrizia,

We are still having this issue. The only update I have is that I tried updating the SMP 3.0 SDK version to SP12 PL05 and it did not resolve the issue. I have an incident open with SAP to track it but I haven't been able to reproduce consistently.

Regards,
Aditya