I am currently making a scheduling/event planning app, here is the structure/connections of what we are working at for context.
Each event could have many program plans, and each program plan record can connect to another program plan record as a “parent plan”, so when the Date and Time of the “parent plan” are updated, based on how much time was offset given the formula to calculate and adjust. The new date and time of the program plan connected to the “parent plan” could be changed too.
This is not doable through record by setting the fields to equal to the equations as the equations have a lagged effect from when the values are entered from the form hence I am creating a task to update the record once more after the updates with the record rule.
I am currently looking for a way to automate the triggering of tasks based on updates of the record, with the task’s function being able to update all the records in the table (based on how many generations of parenting there have been with events) to sync up with the change in time.
I have looked with Zappier and Make, neither of which has the ability to trigger a task, rather it can only trigger a change in 1 particular record.
Are there any ways that I can trigger a task without having to either schedule a set time or have it run manually from the backend? This could be either a button/record rule on the front end, or a third-party automation app.
Thanks so much!
1 Like
Hi @Yee_Hong
I’m not sure I completely understand the set up as I struggle visualising it in text form.
However, Make is an extremely powerful tool and I use it extensively for updating parent and child records. You’ll be able to obtain the ID of the parent and update the related child records based on a trigger being sent to the scenario. Happy to connect and have a chat if you want to explore further
Thank you Carl for replying,
I am currently looking to trigger a task through an update in record, having tested around in Make, it doesn’t seem to be possible. I am currently looking at using javascript to complete the task process.
I am very new to API and Javascript in general (hence I am utilizing a knack to construct my app). I am currently following a tutorial with knack-api-helper - npm to set up some elementary steps. However what I would like to achieve through this process is to detect an update in the record, which would trigger a for-loop (I am not sure if that is what it is named in javascript) with the number of loops being the the count of records connected to another table. This loop will then be put in to place to update all records that have the connected record with a “PUT” command.
If you could guide me in setting this javascript up that would be very helpful!
My sincere appreciation
So breaking the functions down,
- Detect an update of a record from a table
- generate a for loop based on counted values from the table (with filters)
- looped commands of replacing the date & time field with an equation field in a filtered selection of records within this table
Hi @Yee_Hong
As @CarlHolmes said if you are new to JavaScript, Make is the way to do this.
Step 1
Trigger = On Update record
Step 2
Search for all records connected to step 1 record
Step 3
Update all records retrieved from step 2
I am quite happy to help more with this or with the JavaScript I would try Make first as this is fairly straightforward where as JavaScript will involve quite a bit of back and forth or a meeting.
Craig
1 Like
What my good friend @CSWinnall said.
I’m not a coder so would lean towards Make.
Craig is a Jedi Master at coding, well, compared to me. In my defence, I’m an excellent “copy and paster”.
1 Like
Thank you @CarlHolmes but you understand Knack better than most because you don’t code. We tend to use brute force with JavaScript when there are ways to do it in Knack.
With this @Yee_Hong I would use Make over JavaScript as potentially you can do what you need in 3 modules with no code. Otherwise your looking at doing API calls which if you’re happy to learn I will help with just DM me and we can have a chat about it.
Craig
1 Like
Thank you so much, I am currently giving this a try, however, I am having a bit of trouble with step 2 being that I am not familiar with Make. @CarlHolmes, with you having more experience on the platform, do you know if I could search search for records connected to the records that were updated in step 1, as the current prompts I see are based with record IDs.
This would also apply to linking the connections with step 3!
Thank you so much
Yes so you can right click on the trigger then run this module only. Update a record on the front end .
You will see all your fields to chose from
1 Like
Thank you very much, these are the current codes I am also experimenting with, trying to pull an update from the inline edit of the grid, however, I have no clue identify which view the grid I am working with is, I have looked within in knack and in the HTML edit page on the front end and had no luck.
Could you point me in the right direction? Hopefully, the make integration could work but I believe javascript is something to learn and would be useful in the long-term.
Thank you again!
Would this apply to the new records that are created down the line that are not linked in make?
If you go to the builder then click to edit the view.
Then look at the URL in the builder you will see view_123
Or inspect the view using chrome dev tools then look for the ID of the grid/form/details something like
id=“view_123”
2 Likes
Found it, i have definitely spent way to much time on finding out about this!
Thank you so much
1 Like
Hi @CSWinnall , I ran into some difficulties with the equations fields in knack as they aren’t updating properly, but I was able to surpass that by fully utilizing Make.com to compile my calculations.
However, a new problem arises as with the current webhook configuration, Make can only detect user updates from the records, so the records that are updated by Make won’t be picked up by Make to form the “loop” that updates the connected records to the automatically updated record.
is there anyways to customize the webhook so it detects records that are also updated by Make, or is there a way to loop the operation within the make interface so it will continue the operation until there are no more connected records?
Thanks for the all the help!
Hi @Yee_Hong
You should be able to do everything you need in one Make scenario without the need to loop back into the scenario. If you DM me we could setup a meeting to talk through what you’re trying to achieve.
Craig