cancel
Showing results for 
Search instead for 
Did you mean: 

Previous (day) message remains

MariusStoica
Active Participant
0 Kudos

Hi gurus,

I encounter an error while developing apps for SUP 2.1.2 / 2.1.3

I've created an OData service with one entity "ConfProd" and using the "GET_ENTITY" method I should receive as response in the app, only 1 message (2 - blue).

Unfortunately there are 2 messages:

Message 1 (red) is an "old" message. Didn't figure out yet how, why or exactly when it appears, and message 2 which is the correct answer in my case.

I found out that:

1.  after deploying again the MBO and the app, the message 1 (red) disappears

2.  in back-end, only 1 message is appended to the entity  (2 - blue)

3.  in GW there is only 1 message "exiting"  (2 - blue)

Can anyone give me a reason to why does this happens ? Or/and how can I solve this?

Thanks,

Marius

Accepted Solutions (1)

Accepted Solutions (1)

midhun_vp
Active Contributor
0 Kudos

What is the cache group you are using ? How you are passing the load parameters ?

If you are using on demand cache group with load parameter mapped to PK, you will get unexpected results in mobile. In the case of on demand cache it is recommended to use load parameter mapped to sync key or load parameter mapped to PK with "partition by requester and device ID" option checked.

Midhun VP

MariusStoica
Active Participant
0 Kudos

That was it ! "partition by requester and device ID"

Answers (0)