Expand my Community achievements bar.

Adobe Summit 2025: AEM Session Recordings Are Live! Missed a session or want to revisit your favorites? Watch the latest recordings now.

Mark Solution

This conversation has been locked due to inactivity. Please create a new post.

SOLVED

Checkboxes as radio buttons not cooperating

Avatar

Former Community Member

And I'm back yet again.

In Livecycle ES 8.2/Guide Builder

I have a group of checkboxes set to display as Radio Buttons (only for the visual value).

Once a checkbox is selected it is not possible to un-select it (in case the user changes their mind, etc.)

Is this b/c they're set to view as radio buttons? When they were displayed as checkboxes this wasn't a problem.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

But thats what Radio Buttons do ....in the Guide definition you can decide to change how to display this content. In the Guide Builder click on the RadioButton List and in the Field Properties you can change the Display Field As to Checkboxes.

Paul

View solution in original post

5 Replies

Avatar

Former Community Member

That is normal behaviour for radiobuttons .....if the user changes their mind they simply click on the option that they want and the radiobutton that was checked will be unchecked.

Paul

Avatar

Former Community Member

That's what I thought too and the actual radio buttons do that; but these checkboxes that are set to DISPLAY as radio buttons do not. I'm using them this way because I just want them to look like radio buttons but not be mutually exclusive.

Avatar

Correct answer by
Former Community Member

But thats what Radio Buttons do ....in the Guide definition you can decide to change how to display this content. In the Guide Builder click on the RadioButton List and in the Field Properties you can change the Display Field As to Checkboxes.

Paul

Avatar

Former Community Member

It's actually the reverse. They ARE checkboxes that are set to just LOOK like radio buttons. They aren't set to be mutually exclusive because they are actually checkboxes that I don't want to be mutuall exclusive.

They work fine on the pdf form---they look like radio buttons but don't act like radio buttons. And you can deselect one that was mistakenly selected. However in the guide builder and the preview in the web browser, you cannot deselect them. You can select all of them if you want but you can't change your mind and deselect any of them.

I'm sorry, I don't think I'm doing a very good job of explaining this.

Let me try it this way:

on the form there are 3 different sets of mutually exclusive radio buttons--A,B,C. Then there's a fourth set of choices,D, that are NOT radio buttons (so not a radio button list but each a seperate checkbox) b/c they do not need to be mutually exclusive. In order for all 4 sets to look the same, I took that fourth set of checkboxes, D, and just made them look like radio buttons but not act like radio buttons.

In the Livecycle Designer window set D is made up of several checkboxes (in the object field, type is Check box, appearance is solid circle for each of them)

In the guide builder, from what I can tell, they can look like radio buttons, several can be selected at one time (therefore not acting like mutually exclusive radio buttons) BUT you cannot unselect them once they're selected.


Avatar

Former Community Member

In reading over my last post I see where I went wrong, kind of.

In guide builder, edit field properties (for each sep "checkbox") they can only be set to LOOK and ACT like checkboxes or LOOK and ACT like radio buttons, but not act like checkboxes and look like radio buttons.

I think.

I've now confused myself. Is it Friday yet?

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] ----