back to top

SalesLogix Basics 3 – Radio Buttons VS Radio Group controls

For this basics article, I just wanted to outline the differences between the Radio Button and Radio Group controls, and when you would want to use one vs. the other.

Both controls provide a similar sort of interface to end users, allowing them to select one out of many available options.  Differences in how the information is saved, however, could determine which method is used.

 

Using a radiogroup control, you would only need a single field in the database to hold the resulting value.  In addition, the value stored is the actual string displayed in the group itself.  In this example, I create a field called “GroupOptions”.  When this record is saved, the value of “Test1” is stored in the database.

 

To set up the radiogroup control, you just need to add each option to the “Items” property of the control.  If you set the “Columns” property of the control, then the options will be split evenly between however many columns are defined.

 

 

With radio buttons, you would need a field for each option.  A value of either “T” or “F” is stored for the option selected.  For this example, I’ve created 4 fields; “GroupOption1”, “GroupOption2”, “GroupOption3” and “GroupOption4”.  When this record is saved, a value of “T” would be stored in the “GroupOption1” field, while “F” is stored in the “GroupOption2” – “GroupOption3” fields.

 

Radio buttons only allow one selection within whatever control container the radiobuttons are contained.  In order to group these specific options together, I’ve used a panel control as a control container.  Do do this, you just need to drop the panel control on the form, then drop the RadioButton controls on that Panel control.  Each radiobutton is a seperate control.

 

So those are the main differences between those controls.  To summarize:

Radiogroup:

  • Only one control needs to be defined
  • Only one field needs to be added to the database
  • Literal value is stored in the database

RadioButtons

  • A field for each option must be added to the database
  • You must add a control for each field
  • If you want to set up multiple option groupings on a form, and additional control container must be used (such as a panel control)
  • “T” or “F” is stored in the database for the option selected.

 

Thanks for reading!  [:)]

Contact Customer FX for your CRM project
We let our expertise speak for itself - let us know how our all-star team can help on your CRM project
About the Author
Jason Buss
Jason Buss
Jason is a senior application developer with Customer FX.

1 COMMENT

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Infor CRM SLX 10.0: Delegate Ownership Changes for “Everyone” Records

Learn how the new EveryoneOwnerAssignment secured action in Infor CRM SLX 10.0 allows designated users to change ownership of Everyone-owned records without requiring Administrator access.

Related Articles

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Related Videos