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.

A simple problem with value lists?

Featured Replies

Hi, 

I'm trying something that seems very simple, but I can't make it work for some reason. I've tried all sorts of joining tables etc.

I have three tables: A, B, and C. Table A is the parent of both B and C. (so there is no actual relation between B and C, but there are records in B and C with a common A father).

I want to add a field to C that will store a field's value from B.  For that, I want to create a value list of values from B for the user to choose from. However, I do not want to show every possible value from B, only those that share a common father in A with the relevant record of C. 

Is there a simple solution for that?

Thank you :)

Define your value list to use values from field B:Somefield, include only related values starting from A.

--
P.S. Please use meaningful names for your tables and fields when asking; abstract examples are very difficult to follow.

 

  • Author

Thank you for your reply. I will use meaningful names in the future, sorry. 

My first thought was exactly what you describe (this is why I thought it was simple),  but it didn't work. 

I've tried it again and realized my situation is more complicated. While it works perfectly in a simple layout of C (I'll stick to these names for now), I'm using a script that opens a new window as a card for creating a new record in C, and the user should choose the value from the list there. I don't understand why it works in the simple layout but not the card. Any idea?

6 minutes ago, Sharon said:

Any idea?

Not really. If the layout of the card window is a layout of C, then it should make no difference. Perhaps you're using a different occurrence of the C table - one that is not related to A and through that to B?

Of course, if it's a new record then the user must first select a parent from A before they can choose from the values in B that are related to the selected parent.

 

  • Author

Ok. I realize my mistake now. I've used the value list not for a simple field but for adding records in a portal that shows lines of a joining table. I understand now that the context of the portal is not the context of the layout it appear in, but rather the context of the joining table. I solved it with another instance of a table and it seems to work fine. Thank you very much for your time and answers :)

Create an account or sign in to comment

Important Information

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

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.