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.

Possible? Portal Duplicate Filter...

Featured Replies

I'm making a tour managment database.

As of now, I have crew and bands related to the tour. To add crew or bands to the a tour, i have 2 portals; one listing all crew, one with crew on the tour. I have buttons in the portal to add/remove them. That works fine.

But what I want to do is filter out crew that are on the tour already so they can't be added more then once.

Can anyone think of a way to do this?

Hi,

I did something similar for events.

The way I got around it was to create a field in the users database for on event.

This was a return delimited list.

Everytime a new event was created that id was added to the users delimited list.

Then the portal was set to display users with a matching project in their record. This was linked to a global field in the main database.

So, all users appear in this portal where you can add them to the event.

now, when adding a member to that project a new record was created for that user in the events members.

Then a set field script was run, substituting the project id for that user in the on event field with project id & ":0"

This removed the user name from that portal, stopping them being selected twice.

Another portal sat to the side listing all the event members.

Also, you can reverse this so you can remove the user from the event, and they appear back into the other portal.

If you want an example I should be able to put one together for you.

HTH

  • Author

Thanks for the reply...

I think i get what you mean, i will try some variation of it.

Just did a test that works:

Define 3 fields:

In Master database:

g_Avail_Crew_Key (either a global number or calculation) = 0

g_Tour_Crew_Key (same as above) = 1

In Related database:

Crew_is_on_Tour_n (number field, stored, auto-enter "0")

Define 2 relationships:

Avail_Crew (g_Avail_Crew_Key->Crew_is_on_Tour_n)

Crew_on_Tour (g_Tour_Crew_Key->Crew_is_on_Tour_n)

Define 1 script:

Toggle Crew_is_on_Tour_n

Set Field [Avail_Crew::Crew_is_on_Tour, Choose(Avail_Crew::Crew_is_on_Tour_n, 1, 0)]

Go To Field []

You can put Crew_is_on_Tour in the Avail_Crew portal and specify it as a button that calls Toggle Crew_is_on_Tour_n.

You can make a similar script to toggle the crewmember off the tour.

[Edit: Changed some names to preserve Crew/Tour analogy]

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.