Error in list('listname').create({data})

[Jandos22]

Good day!

When I try to create an item in a list I get the following error:

400 - {"error":{"code":"-1, Microsoft.SharePoint.Client.InvalidClientQueryException","message":{"lang":"en-US","value":"A node of type 'EndOfInput' was read from the JSON reader when trying to read the start of an entry. A 'StartObject' node was expected."}}}

const body = {
                Name: action.userData.name,
                Surname: action.userData.surname,
                Alias: action.userData.alias,
                Gin: action.userData.gin,
                Location: action.userData.location,
                Email: action.userData.email
            };
            return sprLib.list('NgPeople').create(body);

I guess it is related to sending 'data' or 'body' object during request.

Regards,
Zhandos

[gitbrent]

Hi @wireliner,

Thanks for opening an issue.

It appears the JSON body object isn't being encoded correctly... Can you check the dev tools (F12) Network tab to see what's being passed to SP?

[Jandos22]

Hi @gitbrent ,

Looks like no payload is being passed. Btw I use sp-rest-proxy for development (2nd picture).

[koltyakov]

@wireliner,

Can you check the same script/payload on SharePoint page and with sp-rest-proxy?
Is there a difference? Feel free to post related issues to proxy's project if there is a different behavior on SP page and Local page talking to the proxy.

[Jandos22]

Privet @koltyakov,

After running script on Sharepoint I get a different error and again don't see payload being passed to SP.

It might be worth to mention that I ran script not from SP *.aspx page, but from custom angular5 html (example, sites/ngapp/dev/index.html#/app). Maybe now it is a RequestDigest value problem?

[koltyakov]

Does SpRestLib wrap digests?
@wireliner please try refreshing the page. The error is common when you navigate back and forth in browsers history and then execute POST with the wrong digest.

[Jandos22]

@koltyakov refreshed the page, same error.

not sure if SpRestLib wraps digests ... I am quite new to SP, but my custom POST call to add item using REST api works fine, just wanted to take advantage of simplicity of SpRestLib.

[gitbrent]

Hi @wireliner,

SpRestLib does pass the security token/digest value - it's one if the last items under the "Request Headers" section:

However, this depends upon the SP page having the __REQUESTDIGEST form element. Normally, you'd embed an app in an .aspx page within a Webpart, where this token will always be present. Check for the token via $('#__REQUESTDIGEST').length etc.

Your second post's screencap shows the URL being used as:

http://localhost:4200/_api/list/getbytitle[...]

So the issue there may be due to an incorrect value. Perhaps, use the baseUrl variable:

sprLib.list({ name:'Employees', baseUrl:'/sites/wireline' })

[Jandos22]

@gitbrent thanks for clear explanation. I see now that the problem maybe is that I use my custom ".html" page and not ".aspx" page, so digest value could not be retrieved in this case. What I do is get FDV by calling to "_api/contextinfo".

[gitbrent]

Hi @wireliner,

Thanks for the follow-up, that's really helpful.

The library currently only looks for the FDV via the __REQUESTDIGEST form element, but that leaves people who use the _api/contextinfo without an avenue to auth via SpRestLib...

I'll create a new option to pass the FDV value in the next release.