Skip to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Checkbox calculation problem

Featured Replies

I am trying to code conditional formatting based on whether or not a single value in a checkbox set is checked (regardless of the other values). I found this FM Support answer that says clicking a single box returns results based only on that checkbox, but when I write a calculation, this is not the case. For example, I have a field with four possible values. If I use the calculation [ table::field = "value 1"] to run conditional formatting on a related field, it is only applied when "value 1" is checked and all other checkboxes are empty. I want it to apply formatting independent of other checkbox data. What am I doing wrong? Thanks for your help!

I am trying to code conditional formatting based on whether or not a single value in a checkbox set is checked (regardless of the other values).

Try =

not IsEmpty ( FilterValues ( "single value" ; CheckboxField ) )

This article is about performing a find and irrelevant to your question.

  • Author

Awesome! Thanks!

Or you could make a calc like this.

PatternCount ( CheckboxField ; "single value") > 0

Or you could make a calc like this.

PatternCount ( CheckboxField ; "single value") > 0

No, that's not a good idea, because it searches for a string - and the string may be contained in another value.

I'd like to suggest NOT using a checkbox set. I rarely do. Perhaps these should be related child records? Reporting, finding, etc., on checkbox sets is more difficult than doing so from a child table.

I'd like to suggest NOT using a checkbox set.

Hmm.. wouldn't you want to know what this is about, before making such a radical suggestion? I can't see nothing inherently wrong with checkboxes as such.

I did say "suggest" and "perhaps." I don't think it's radical. I think that beginners use checkbox sets rather than child tables all the time, and live to regret it.

LOL, very good Vaughan.

Without wishing to hijack the OP is there an easy way spit the checkbox values into a child records?

My first thought is to run a loop script and getvalue.

My other thought (if it would work) would be to parse the checkbox field to a repeating field (using a recursive custom function?) and then import using the splitting repeating fields option.

Both would work.

parse the checkbox field to a repeating field (using a recursive custom function?)

No custom function is necessary; use GetValue () with Get ( CalculationRepetitionNumber ).

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.