Your question was "What do you mean by GUI?" and I answered.

In your (first?) LSS file that I downloaded and used you had set the "encID" question to "Always hide: ON" in the GUI, while Tpartner had set the css class for this question to "hidden", not using the "Always hide" feature. Here a screenshot on where to find both options:



When writing something to a question via Javascript, you usually can't hide the question via "always hide", because JS wouldn't have anything to write to.

But for other operations from within LS (e.g. with Expression Manager) this should not be a problem and you should be able to use the "always hide". That is also described in the manual for the panel integration. So it should work. But in your first lss which I tested it didn't. it only worked once the "always hide" was set to "off". So either there is another problem within your test survey, or this is a bug with LS.

I will try to setup my own clean test survey to give it a try and see what happens.

holch wrote: So either there is another problem within your test survey, or this is a bug with LS.
I will try to setup my own clean test survey to give it a try and see what happens.

The GET URL parameter to hidden question should work with the "always hide" function. That was the way is was even before the panel integration function was available.

What does a complete URL look like, when it come from the panel provider?

You mean those below...?


Completes:
survey.blablabla.com/ic/survey.php?autoAnswer [317950][0]=0&encID=xxx

Screen-out:
survey.blablabla.com/ic/survey.php?autoAnswer [317950][0]=1&encID=xxx

Quotafulls:
survey.blablabla.com/ic/survey.php?autoAnswer [317950][0]=2&encID=xxx

IP check:
survey.blablabla.com/ic/survey.php?autoAnswer [317950][0]&encID=xxx

No, filled with actual values. E.g.what is the maximal length of encID?

This part looks quite unusual: [317950][0]

The attached LSS export is containing bugs. Was the export the final version?
There are missing variables and other bugs.
Might be totally unrelated to the URL issue, but I don't want to waste time.

The panel integration of the survey is containing this:


That isn't matching the entry URL you showed:

This part looks quite unusual: [317950][0]

I searched a bit with the URL and this seems to be some code (for the survey probably) from the panel, because other links from them looked the same (there are quite a few questions in the soci survey forum).

jelo wrote: No, filled with actual values. E.g.what is the maximal length of encID?

I believe this is the length of their endID 3-zJiSl_V3Ey-A9ZpaG5XSKA~~

jelo wrote: This part looks quite unusual: [317950][0]

this is what panel provider gave me...

jelo wrote: The attached LSS export is containing bugs. Was the export the final version?
There are missing variables and other bugs.
Might be totally unrelated to the URL issue, but I don't want to waste time.

I don't now how... uid code was my first attempt that I changed for encID later... so I abandoned the LSS export test1, and made a new one from scratch which is attached... what are you saying about the bugs?

You attached a shorter survey. For testing fine.

I found no issues when using a typical link from your panel.
The encID is in the EndURL.

Thanks... but I can not believe this any more... I did not change a thing in a file, and I am not getting what you see on the last screen... how did you get encID in the end URL?!

ipazur wrote: I did not change a thing in a file, and I am not getting what you see on the last screen... how did you get encID in the end URL?!

You attached two surveys in this thread, correct?
I just used the last survey you attached and tested it via demo.limesurvey.org.

You should test such input/output URLs with a second browser session.
Login into LimeSurvey and for survey links use the private session window of your browser.
That way you can close that window and test again. No side effects via session data left.

The entry URL might be a source for issues too:

Yes, I attached two files, the last one limesurvey_survey_745722.lss, testna 2

Ok, I imported this file also on demo.limesurvey.org now, and tried like you suggested with private window but no luck...

demo.limesurvey.org/index.php?r=survey/i...SURVEYID&lang=hr&enc ID=4--8IZ-ngvFB3aJnuUFwLGdg~~ - where this part is coming from in this link?!

my entry link there is
demo.limesurvey.org/index.php?r=survey/i...2&lang=hr&encID=test

in my end link I am still not getting endID

OK, now I get where you problem is. We really, really, really need to start with the basics. What is a panel, how they work, what they do...

The panel sends people to your survey. To do so, they need a link to send the survey to.

However, they also need to know, who of those they have sent to your survey have completed the survey, have been screened out because they did not fit the profile or the quota for their profile was already filled. So how will they know that?

This is why you need to catch their participant code at the beginning of the survey (here called encID). So you give them the link to the survey, and they will add their encID at the end. Each respondent will have such an ID.

So if the survey link says contains "&encID=test" at the end, what will get out at the end is "test". If the survey link they give to the respondent contains "&enc ID=4--8IZ-ngvFB3aJnuUFwLGdg~~", then "4--8IZ-ngvFB3aJnuUFwLGdg~~" will be saved in your survey as encID and then passed on to the endURL.

It is just an ID that you have to catch at the beginning of the survey and then pass on to the URLs that redirect the respondent back to the panel. Therefore you recieved different links. Depending on the links the respondents will registered as completed or not by the panel and receive their points or money or whatever.

So why did Jelo get "4--8IZ-ngvFB3aJnuUFwLGdg~~" in the end url? Because he put it in the start url!