different xhr.responsetext in sharepoint 2016 and 2013

[Dariusz]

Hi 😊

I need some help. I was using kendo for uploading files into sharepoint 2013. After migration to sp 2016 the same code generates different response from server (it is without 'd' and it starts with odata.metadata - the old working one has 'd' and __metadata). Is the odata different and that causes issues? Any help would be appreciated. Thanks.

[Ivan Danchev]

Hi Dariusz,

We are not experts in Sharepoint so we are not sure what has changed in the way the response is returned from the server. Sharepoint's forums would be a better place for this inquiry.

With regard to the Upload, when you return an empty string from the server this signifies success. If you want to return a message, for example an error message, you can either return a string, e.g.:

return Content("my message");

or if you have some error handling you can return the error message like this:

try
{
    // return an empty string
    return Content(string.Empty);
}
catch (Exception ex)
{
    // return the error message

    return Content(ex.Message);
}

The returned message can be then accessed in the Upload's error event handler:

function onError(e) {
    var error = e.XMLHttpRequest.responseText;
    alert(error);
}

Regards,
Ivan Danchev
Progress Telerik

[Dariusz]

Thanks Ivan.

I found out what it was. For future if someone will face this problem he or she has to add to accept header: odata=verbose.

Thanks again and have a nice day 😊

[Ivan Danchev]

Hi Dariusz,

I am glad to hear you were able to identify what was causing the issue. I am sure it would be helpful, in case someone else from the community stumbles upon this problem. Thank you for posting this information.

Regards,
Ivan Danchev
Progress Telerik