Forum Discussion
EdwardHefter
Qrew Cadet
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
------------------------------
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
3 years agoQrew Captain
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
------------------------------
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
------------------------------
- EdwardHefter3 years agoQrew CadetI 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
------------------------------- EdwardHefter3 years agoQrew CadetTech support at Quickbase solved this for me.
I was searching for the existence of a record and, if that record existed, to update the original record. If the record didn't exist, to create it and update the existing record. I was trying to do it all at once - Do the search, if it is empty do A and if it is not empty do B. What I needed to do was:
Search the records
In the Do Loop for the search (which I had deleted before), update the original record, because if the Do Loop was looping, then a record must have been found.
After the do loop, at the same indention level as the search, put in the condition that If the search found nothing, then create a record and update the original.
Then everything worked. If this is confusing and you are reading this years later and want to know how I originally broke it and then how Quickbase helped me fix it, contact me about the Sunnytech App.
------------------------------
Edward Hefter
www.Sutubra.com
------------------------------- PrashantMaheshw3 years agoQrew CaptainThanks ED . I would still appreciate screenshots of the final working pipeline !
------------------------------
Prashant Maheshwari
------------------------------