![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Here's my situation: I have a table called Contacts that tracks people and is used across multiple departments. All communication in the organization is stored in a table called Contact Log. Contacts match to log entries based on their primary key, contactID. Each log entry has a Type, such as 'Note' or 'Donation'. My problem comes when I try to make a filtered portal to only display log entries with type 'Donation' and then perform a find through it. I set up this portal by creating a field in Contacts called g_DonorMatchKey which is a global text field that contains the value 'Donation'. I created a relationship called 'Donations' which is: Contacts::contactID = Contact Log::contactID AND Contacts::g_DonorMatchKey = Contact Log::Type I built a portal using this relationship. It works just fine for viewing. It only shows the donations, of which there are 9,000. However when I do a find through this portal, it returns 42,000 records, which is all the log entries, donation or not. It appears to be ignoring the second match criteria of my relationship in performing this find. Can somebody help me understand why this find isn't working? A big thank you, Kevin |
#3
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |