Unanswered

An unexpected 'StartObject' node was found when reading from the JSON reader. A 'PrimitiveValue' node was expected.

(0) Share

Report

Posted on by stormin_30

Hello All,

I am receiving the following error message when adding a picture to a SharePoint image list column. This was working before.

An unexpected 'StartObject' node was found when reading from the JSON reader. A 'PrimitiveValue' node was expected.

Any insights would be appreciated.

Thanks,

Norm

Categories:

Building flows

I have the same question (0)

All responses (13)

Answers (0)

fchopo 8,003 Moderator on at

Like (0)

Report

Hello @stormin_30

Have you changed any SharePoint list column value type or nullable?

Regards,

Ferran

Was this reply helpful? Yes No
stormin_30 89 on at

Like (0)

Report

Hi @fchopo,

Thanks for responding. The column (named Picture) has always allowed null and has always been an image type.
Have you experienced this error before?

Thanks.

Norm

Was this reply helpful? Yes No
fchopo 8,003 Moderator on at

Like (0)

Report

Hello @stormin_30

I did a test on my side and I have the same exact problem... :S I'll do some other tests and let you know.

Regards,

Ferran

Was this reply helpful? Yes No
stormin_30 89 on at

Like (0)

Report

Thanks, @fchopo I appreciate it.

Was this reply helpful? Yes No
CU09091757-0 299 on at

Like (0)

Report

@fchopo Any solution to this issue?

Was this reply helpful? Yes No
Deaked 4 on at

Like (0)

Report

Was there ever a solution to this issue?

Was this reply helpful? Yes No
stormin_30 89 on at

Like (0)

Report
I don't recall what the fix was but I did write a blog post about the Flow pattern was maybe the fix is included. Snippet below and URL to blog for context:
https://normyoung.ca/2020/04/24/build-a-safety-issue-solution-using-sharepoint-and-power-automate-part1/

Add a SharePoint “Send an HTTP request to SharePoint” action
Set it to your site.
Set the “Method” to “Post”.
Set the “Uri” to “_api/web/lists/GetByTitle(‘Safety Issue‘)/items(ID).
Safety Issue is the external name of the list, note the space!
ID is from the “Create item” action!
Set the “Headers” to (using text mode):
{
"Content-Type": "application/json;odata=verbose",
"X-HTTP-Method": "MERGE",
"IF-MATCH": "*"
}
Set the “Body” to:
{'__metadata': {'type':'SP.Data.SafetyIssueListItem'},'Picture':
{'Description': 'Timestamp.png',
'Url': 'AbsoluteUri'}
}
Timestamp is “Timestamp” from the “Manually trigger flow” trigger.
AbsoluteUri is “AbsoluteUri” from the “Add attachment” action.
Important there are single quotes around ‘Timestamp.png’ and ‘AbsoluteUri‘.

Was this reply helpful? Yes No
Deaked 4 on at

Like (0)

Report

Thanks for the reply. Same error unfortunately however i have logged a ticket with support 🙂

Was this reply helpful? Yes No
helloAndre 27 on at

Like (0)

Report

DId you ever get this solved with support? Having the same issues

---
Update I thought I've not got a solution

Was this reply helpful? Yes No
helloAndre 27 on at

Like (0)

Report
I used the solution in this video:
https://www.youtube.com/watch?v=y-2iDrfgvfw
But updated the code to update an existing record:

Uri:
_api/web/lists/getbytitle('Branch List')/items(*DynamicListItemIDNumber*)

Headers:

Body:

{ "__metadata": { "type": "*ListName*" }, "*ColumnName*": "{\"type\":\"thumbnail\",\"fileName\":\"*FileName*\",\"fieldName\":\"*ColumnName*\",\"serverUrl\":\"*SharePointURL*\",\"serverRelativeUrl\":\"*ServerRelativeURL*/*FileName*\"}" }
Examples:
ListName: SP.Data.My_x0020_StakeholdersListItem
You can find this by searching your the code at this directory:
If you're in your own Space: https://*domain*.sharepoint.com/_api/web/lists/
If you're in a Teams Space: https://*domain*.sharepoint.com/sites/*msteams_00aa00*/_api/web/lists/
ColumnName: Pictures
FileName: File Name.jpg
SharePointURL:
If you're in your own Space: https://*domain*.sharepoint.com/
If you're in a Teams Space: https://*domain*.sharepoint.com/sites/*msteams_00aa00*
ServerRelativeURL: /SiteAssets/Lists/aaa000aa-a0a0-a0a0-a0a0-0aaa00a0a00a

Was this reply helpful? Yes No