CSPro Users Forum

Not sure I understand. Maybe the keyword reenter will help you out. https://www.csprousers.org/help/CSPro/reenter_statement.html If that's not helpful can you try to clarify the intended behavior. Also, attach the application with partial data and instructions to get the the particular field of the ...

Can you post or email (cspro@lists.census.gov) the URL? If the URL is constructed try outputting the string using the errmsg function. I'm curious to see if it is double quoted, has a space, or something else funky is going on.

The HTTP 500 error just means something went wrong on the server. However, I can't say much more. Attach the sync log from the device that was synchronizing with the server. Hopefully, it will have some more details.

Typically we use a menu to do this. If we know the households in advance we'll create a dynamic value set to select them. Then using the PFF object and set the key property. As long as the key property is set the household application's ID items will be pre-filled when the PFF is executed. I recomme...

I'll take a look at it if you send the application, dummy data (before data is missing), and instructions to reproduce the issue.

You can change languages by select the "change language" option in CSEntry's UI. Additionally, since you can programmatically set the language you could also add a field and do this as part of the questionnaire.

setlanguage helps: https://www.csprousers.org/help/CSPro/s ... ction.html

I've attached an application with a single id item and a multiply-occurring record with two fields. Can you download it and let me know if you're able to reproduce the issue? If so provide instructions to reproduce and I'll take a closer look.

Looking at the screenshot above you would:

• Add a value set
• Add the two labels in French
• Switch the language
• Translate the two labels

You've created two value sets with no values. Since they have no values they're removed. Try adding a value then saving.

The production value on these first few videos looks great. Plus you do a great job of explaining your implementations.