Expand my Community achievements bar.

SOLVED

radio & checkboxes act as text

Avatar

Level 2

Hi,

I've designed a form with check boxes and radio buttons.  When I view it in the designer, however, I can't select them.  They seem to act as regular text.

I made another form yesterday with the same items which work fine.  So, I created a new form with check boxes on them but they don't work either.  I'm guessing there's a security check here?  I've looked in Options but don't see it.

Anybody know how to fix this?

Paul

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

In the File/Form Properties/Preview tab are you render as an interactive form or a print form?

View solution in original post

4 Replies

Avatar

Correct answer by
Former Community Member

In the File/Form Properties/Preview tab are you render as an interactive form or a print form?

Avatar

Level 2

It was a print form, I changed to interactive which fixed it.

thanks again Paul, you are a "diamond geezer"!

Avatar

Level 2

I have another problem.

I want to have my form select from sets of radio boxes.

I have two columns with multiple rows.  On each row I want two radio buttons, each with mutual exclusivity.

Yes               No

<radio>          <radio>

At the moment I have this set up but I can select both at the same time and cannot deselect either.

I also need this to be 'mutex' but only for each row, if you know what I mean?

Avatar

Former Community Member

In the hierarchy there is a RadioButtonGroup for each radio button. Drag the radio Button object for the No value into the radioButtonGroup for the Yes value. Now you should only be able to select one.

Paul

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----