Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Confiforms: Set values as key=value pairs, separated by & (as request parameters) for inline 'Add'

Our organization recently upgraded Confiforms from 2.18.13 to 3.5.8. It is causing a lot of tableviews stop working.


Form definition:

There is a field definition called category (drop down type: i.e 1:Cat1, 2:Cat2, etc.)

Table view:

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?



1 answer

1 accepted

0 votes
Answer accepted
Alex Medved _ConfiForms_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 04, 2023

Hi @Patrick Liang 

Sorry about that. This is a confirmed (now) regression - will provide a quick fix as part of the 3.6.1 version release


Excellent. Thank you, Alex.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events