Confiforms - Smart Dropdown not populating

Jan-Hinrich Eymers August 14, 2024

Hello,

im working with a complex form.
For testing purposes (dont want to break the live form) i copied the whole confluence page and renamed it.

The page contains two forms. Form 1 is referencing the second form with a smart dropdown field.

Now, what happens if I want to create a new entry in Form 1 with the registrations control macro the dropdown works as expected showing entries from Form 2 as options.
After creation a subpage is created with EditControls nested in a Cardview. The subpages represent one single entry in Form 1.

Within that formview, nor in inline edit the options are shown within said dropdown field.

In the original form i copied it works in creation formview, and also in edit formview as well as inline of the subpage.

Any hints as to what im missing? 

1 answer

1 accepted

1 vote
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.
August 14, 2024

Hi @Jan-Hinrich Eymers 

When you copy a page you get a copy of the page and your smart fields will continue to point at the same page they were configured to in the original page

Alex

Jan-Hinrich Eymers August 14, 2024

Thanks for the prompt answer Alex!
Yes, i changed the page reference in the field definition.

The entries in Form 2 differ from the original form. These different options are shown in the registration ("Create") control form view, but not in the edit view / inline on the subpages that are created with IFTTT rules. So field definition cant be the culprit I suspect.

The field macros point to the copy form as well, i adjusted the view macros in which they are nested and tested successfully that they are referencing the copy form fields. ( e.g. by changing non-smart dropdown options and see how this reflects in the subpages)

Like mahboob_sharif likes this
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.
August 14, 2024

Then I am really puzzled with what is NOT working for you...

Could you please explain this a bit more?

Like # people like this
Jan-Hinrich Eymers August 14, 2024

Yes. Sorry for the confusion.

Form 1:
field definition macro with smart dropdown referencing Form 2

Form 2:
contains entries (test1,test2,test3)

On the page where Form 1 and Form 2 are defined is a registration control macro.
If i use that one (create button in most forms), the options (test1,test2,test3) are shown for the smart dropdown field.
(--> reference of dropdown is working)

After creation a subpage is generated. This subpage contains cardview macros with the entry:id filter similar to the tutorials in the confiforms docs. It also contains a Edit Controls macro to have a proper form view.
In the inline edit of the cardviews the dropdown shows "No matches found" instead of the options (test1,test2,test3).
Same behaviour of the edit form view on the subpage.

EDIT:
the other (non-smart) fields work fine and as expected and are referencing the test form correctly.

Like mahboob_sharif likes this
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.
August 15, 2024

The part with the "After creation a subpage is generated." - what is that?

Do you have a form that creates a page for you via ConfiForms? Is that correct? What is the template/layout that you have then in there?

Jan-Hinrich Eymers August 15, 2024

Within the parent page containing the two forms is a IFTTT rule, which contains the layout and some cardview macros with the filter set to id:[entry.id]

Within one of those cardviews is the field referencing the smart dropdown field definition within the form definition of the parent page.

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.
August 15, 2024

Could you share the storage format of the page with the form?

Jan-Hinrich Eymers August 15, 2024

I would prefer not to, because it contains sensitive data of my customer

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.
August 15, 2024

You can remove the sensitive data, of course.... but feel free to open a private support ticket with us - https://wiki.vertuna.com/display/VERTUNA/Support+Request+Form

At the moment I simply dont understand what you have and what is not working for you, sorry

Jan-Hinrich Eymers August 15, 2024

I removed the sensitive parts:

https://pastebin.com/fYS7y9iP

Jan-Hinrich Eymers August 15, 2024

The fiedl Causative Application is a smart dropdown.

If i use the creat button on them ain page, the options within this dropdown are showing.
After creation, if i try to edit this field cia the edit button on the subpage for that entry, or in the inline edit of the subpages cardviews, no options are found for that dropdown anymore.

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.
August 15, 2024

Your configuration for the "Causative Application" field contains a reference to the current page (where the view is placed, not at the page where the form is)

 <ac:structured-macro ac:macro-id="eb265d1e-9dd5-450f-83f6-89926a46d98d" ac:name="confiform-field-definition" ac:schema-version="1">
<ac:parameter ac:name="fieldName">causativeApplication</ac:parameter>
<ac:parameter ac:name="fieldLabel">Causative Application</ac:parameter>
<ac:parameter ac:name="values">[[entry._page]|applicationsTest|application|true||]</ac:parameter>
<ac:parameter ac:name="type">smartselect2</ac:parameter>
</ac:structured-macro>

 [entry._page]

Fix this configuration to point at your page by selecting page title (actual page id will be taken)

Alex

Like Jan-Hinrich Eymers likes this
Jan-Hinrich Eymers August 15, 2024

You are the GOAT, thank you so much Alex!

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.
August 15, 2024

Awesome

Happy to help

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events