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.

Conditional Value List and IWP

Featured Replies

Just for fun, I shared a simple FM file on IWP. I wanted to see how the conditional value lists would perform. Not good.

In FM Client, the second value is set to lookup when the first value changes. This prevents mismatches. I understand that I may need commits after the first value is selected using IWP. I tried that, and a OnObjectModify script trigger, but I still can't get the second popup to lookup. The second popup is only displaying the choices related to the first popup, so the condtl value list is working. However, if the user doesn't enter the second popup and make a choice, they still have a selection that is not valid for the current choice in popup1. The lookup is not working.

What is the best practice for conditional value lists and IWP? (and don't say "avoid them"). I do not want to move to a Wizard-like interface; I'd rather keep the user on the same layout.

I also realize that all my nifty validation dialogs won't display. So, I'll just write my messages to a field on the layout and script my own submit button.

I'm not sure how a lookup figures in this. Does the file here work for you?

http://fmforums.com/forum/showpost.php?post/195641/

  • Author

Thanks for chiming in here, comment.

The clear mechanism at least solves the problem of mismatched choices. In fact, it's better than a lookup.

However, the i/f is still a bit weak. If the user doesn't submit after selecting the primary selection, their choices in secondary are not updated. So they will see a mismatch. Submitting clears the secondary choice. Now the user must go back and choose a secondary, and resubmit. It's awkward. I know script triggers don't work as they do in FM client, but I'm hoping I can avoid two submits. With multiple condtl value lists on a form, I can't require so many submits.

I also need to figure out how to not allow a record without a secondary choice value.

Snapshot_2009-06-20_18-46-36.gif

Edited by Guest

Well, IWP is quick and easy, but it is far from perfect (and so are conditional value lists, BTW). I don't think there's a way to square this circle. Keep in mind that you are in a browser, not in the application. Nothing really happens until you submit. I'd say look for some other selection method, or perhaps move to CWP.

  • Author

OK. I was toying with the idea of using this little system to finally learn PHP. I was surprised by how well IWP did work.

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.