Confiforms: Define a form on one page but show results only from submitting pages

[Katherine Barako]

Hello,

I have a workflow where pages are created from created pages in a chain. I would like to keep my form definitions in a centralized location instead of re-defining them on each created page.

I am looking to define a form "data" on Page A, which creates Pages B and C. I would like pages B and C to have registration buttons and tableviews for "data" on Pages B and C. However, I want the table in B to only show the data submitted from Page B, and the table in C to only show the data submitted from Page C.

I'm very new to confluence and not sure of the right way to approach this. I tried putting id:[entry.id] in the entries dataset filter for the tableview, which didn't work. I stuck an autopage field in and tried autopage:[entry.autopage], but that didn't seem to work either.

Could someone please point me in the right direction? Thanks very much.

[Alex Medved _ConfiForms_ · Accepted solution]

Hi @Katherine Barako 

What you are asking is really what ConfiForms is all about - you configure the form once and use it in different places, as you like and need - even with custom designs and layouts if that's desired

So, what is not working for you with the "centralized" approach? 

Page B and C are using the form from a page A? 

Then the simplest way to filter the data per page would be to use an autopage field and use it in filtering agains the "current page"

autopage:[entry._page]

https://wiki.vertuna.com/spaces/CONFIFORMS/pages/5341277/Accessing+field+values+and+properties#Accessingfieldvaluesandproperties-Additionalvaluesavailableinthecontext

Alex

[Katherine Barako]

Thank you!! Yes! I got it working.

[Katherine Barako]

@Alex Medved _ConfiForms_ I thought I had it working for a while but I'm actually having an issue now where "autopage" is recording the page the form definition sits on instead of the page the form registration is being clicked on. As a result, when it's comparing autopage to the current page, nothing is showing up on the filter.

Do you know how I can fix this?

[Alex Medved _ConfiForms_]

Sorry, I dont think I understand

autopage field records the page where the registrations control field is placed or where you have edited the record (in case if the field is set to track that as well)

[Katherine Barako]

Exactly--could this be a bug? It appears this is happening only on some forms. My form definition is on one page, my registration is on the other page, and autopage is picking up the form definition page, even when i register from the other page.

[Katherine Barako]

 @Alex Medved _ConfiForms_  I found the culprit though I still don't know why...and removing the "bad macro" causes a loss of functionality.

I had followed this method (second option) to create a link to a created page which involves an IFTTT that updates a confiforms entry with these parameters: entryId=[entry.id]&mypage=[iftttResult_2.id]

When I removed that macro from the form def, autopage functioned correctly again. Do you know why that might be the case?

[Alex Medved _ConfiForms_]

Not sure what you are calling a “bad macro”, but ok. 
I guess your autopage field is configured to be updated each time the record is updated. 
But it feels like you want only to track the source page only when the record is created. So, configure the autopage field to track the source only for new records

[Katherine Barako]

Alex, you fixed it! Thank you

[Katherine Barako]

@Alex Medved _ConfiForms_ Another roadblock:

I'm trying to create a form that creates other forms. Thus, there are tableview macros inside the IFTTT createpage.

I just discovered that while the table autopage:[entry._page] filter works when the form is on an existing confluence page, something odd happens when the form is being created by another page. the [entry._page] gets turned into the form definition page, so all the tableview settings in the edit macro window turn from autopage:[entry._page] to a hardcoded autopage:1403616974.

Is there a way around this? Thanks for your help today.

[Alex Medved _ConfiForms_]

autopage:[entry.id.asEntryRef(entry.page)]

[Katherine Barako]

Thanks @Alex Medved _ConfiForms_ That did the trick, but led to another question.

I have ifttts that create pages--inside these i have many occurances like the above where [entry.fieldname] got replaced with hardcoded numbers. I'll apply your advice to all the affected items and wrap my entry references this way with

[entry.id.asEntryRef(entry.fieldname)]

However, How should I modify references that i want to look like the following:

mypage=[iftttResult_0.id]

[Alex Medved _ConfiForms_]

Why should you modify something like mypage=[iftttResult_0.id]?

Looks like you have some rule that saves back a created page or something

[Tomislav Tobijas]

Hey @Katherine Barako ,

Alex from Vertuna (vendor) might jump on here as well to provide some assistance, but you could also reach out to the product/vendor team directly via one of the following channels. 👈

Marketplace teams are usually quite responsive and helpful when it comes to their apps, so I would probably suggest going in that direction.

I haven't used ConfiForms that much to be able to answer this 😕

Cheers,
Tobi