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.

Problem with multiple criteria

Featured Replies

I have a company table that has a relationship to a "tickets" table. I may be approaching this wrong, but the way I am using the "tickets" table is for several different items. A ticket could be a proposal, service order, invoice, or PO. I have a field in the tickets table that is for this purpose. I thought this is a good approach for me because the user could simply "convert" a proposal to a service order and almost all the data is carried over without having to move the data to a Service Order table. However, in my company table I want tabs for the user to view a portal of Proposals, SO's etc. I have created a new TO of the tickets table and defined multiple critera (ex CompanyID = FKCompanyID AND SOTicket = TicketType) with SOTicket being a global in the company file with the value "so".

I have tested this in a very simple test file and it works perfectly. However, in my real solution I am getting different results. It has worked properly at times and I could change the value of tickettype and it would be removed from the portal, but other times I just end up getting a duplicate of the first matched record. For example if I have ticket 2000 and 2001 in the ticket table for the same company. When I go to view the data in the portal it just shows 2000 twice. If I change the "type" of 2001 it will only show 2000 once in the portal.

Initially I had found that at least part of the problem was that I was not indexing the ticket type field, and once I did this and deleted the records in tickets it began to work on new records in the tickets table. It has since began to do this since. I am obviously missing something because in my test file with the same setup it works perfectly everytime.

Any help is greatly appreciated

  • Author

Thanks for looking, but I found the problem!

It seems like strange behavior to me, but the problem was the fields that I had placed in the portal were to the relationship to the TO with only the single criteria. When I changed the fields to be from the secondary TO it worked perfect.

It seems strange to me that it would populate the portal in this fashion (showing the first record repeated). The way I discovered the problem was to create to completely new TO's of both sides and change the layout to be based on the new Company TO. When I did this all the fields showed . It seems to me if I had the portal setup to show records from TO-2, but fields to TO-1 it would show the in these fields instead of showing the first related record???

Either way I will not make this mistake again!

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.