Forum Discussion

Roy-Wanyoike's avatar
Roy-Wanyoike
Qrew Assistant Captain
13 days ago
Solved

Skipped because set values are the same as in source object.(Error in Pipeline)

I have a pipeline which is supposed to update kanban columns. Am doing a search in the first step which has the filters and then a condition to check if a condition is met with the criteria I have set. When I run it I can see the green tick which make me smile but when I go to the kanban report there is nothing happening. The only message being displayed is " Skipped because set values are the same as in source object." 
I've tried even creating a datetime field to use to update the search and update but nothing works. Any remedy for this?

  • I managed to fix it. I was missing the column in the filter step. I know its not a long term fix but for now it solves the problem. I added this filters
    "Kanban column is not product name" 
    This rephrases which column you want the column to be moved to by the pipeline.The pipeline was finding records that already had the correct Kanban column value, so QuickBase skipped the update with "Skipped because set values are the same as in source object" — there was nothing to change.

    The Fix

    By adding the filter "Kanban column is not [product name]" to the Search Records step, the pipeline now only pulls records that are not already in the correct column. This means:

    Before the fix → pipeline found all Resurg records including ones already in the right column → skipped them

    After the fix → pipeline only finds Resurg records that are sitting in the wrong column → updates them and moves them

3 Replies

  • Use the Activity log for a Run and see what the input-value is that the Pipeline is reading (which you are expecting to change).  Try test-runs on specifically filtered-records under the different conditions you expect to change/not change to see what the Pipeline is doing.  Make sure your search step has the next step as a LOOP and your CONDITION is INSIDE the LOOP.  Post the YAML here so we can see what the Pipeline is doing.

  • hi, Roy.  what's the underlying data structure and what's triggering the pipeline?  without knowing the specifics, you may have more luck using the https module to directly query the Quickbase API.  the API response gives you more specific feedback than the green tick, for sure.  you can also use Quickbase's API explorer to quickly experiment until you get what you're after.

  • Roy-Wanyoike's avatar
    Roy-Wanyoike
    Qrew Assistant Captain

    I managed to fix it. I was missing the column in the filter step. I know its not a long term fix but for now it solves the problem. I added this filters
    "Kanban column is not product name" 
    This rephrases which column you want the column to be moved to by the pipeline.The pipeline was finding records that already had the correct Kanban column value, so QuickBase skipped the update with "Skipped because set values are the same as in source object" — there was nothing to change.

    The Fix

    By adding the filter "Kanban column is not [product name]" to the Search Records step, the pipeline now only pulls records that are not already in the correct column. This means:

    Before the fix → pipeline found all Resurg records including ones already in the right column → skipped them

    After the fix → pipeline only finds Resurg records that are sitting in the wrong column → updates them and moves them