Forum Discussion
DanielJohnson2
4 years agoQrew Trainee
Hey Mark,
Thanks for the reply, as always. I see where you're going with that User Focus table and I decided to try it out with a combination of pipelines, formula queries and API calls.
So, I've got a pipeline that creates a dummy record in the schedule table under my username for each day (the same pipeline is meant to delete old records). Then, when I'm ready to view the recording record I'm starting from a report from the recordings table with a button on it. I added a variable with a query in it in the button field to locate the dummy record and send over the length of the recording when I press the button from the report.
Then back in the schedule table, I've got another formula query field that is looking only at that dummy record and the field with the recording length in it that gets updated every time I click that button.
So now, when I click that button on the recordings table report, it opens the recording record with the linked report in it, that now has a field that's looking at that dummy record that has the length of the current recording in it just sent over with the button click, and from there I can do my calculation.
I am having a little trouble with the pipeline at the moment. I want to scrub the schedule table of the dummy records. So, my thought was to create a scheduled pipeline that creates a new record two days out, every day, and deletes yesterday's record. However, I'm having trouble with the Search Records step identifying my dummy record from yesterday. Any thoughts there?
Thanks,
------------------------------
Daniel Johnson
------------------------------
Thanks for the reply, as always. I see where you're going with that User Focus table and I decided to try it out with a combination of pipelines, formula queries and API calls.
So, I've got a pipeline that creates a dummy record in the schedule table under my username for each day (the same pipeline is meant to delete old records). Then, when I'm ready to view the recording record I'm starting from a report from the recordings table with a button on it. I added a variable with a query in it in the button field to locate the dummy record and send over the length of the recording when I press the button from the report.
Then back in the schedule table, I've got another formula query field that is looking only at that dummy record and the field with the recording length in it that gets updated every time I click that button.
So now, when I click that button on the recordings table report, it opens the recording record with the linked report in it, that now has a field that's looking at that dummy record that has the length of the current recording in it just sent over with the button click, and from there I can do my calculation.
I am having a little trouble with the pipeline at the moment. I want to scrub the schedule table of the dummy records. So, my thought was to create a scheduled pipeline that creates a new record two days out, every day, and deletes yesterday's record. However, I'm having trouble with the Search Records step identifying my dummy record from yesterday. Any thoughts there?
Thanks,
------------------------------
Daniel Johnson
------------------------------
DanielJohnson2
4 years agoQrew Trainee
Figured out the Pipeline issue. I was putting a {1.EX.'yesterday'} type expression in the advanced expression in the conditions area, when it was meant to go directly under the fields in the Advanced Query area. Works now.
------------------------------
Daniel Johnson
------------------------------
------------------------------
Daniel Johnson
------------------------------