Jump 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.

Different behavior when submitted via Web

Featured Replies

I have a web companion form that has a check box in it. After the form is submitted via the web, I can view the record and see that the checkbox is marked. But when I run a calculation on the field, its as if it is not marked.

The checkbox is using a value list that only has "Yes" in it. Therefore, checked = yes. I then have a script that does "If <checkbox-field> = "Yes" insert text "1" in <another-field>.

Oddly enough, if I fill out the form within filemaker, the script inserts a 1 into the other field whenever I run the script and the checkbox is marked. What is different between the web companion and filemaker? I can't figure this out.

Thanks all.

--

Chevell

Hi, Chevell! I'm not Script-Wise enough to advise or discourage you from using scripts on the web (debatable issue), but you may want to read some posts on the subject. As to differences between Web Companion and FMP-direct, there are some but I don't see why it would be in this case... maybe someone else can see it?

My guess, though, is that something isn't quite coded right in the CDML. Still...

(Q) After new record via web, is the check checked properly from the db point-of-view?

(Q) Are you sure the script is executing through the web correctly / at all?

(Q) If you make another layout and view the field NOT as a checkbox, does it look OK? Right now, I have a problem with an extra return/break <BR> being inserted in my check box values and maybe the same is happening to you? (instead of "yes", I get "<BR>yes")

There are other issues with check boxes, too. Use a YES/NO radio button instead if you can and it may save you some trouble down the road.--ST

when in doubt: text fields will accept almost ANYTHING

but WHY:

"The checkbox is using a value list that only has "Yes" in it. Therefore, checked = yes. I then have a script that does "If <checkbox-field> = "Yes" insert text "1" in <another-field>. "

makes no sence ....why go back and forth just set the web form box value to be =1 or 0 if use some JS (If x="" then x=0)

and of course the "script over the web" flaming issue....

-I am a speed freak - the faster the wwww the better .... I have not see a "fast" FM.script yet....they DO work but it is just another thing that can go wrong. [no more comments about script] lol

All the best!

Gentlemen, I believe that Chevell is using IWP. Unless you have some insight into how IWP generates format files on the fly, I don't think you can really help Chevell.

I did notice recently that FMI Support has a Tech Article on IWP and checkboxes. No, I didn't get the article no, 'cause I could really give a flying-frog about IWP. But it's there and if Chevell is diligent it can be found. I believe the search criteria I used was "checkbox" (no quotes) if that is any help. I think there were over 125 results, so each page that came up I did a JavaScript find on "checkbox" (no quotes) to speed things up (avoid the sales pitching articles).

Bon chance

Create an account or sign in to comment

Important Information

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

Account

Navigation

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.