MaddHatter

I finally figured out how to do this. When a Customer selects a photo it assigns it the Customers::Key. So here's what I setup Parent Table Child Table un-stored Calc field with value "1" <---------------------------------------------> Stored and Indexed Calc field with value Case (not IsEmpty (_fkCustomers) ; 1) (The above shows all photos that have been selected instead of only the ones associated with the current customer) un-stored Calc field with value "Not Emailed" & ¶ & "Rejected" <---------------------> Stored and Indexed Calc value of Photo::EmailedStatus & ¶ & Photo::ApprovalStatus (I learned that setting up a relationship like this creates an OR relationship between the two keys it creates. You can easily accomplish this with a Portal Filter but it's not as easy to do when creating relationships.. UNTIL NOW!) Two important points for those coming here afterwards with the same problem. 1) The value on the right side of the relationship value can never be an un-stored calculation field or it will not work (for any relationship) The field has to be indexed so it has to be stored. 2) The Paragraph returns (& ¶ &) create keys on both sides. These correspond to each other so "Not Emailed" will relate to Photo::EmailedStatus OR "Rejected" will relate to Photo::ApprovalStatus By the way BruceR you added nothing to this conversion at all. You offered no advice at all about the subject at hand (even after I said that in needed to be done with a relationship) So I didn't get any expert advice from you ole' Sport 1) This was posted in the RELATIONSHIP section of the help forum 2) I made it very clear How and Why I needed to set it up as a relationship. If you read my original post you would have seen that. Thanks for stopping by and half reading the post before you decided to talk down to me. Maybe next time you could try to extend some sort of advice AFTER you read through EVERYTHING. Thanks to everyone else who offered advise I tried to take everything (except BrucR's comments) into consideration while figuring this out.

I understand Bruce but, as stated above, I need to set this filter up using a relationship so that I can use the portal on one of my Filemaker PHP api webpages. I can create this list very easily with a search. Did you read the previous comments??

Hi Webco. I'm not sure that I'm following you. How would I setup the relationship with what you're suggesting to do? What table would the portal be put onto and what would the relationship match criteria be? Again I'm trying to show ALL of the photos that have a Customer:Key and then further filter this list with those criteria. I'm trying to setup a relationship I could very easily have found these using a search. Did you read the post? Hi Webco. I'm not sure that I'm following you. How would I setup the relationship with what you're suggesting to do? What table would the portal be put onto and what would the relationship match criteria be? Again I'm trying to show ALL of the photos that have a Customer:Key and then further filter this list with those criteria.

How would I set that search up?

I I need to setup a portal relationship so that I can access the list from PHP page using the API. Is there a way to setup this relationship?

I just want to make sure that I'm understanding this properly. Are you saying that I should match Customers::Key <-> YourCalculation in the second TO and also match Customers::Key <-> Photo:::Key in the the original TO if so what TO portal do I put on the Customers layout? Also will this method show All photos that have Customer::Key <-> Photo:Key or just the photos associated with this Customer:Key? I want to show ALL photos for all customers that have a matching key in the Photo table (not all of them have one) and then filter with those other criteria.

(I'm using Filemaker Advanced 15 on Mac OS X El Capitan) I have some filtered portals that I need to turn into portals that are filtered by relationship. I can not figure out how to set this up properly. I'm trying make a portal that will show me a list of all of the photos that still need to be Touched-Up. When a photo is selected for touchup the customer record is linked with the Photo by a key.Customer -> PhotoAfter the photo is emailed out for touchup "EmailSent" goes into Photo::EmailedStatus and if the touchup comes back and needs to be sent out then "Rejected" goes into Photo::ApprovalStatusI tried to make a self-join relationship between Customers and CustomersJoin and make a cartesian join between the primary fields and then add the rest of the filters using Calculation Fields and Global fields but I can't figure it out because the calculation field needs to be on the left side. I'm not sure if I'm approaching this right can you help me out?1) What Table should the layout be based on? I have it on Customers is that correct?2) How can I filter this using this relationship? Am I approaching this right? I want the list to show ALL of the photos where Customers::Key = Photo:::KeyANDPhoto::EmailedStatus = "Not Emailed"orPhoto::ApprovalStatus = "Rejected"