Forum Discussion

bradyakers's avatar
bradyakers
Qrew Cadet
24 days ago

Pipeline shows 0 records found?

Made a scheduled pipeline to look at a "formula - duration" field on Table A (Calendar) that signifies how many days until an event there are.  If it is between 0-75 days, it should create a new record on Table B (Project Manager).  For some reason, however, its just returning 0 records, and going through as successful.  Even though I have a record where the column is 5 days away.  I will continue to work on this, but I didn't know if anyone might have some ideas why it is not seeing this record on Table A and making a new one on Table B?

  • If the field you are comparing to in native, Quickbase is a duration field then you're being tripped up by the unit of measure issue. There is some possibility that if you compare the range to 75 days instead of 75 it might work. But if that doesn't work, then I suggest you make a new formula numeric  field in native. Quickbase called [duration in days]; with the formula of

    ToDays([My duration field])

    that will give you a nice clean numeric field to use for the comparison in a pipeline  

     

     

    • bradyakers's avatar
      bradyakers
      Qrew Cadet

      Yes it was initially set to smart units, where I set the filter up as "0 days to 75 days" but it completely failed doing that.  So I switched it to just being "Days", which gives the numeric value. But now it runs fully but it discovers no records.

  • Just set up a formula numeric field like you suggested and it worked!  Very strange.

  • Mez's avatar
    Mez
    Qrew Cadet

    I've ran into something similar with trying to determine if a record is less than a duration value. I'm not sure why but it appears the function for seconds is adding zeros (000). When you set the duration field to seconds, it will display appropriately. However, if you use the formula builder, you'll see 3 extra zeroes added. This value is also true in pipelines, even though you might expect the value for a full day in seconds to be 86,400, you'll get 86,400,000. 

    One of my examples was to look at something within a duration of 4 days. In pipelines if I multiple the total seconds by 1000, I get results that I'm looking for. 

    Very strange indeed. 

     

    • MarkShnier__You's avatar
      MarkShnier__You
      Icon for Qrew Legend rankQrew Legend

      It's not strange.  It just means that they store Duration fields in Milliseconds.

      • Mez's avatar
        Mez
        Qrew Cadet

        Strange from the end users perspective in that I've asked for seconds, yet I don't get the data that way. End users should not have to concern themselves with data storage. 

  • When you say that you sent the Duration field to seconds, that means to display as seconds.  That affects the formatting of the display but does not affect how its stored.  So it's good to  know that they store durations in milliseconds.

    • Mez's avatar
      Mez
      Qrew Cadet

      Agreed, even though it's an implementation decision that is not visible to the end user without investigation since the lowest level to a user is seconds. Not sure I've seen this in the documentation either. Perhaps I just missed it.