Query Params Usage

[Chackmool]

I think I find a small bug.

If I go to define query Params over the app. I can change them and edit them.

But later when you try Insert App Connect Bindings

Query params is not updated.

Both panels do not match in params.

[Alexander_Paladines]

You have another Query1 inside View: content

[Chackmool]

But this is query manager not query params.

[Alexander_Paladines]

They are the same.
You have queryTemplate too,
In View:Content you have a query manager too, that’s ok. But in main layout you have global query params and the queryTemplate, they are the same.

[Chackmool]

Is not a Bug. I understand whats happening. The query parameters need to be declared on the template itself and not in the content page. Thanks

[Cheese]

Try renaming your APP ID in the Content page to the same APP ID as your Layout page (by default it is main I believe). You should then be able to see the Query Manager variables within the Content Page.

[Cheese]

In this post I point it out with its relation to Cookies, but is the same with the Query Manager and Data Store too. Why the Content page does not automatically adopt the APP ID from the Layout page is still a mystery to me though!

Layout Page App ID should be passed as Content Page App ID

The App ID of the Layout Page should be inherited by the Content Page based on the selected Layout. For example if using the Cookie Manager if the App ID’s do not match the cookies are not available to manipulate as they are based on the App ID? By default the newly created Content Page sets its App ID based on the name of the page created rather than that specified in the Layout Page? Is there a reason for this? I’ve used the Cookie Manager as an example for the App ID’s matching but no dou…

[Chackmool]

@Cheese

Try renaming your APP ID in the Content page to the same APP ID as your Layout page (by default it is main I believe). You should then be able to see the Query Manager variables within the Content Page.

Confirmed this works

[Cheese]

@Chackmool

Confirmed this works

Onward and upward @Chackmool.

[Chackmool]

@Cheese

Onward and upward

I am still learning but get amazed with some functions and frustrated with others. But at the end is part of learning curve. Now seems that Dropzone still not ready for App connect 2. Lets see what I will do…

[Cheese]

If you are in that learning phase stick with the Stable Channel to save headaches or the unknown. For everything else you have this wonderful Community to fall back on. More often than not you will get an answer/solution within an hour or two (most of the time within a few minutes). The support here is second to none.

Good luck with your Projects!

[Chackmool]

@Cheese

If you are in that learning phase stick with the Stable Channel to save headaches or the unknown. For everything else you have this wonderful Community to fall back on. More often than not you will get an answer/solution within an hour or two (most of the time within a few minutes). The support here is second to none.

How can I know if the project is in app connect 1 or 2? is any way to go back to app conect 1 if that is the case?

[Cheese]

@Chackmool

How can I know if the project is in app connect 1 or 2? is any way to go back to app conect 1 if that is the case?

All explained HERE

Make sure to click Change Channel and upload the new files to your host. As simple as that but explained a lot clearer in the above link to the documentation on the subject.

You can switch back and fourth as you wish. BUT do remember if you have used Beta Channel specific options within your Project these will no longer work when you switch over to the Stable Channel.