cancel
Showing results for 
Search instead for 
Did you mean: 

Error with offlinestore with request with XML format

Former Member
0 Kudos

We're using SMP3 SP08 pl1 with iPad application.

We're setting the OfflineStoreOptions with this example Request:

NSString *req6 = @"/ActivityMediaSet()?$format=json";

(....)

[options addDefiningRequestWithName:@"req6" url:req6 retrieveStreams:NO];



This works great! However we want to enable delta tokens and for this is mandatory to use XML format. So, we change the format value:


NSString *req6 = @"/ActivityMediaSet()?$format=xml";


But we receive the offlineStoreOpenFailed event with this message:


"The operation failed due to an error on the server"


If we try the service on a browser with XML and JSON and works fine.

If in iOS we delete the format tag ( NSString *req6 = @"/ActivityMediaSet()"; ), the gateway get the request as JSON format:

If we've delta token disable, we haven't problem with the request. But if we enable, we obtain a message that JSON is not supported for delta token.



1. Do you know why we are getting this error with XML?

2. What kind of log error we've to enable to trace in SMP Server?


Thank you very much.

Accepted Solutions (0)

Answers (2)

Answers (2)

0 Kudos

If the service doesn't have edit links, they need to the exposed and that should fix the issue.

See KBA 2219208

PavelPenaz
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Josue,

Please configure Debug logging for the Offline component in SMP Admin Cockpit - tab Logs / Settings and change Offline line from Error to Debug.

Extract from the blog here:

2. The log trace of offline component with DEBUG level to figure out the bottleneck

Bump up the trace level for offline component. Go to "LOGS" > "SETTINGS" in admin console.

Change the log level of the Offline component to "debug" and the trace "Enabled".

Now the offline component is ready to show the useful info.

The info provides very fine details of the offline store, you'll get clear idea what's happening behind the scenes. The timestamp data also tells you where's the bottleneck is.

Hope this will help in troubleshooting the issue.

All the best!

Pavel