ContributionsMost RecentMost LikesSolutionsRe: Pipeline Jinja based on current timestamp One caveat to this - this code does not adjust for daylight savings time. It was skipping at 6am, but now is skipping at 7am. I may just have to adjust this manually twice a year, or come up with another option. ------------------------------ Scott Dye ------------------------------ Re: Pipeline Jinja based on current timestamp This is great. Thanks! For reference if anyone tries this, the 'weekday' check also assumes UTC time, so the start of the day does not match the start of my day. In my case, that was not really a big deal, but wanted to mention it. ------------------------------ Scott Dye ------------------------------ Re: Pipeline Jinja based on current timestamp I forgot to add, this would need to trigger TRUE within the 6:00 hour only M-F, not weekends. ------------------------------ Scott Dye ------------------------------ Pipeline Jinja based on current timestamp I'm trying to build a pipeline that runs hourly, to perform an API call. However, I would like for the same pipeline to perform a second action once per day, at a specific hour (when the hourly run happens in the 6:00AM hour). I understand to build an if statement as so: IF [expression (advanced)] evaluates to TRUE [____________________________________] and I know that the Jinja for "now" is{{time.now}} How would I build the expression that returns true only if the current time is within the 6:00AM hour? ------------------------------ Scott Dye ------------------------------ Re: How can I update a connected field whose column name changes in the connected CSV?Yes, that would probably work - but boy is that messy (as you say).How can I update a connected field whose column name changes in the connected CSV?We recently had to make a change to the CSV file that is used in a connected table via Quickbase Sync. This column name change immediately caused the sync to fail on the next interval, which makes sense. I expected there to be a way to go to the connected field in Quickbase (that was now orphaned), and "re-link" it to the newly renamed field in the CSV. However, there only appeared to be the option to delete my orphaned connected field, and add the "new" renamed field. In this situation that wasn't too big of a deal, but if that field had a long list in the "usage" tab (reports, calculated fields, relationships, etc) it would have been very tricky. Is there not a way to re-link a broken connection to a field?