SharePoint 2013 Designer workflow Rest API: update items in multi valued lookup column - rest

I am trying to update the SharePoint online list items using Rest API in SharePoint Workflow 2013.I am able to update all the columns except Multi valued lookup column.
I am getting the below error :
An unexpected 'PrimitiveValue' node was found when reading from the JSON reader. A 'StartObject' node was expected.
I have tried the below code :
Passing ID & Value
1;#abc;#2;#xyz
& i have tried passing dictionary also but no luck every time getting some or the other error.
Please let me know how to achieve this.

Related

DataFormat.Error on AssignedTo column running Power BI query to get Azure DevOps data

I'm using this sample Power BI query to get data from Azure DevOps Services, and I get the following error on the AssignedTo column:
DataFormat.Error: We expected a property 'AssignedTo', but the OData service omitted it from the response data. This can occur for a number of reasons and does not necessarily imply that the data does not exist or is of a default value. Details:
Property=AssignedTo
However, if I run the URL directly in a browser, I get all the data returned correctly including the AssignedTo column.
Any idea what might be happening here?
This happens when the AssignedTo is empty in Azure DevOps. The solution is to replace it with empty:
#"Replaced Errors" = Table.ReplaceErrorValues(#"Your table here", {{"AssignedTo", ""}})
in
#"Replaced Errors"
Removing OmitValues = ODataOmitValues.Nulls from the query fixed it. It appears that the sample query assumes there are only non-null values, and will therefore omit null values. Removing this part of the query ensures that null values are considered valid, and therefore removes the error.

Power Automate - Update Work Item Error - Response in JSON Format -Azure Devops

I am getting an exception when I am trying to update an existing work item description with a link of SharePoint file in power automate. This SharePoint file had been created when an email with the attachment was received.
Please have a look at the flow and exception below
Can anyone please help me understand the issue?
Thanks,
Bee
It looks like you entered a wrong variable for the field Work Item Id. The field Work Item Id for step Update a work item should be the id of the work item to update.
I saw you set the field Work Item Id to variable {x}workItemUrl. If variable workItemUrl is not the work item id. The automate flow will fail with above error.
You can also check the log to see if the values you specified in the fields are correct.

Retrieve count related lookup value using REST in SharePoint 2016

I am following this post:
http://pawansatope.blogspot.com/2012/01/how-to-create-count-related-lookup.html
Now I want to get the same results(i.e DepartmentTitle and NbOfEmployees) values programatically using the REST api.
I've tried different variations of:
/items$select=Title,NbOfEmployees/...&$expand=NbOfEmployees
but haven't got any luck.
Has anyone tried this?
Many thanks!
I created the lookup field "NbOfEmployees" (Department(Count Related) to Employee Data list like this:
This is the two list data:
Then for NbOfEmployees field (Department count), directly get in Rest API:
http://sp2016/_api/web/lists/getbyTitle('Department')/items?$select=NbOfEmployeesId,Title
Actually, this value is the real count value for department, no need to expand in Rest.

How to pass 3 query parameter in talend tRESTClient

I'm using Talend Big Data for pulling data from HP ALM to mongoDB using tRESTClient. Already i am passing two query parameters(query,page-size) in tRESTClient. Now i have tried with one more parameter last-modified like this query1={last-modified[>=(2017-06-21)]}. But it is not taking as a parameter.
Below i've mentioned tRESTClient component detail.
How can i pass 3rd parameter with the tRESTClient?
Just bellow the Query parameters box, you can find easily a green + button that adds new line for a new paramerter

Searching for messages with categories in Office 365 REST API

I'm trying to find all messages that have a non-empty category list, using Office 365 REST API, using the following request:
/api/v2.0/me/messages?$search=%22Categories:-[]%22
This doesn't seem to work though: it returns an empty result set. When I run the same query in Outlook 2016 UI, it does return results.
Is it not supported or is their something wrong with the query?
As my test, using the following format can get the non-empty category list.
endpointUri + "/Me/Messages?$search=%22category:%22".
The search field is 'category', and add nothing behind the colon. Hope it helps.