Follow @dporton

Debugging your surveys with Chrome.

Hello , first off sorry for all the coughs and splutters in this recording but i just had to share what i discovered today. I am sure some of you already new this , but for me it was a life saver. Made my editing allot less painful. I hope you find it useful also.

Tip from Bob Davis : i.engine

A while ago a topic in LinkedIN was started arround Tips & Tricks. There has been some realy great tips and we wanted to make sure that you saw them also.

That is something that is immediately useful over here. I was reminded that we can also pass i.engine=if we want to test particular engines or to pre-cache a project on that engine.

To find out about this URL item and more look here
http://publib.boulder.ibm.com/infocenter/spssdc/v6r0m1/topic/com.spss.ddl/interviewscripting_properties_table.htm

Tip from Bernhard Witt : TestUseSampleMgmt

When testing surveys with Sample Management, it is often annoying that I need a test

 to logon to the survey. In that case, you can change a setting for the project inside DimensionNet: Go to Project Editor, switch to the properties tab and choose the dropdown entry mrInterview (Dimensions). The property to change is: TestUseSampleMgmt which is set to 1 by default. Enter 0 here and the survey can be started without authentication in test mode, while it still requests authentication in live mode. 

This is also great when a client wants to have a look again to the survey, but you cannot easy create new sample

s. 

Tip from Tyler Ball : i.timeout

We also use i.timeout (set to a very low number) when we want to test how some logic will perform after a timeout has occured and don’t want to wait 10 minutes for the standard timeout. This is especially helpful for projects that use restart logic or have redirects that take them out of the survey to a 3rd party and then back into the survey.

To find out about this URL item and more look here
http://publib.boulder.ibm.com/infocenter/spssdc/v6r0m1/topic/com.spss.ddl/interviewscripting_properties_table.htm

Tip from Bernhard Witt : MustAnswer

Another one of my private library:
MustAnswer=false works great for text questions, but not for numeric questions, unless you create your numeric question with an additional

:

<

>Income "Income" long; >

This one does work:

<

>Income "Income"
long

s(
{
- "No answer" NA
} ); >

Whenever I need this, I cant't remember how it works exactly, so that's the reason why I stored that in my library.

To find out about this URL item and more look here
http://publib.boulder.ibm.com/infocenter/spssdc/v6r0m1/index.jsp?topic=%2Fcom.spss.professional%2Finterviewscripting_questions_mustanswer.htm

Tip from Kevin Grey : I.routingcontext

Often people forget the item that can be entered on the URL. I.routingcontext=. I find this a great way to isolate a particularly difficult bit of functionlity in a script (say a particularly complex question). Just put the relevant

 into another context and use i.routingcontext= to run that 

.

To find out about this URL item and more look here
http://publib.boulder.ibm.com/infocenter/spssdc/v6r0m1/topic/com.spss.ddl/interviewscripting_properties_table.htm

Tip from Bob Davis : i.Renderer

A while ago a topic in LinkedIN was started arround Tips & Tricks. There has been some realy great tips and we wanted to make sure that you saw them also.

Extract : One of my fellow programmers asked me if there was a way to test a CATI version of the program using a web link. I reminded him of the ability to specify the player in the URL by using

<

>&i.Renderer=CATIPlayer or &i.Renderer=XMLPlayer >

If you want to find out more about this option then you can read up on it on the online version of the DDL.

http://publib.boulder.ibm.com/infocenter/spssdc/v6r0m1/index.jsp?topic=%2Fcom.spss.ddl%2Fmrintover_html_player.htm

Participants Tips

Have you ever imported a file into Participants and gotten “Attempting to insert data that does not have a corresponding column.” or “String or binary data would be truncated.”?  This post will explain how to avoid these errors by checking and fixing your Participants file manually before importing.  We will first describe the manual method using Excel and then provide a Dimensions script that can also be used to fix these issues.

Read more

%d bloggers like this: