Forum Discussion

EdwardHefter's avatar
EdwardHefter
Qrew Cadet
3 years ago

Pipeline views {{e.id}} as the text "{{e.id}}" rather than the record ID number

This one has me confused. I have a step in a pipeline to update a field in a table with the record ID from another record in another table. I have a search in step E for records that match a criteria....
Pipelines
JenBlack's avatar
JenBlack
Qrew Member
3 years ago
I'm not sure if this will help but for all of my pipelines, I end up turning my record ID field into an integer in the pipeline Query step by adding "|int" into the field as seen below. SS also provided. Not sure if that will help but I've never had any issues with pipelines on the record ID side with this trick.  

{{a.id|int}}



------------------------------
Jen Black
------------------------------
  • EdwardHefter's avatar
    EdwardHefter
    Qrew Cadet
    3 years ago
    Thanks Jen,

    It's a good idea and it's worked for me in the past, but it didn't work this time. It seems like the pipeline is actually trying to put the text "{{e.id}}" or "{{e.id|int}}" into the number field, rather than the record number itself. I'll upload pix in response to Prashant's post.

    ------------------------------
    Edward Hefter
    www.Sutubra.com
    ------------------------------
    • PrashantMaheshw's avatar
      PrashantMaheshw
      Qrew Captain
      3 years ago
      Honestly the [pipeline] looks simple enough,

      I would definitely try to run a smaller pipeline for my scenario 2 , Which means the filter of is empty is not working , Or at least reverse the scenario where we check for [pipeline] is empty


      .making sense ??

      ------------------------------
      Prashant Maheshwari
      ------------------------------
      • EdwardHefter's avatar
        EdwardHefter
        Qrew Cadet
        3 years ago
        I reversed the order, so that if there were found records, it would do that branch first. I ran into the same problem. When there were no records found (the "else" branch of the "if/then/else"), using {{__.id}} worked fine, but when there were records found (now the "then" of the "if/then/else") I got the same error.

        The pipeline is interpreting the {{___.id}} as the number in one instance and as the literal text {{__.ID}} in the other. I substituted the number 47 for {{___.id}} in the step where it wasn't working, and that worked fine. Of course, I need the actual record number, not the arbitrary one I picked...

        Trying to force it into an integer by using {{___.id|int}} doesn't work because Pipelines is just looking at it like text. 

        ------------------------------
        Edward Hefter
        www.Sutubra.com
        ------------------------------