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
Our organization recently upgraded Confiforms from 2.18.13 to 3.5.8. It is causing a lot of tableviews stop working.
There is a field definition called category (drop down type: i.e 1:Cat1, 2:Cat2, etc.)
Set values as key=value pairs, separated by & (as request parameters) for inline 'Add':
we used to set it as "category=1" without including a field in the tableview directly and it worked fine. However, after the upgrade, it stopped working unless we add the field of "category" in the tableview.
What it means is that:
- If we do not include the field "category" in the tableview, when we add a new record inline, it won't set the category=1 automatically.
- If we add the field into the tableview, then it sets the category correctly as 1
- Before the upgrade, we didn't have to include this field in the tableview because we wanted to hide it and automatically set it. But after the upgrade it stops working.
Can you please help provide a direction how we should fix it?