Forum Discussion
Here's the Jinja info for anyone looking to take that approach.
Get the Jinja Date & Time Cheat Sheet mentioned in this video.
------------------------------
Quick Base Junkie
------------------------------
------------------------------
Brittany Zane
------------------------------
- QuickBaseJunkie3 years agoQrew CaptainHi @Brittany Zane
Thanks for posting this. It appears the behavior in Step A with regards to dates has changed. I previously used and tested the code that you are using and now I too am getting the validation error.
I have not yet found a proper workaround. It looks as though the Pipeline wants a format similar to "2022-04-18T00:00:00+00:00" even if it is just a Date field.
I will post an update when/if I'm able to resolve this with Jinja.
In the meantime I would suggest using an Advanced Query instead as it is simple to use 'today' in the query such as:{7.EX.'1'}AND{8.EX.'today'}
Where 7 would be replaced with the field ID for your Proposal Log - Deposit Required field and 8 would be replaced with the field ID for Fiscal Year End.
Please note you will need to delete all of the Queries you have Step A now, in order to access the Advanced Query (just above the existing Queries).
For more on Queries: https://www.quickbasejunkie.com/blog/query-writing-101
------------------------------
Quick Base Junkie
------------------------------- BrittanyScheid3 years agoQrew CadetThanks for the reply. I did find that Advanced Query workaround through another post and have been using that for now. I too was confused because I was sure I had it working in a pipeline previously as well, but over the last couple weeks/month, I haven't been able to get it to work. Please let me know if you find a solution. Thanks!
------------------------------
Brittany Zane
------------------------------- QuickBaseJunkie3 years agoQrew Captain
@Brittany Zane I figured it out, although it's not the answer either of us will like.
Basically, Jinja such as this{{ (time.now|timezone('America/Los_Angeles')).date() }}
Can only be used on "Search/Query" type steps when in Step A.
I do have a footnote to this effect on the Jinja Date/Time Cheat Sheet (but it's easy to miss or forget about).
The messaging from the Pipeline error is very misleading as it appears its just the wrong format when in reality it's not reading it at all. (I invite the Pipeline developers to correct me if I'm wrong).
Besides the Advanced Query solution, the other option if your Step A is a Trigger or Action would be to insert a Condition just after the step such as this.
The background shows the condition, the foreground shows the activity success.
------------------------------
Quick Base Junkie
------------------------------