You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi @Kathleen Janiszewski and welcome to community
I will try my best, but honestly - I am very puzzled with your question
Seems to be a mixture of client side and server side things
So, you can update ConfiForms records with ConfiForms IFTTTs (server side) and you can also use REST APIs to update ConfiForms records from a client side
These are different approaches/methods on how to do a similar (or same) thing - should not be used together (and are independent from each other)
Let me explain what's going on. I start with a ConfiForm that has a user, number of hours per week, and a list of start weeks and end weeks in the fiscal year. An admin can at any time change the number of hours per week a user is assigned to their project for a given time frame by week. Based on the selected weeks, I know which ConfiForm fields need to be updated. This is where I construct the string that's used in the REST API. If you have a more direct way for me to be able to update the data directly via the IFTTT macro, please let me know! That's what I've been looking for.
What is the easiest for you. If you find the REST API call easier then do that
I think using the Create/Update ConfiForms Entry or Update Entries by Filter IFTTTs is easier to use and work server side, which means - always (even when updates are invoked from automation, etc)
If you need to build the parameters dynamically then you better stay with REST APIs
So now I have the ConfiForm storing the correct data, using the REST API. Now, I need to force the refresh of the TableView macro. How can I accomplish that? I tried adding another onModified IFTTT macro that redirects to the current URL, but that doesn't always work for all of the data. It's probably an issue with synchronicity. Please let me know if there are any other options.
Hard to tell what does not always work... without seeing complete configuration, but
If your IFTTT runs onModified and does not have any condition set then it is a problem.
Your IFTTT should have a condition or catch the transition and not run every time on every update
The user would only edit and not cancel out unless they modified something, so there's no good reason to have a condition set. If there's some flag that is set when something changes on the form, that might work. Otherwise, my initial approach was to do all of this on the initial update form. Hence the question I pose here: https://community.atlassian.com/t5/Confluence-questions/How-to-use-data-on-a-ConfiForm-to-update-hidden-fields-prior-to/qaq-p/2293599
Well it all depends on what you feel more comfortable with and what is the best tool for the job
From fragmented requirements I read from your posts I feel like this is not really a job for ConfiForms.
As this is some very custom form that you need to do lots of precalculations.
If there's some flag that is set when something changes on the form, that might work.
You can set one extra field that will tell you such "flag" And never do an update when this field is matching
We send an email only when send field has a true value and only when it changes to true
We have an extra ifttt that resets the send field value after that