Pipeline - SharePoint Item Search Issue
I am creating a pipeline to update existing items in a SharePoint list when an item is updated in a Quick Base table. When I do the step to look up the item in SP (SharePoint) I am unable to find th...
Forum Discussion
So if I made the column type maybe a line of text would that work best? Also the SharePoint is an older site, could that be contributing to the error?
At the issues simplest form if I run a single step of just "search items", point it at the SharePoint and the correct list, add conditions where "QB ID" equals 602 (a known items related QB ID), I get a result of no records found.
Could it have to do with field or column needing to be in the default report for the list?
------------------------------
Joshua Case
------------------------------
Text searches will always take longer, so that would be up to you. And, regarding the SP site's age, I doubt that has anything to do with it. If Pipelines is passing a numeric value - using 602 like your example - it will push 602.0. To fix this, you have to force Pipelines to utilize the Integer function like this:
{{a.search_number | int}}
This will force Pipelines to push 602 instead of 602.0 . Anywhere you think this may matter, I would encourage you to utilize the INT function and re-test it before making changes to the field types.
------------------------------
Blake Harrison
bharrison@datablender.io
DataBlender - Quick Base Solution Provider
Atlanta GA
404.800.1702 / http://datablender.io/
------------------------------
Would you run this as an expression first and then by the condition of finding the specific number? I am sorry I am new to using expressions like this.
I ask because when I run this I find an item but it displays an error.
------------------------------
Joshua Case
------------------------------- My apologies - I didn't explain that very well. The example I provided:
{{a.search_number | int}}
was intended to be just a sample, with 'a.search_number' representing the data point you need to search for from your trigger. So, if your field was named 'My Number', the entry would look like:
{{a.my_number | int}}
The inclusion of the pipe ( | ) and the int is what forces Pipelines to format the value for the field as an Integer, rather than a standard Number.
------------------------------
Blake Harrison
bharrison@datablender.io
DataBlender - Quick Base Solution Provider
Atlanta GA
404.800.1702 / http://datablender.io/
------------------------------