[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 498
  • Last Modified:

Limiting a pop-up menu to only show records marked "active"

I have a clients table that contains the ID, name, and a active field (0 for inactive, 1 for active).

I want to have a layout where a user selects the active client and then moves on to another layout passing the ID as a variable.

The problem - I can't figure out how to limit the field to only display active clients.
0
OTAdmin
Asked:
OTAdmin
  • 5
  • 2
1 Solution
 
North2AlaskaCommented:
Are you displaying the list via a portal?  If you are I can suggest two option. 1) either modify the relationship to include the active field or create a new relationship with the same. 2) use portal filtering when defining the portal on the layout.
0
 
OTAdminAuthor Commented:
No, not via portal.  It's a pop-up menu to select a client and a day below that and then submit to the next layout, passing those variables.  I just can't figure out how to limit the popup menu to only show records marked as active (1).
0
 
North2AlaskaCommented:
So, you are using a value list to populate the popup.  So, I think a relationship is probably your best bet.  Here is a little sample of how you might make this work.  The elements to look at are:
1) Global g_active set to 1 (active) to filter the list
2) The Value list uses the "Include only related records" option.
3) The Value List only displays the name but returns the ID.  (the g_selected field is only used to capture the selection.  You may want or need to do this another way.
4) The Active field is where you would change the status from 1 to 0 to indicate activity.

See if this makes sense...
Popup-Filter.fp7
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
OTAdminAuthor Commented:
Wow, thanks for the sample database.  I see what you did, however I don't understand.  I don't see the process that causes the value list to be limited.  I can mimic this, but I just don't understand.

It also seems like a lot of work when they could just add filtering formula criteria to the value list generation.  But, that is a wish for another day.  :-)
0
 
OTAdminAuthor Commented:
Never mind.  I see it in the relationship.  Now I get it, although it seems like so much work when it could just be a filtered value list.  I guess I don't really understand that whole table occurrence thing.  I knew i had to do it, but I haven't found a good explanation of them.
0
 
OTAdminAuthor Commented:
Hmm.  Possible bug.  I notice that if I flip around a few times in the value list, it changes one of the client names to a 1.  I'm trying to narrow down and recreate the process repeatedly.

What is the purpose of the "g_selected" field in your example?
0
 
OTAdminAuthor Commented:
Never mind again.  Ugh.  I now see my you have that field.  It prevents the name field from being renamed.

Will this still work in a multi-user environment where multiple users are selecting and entering data simultaneously?
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now