11 Replies Latest reply on Jan 15, 2010 12:25 PM by blewvelvet

    Portal or relationship won't work



      Portal or relationship won't work


      I'm having major problems with filemaker portals in a larger database.

      The main issue is with three tables, Project, Items2Buy, and JOIN_Proj_Items.

      Once I add a portal to Projects and/or Items2Buy I can't see the related items. I know how to do this trick, I've done it before. For sanity, I made a new database with the same three aforementioned tables, linked them together with some filler data and it worked fine. However, it's not working in the database I'm trying to use.

      My JOIN_Proj_Items table works fine. I have an FK for Projects, and one for Items2Buy. I can pull in information to a record in the JOIN fine.

      My portal is set to the JOIN table, I added fields from Projects or Items2Buy to pull in data, I've checked to make sure I was looking at the correct records for the effect. Both portals, the one in Projects, and the one in Items2Buy won't show my info.

      I have a suspicion this has something to do with an overlinked Projects table. Filemaker balked at multiple connections to one table, so I ended up with an alias table, Project 3 to connect to my JOIN.

      Elsewhere in my database I have 2 other JOIN tables. One works fine and another pair don't work, but I'm hoping the solution to this answer will solve my other problems.

      I can email the file, but I'd rather not get to that since it's not one cohesive file but multiple files referenced together.

        • 1. Re: Portal or relationship won't work

          Are the fields that are in the portal the right context? That is, are the using the same TO as the portal?


          You might benefit from reading a white paper on the Relationship Graph. FMI has a Developer's Conventions whitepaper that helps you approach the relationship graph in more complex solutions. I am a fan of the Anchor-Buoy methodology. Your Project table isn't overlinked, it is that FM won't allow circular references in the RG. 

          • 2. Re: Portal or relationship won't work
               Where can I find the FMI Developer's Conventions whitepaper?
            • 3. Re: Portal or relationship won't work
              • 5. Re: Portal or relationship won't work

                At some point you will need to redo your relationship graph. I'd go for it now. It'll pay off tremendously as you build more complexity.


                It works from the context of Projects3 bcs there is a relationship to the Join. If the layout is based on the Projects TO, then create a relationship to the Join from Projects.


                You must understand the concept to context in FM. Think of it as the room you're in and any relationship is a window to another table. If you're in a room (TO) without a relationship to another TO, then you can't see another table.

                • 6. Re: Portal or relationship won't work

                  Thank you for all your help. I think my solution was strongly about grasping the circular-reference issue that FM won't let happen.


                  I rearranged my RG to look like the a/b method. I feel good about more ambitious solutions with Filemaker.

                  • 7. Re: Portal or relationship won't work

                    I think I may have the same problem.


                    This is a film company..that has a CLIENTS (table) which created new PROJECTs (table)...and we have CREW (table) working on multiple projects and sometimes appear in multiple portals in a project - we have other things going on like TALENT and VENDORS..but it should not be relevant here since all those portals work.


                    The Portal success is that CLIENTS layout portal can see all their projects. - nice..and how much they owe etc.


                    RE: CREW portal


                    Need to see a PROJECT PORTAL on CREW LAYOUT which shows the PROJ ID and NAME AND.. INCIDENTS that a CREW member has been in on the surrounding tables..


                    Each PROJECT Unique ID.

                    2 UNITS or film crews per day.

                    Each UNIT is a portal has their own incident table (D1 U1, D1 U2  or ( Day / Unit ) ) because the same Crew member may be on two units that day or on multiple days. (this portal selection of crew members works nice and we get their photo, cell phone etc on the call sheet -nice!

                    Each incident/record pull their DAY rate /HALF DAY rate and calculates their rate in that incident. We can manually adjust the rate and number of in that incident/record.


                    Ok..so now all those incidents where CREW appear on a project (various days and units) from those various incident tables...do not show up on their individual record in the CREW layout. I did complex relation connections and simple ones by just linking the PROJ ID..which is the primary KEY FIELD used on the main relationships you see coming off the PROJ Table.


                    I've seen that too many relationships can mess things up..all links to the Call Sheet work nice with merged fields..but..when I try to seek out all incidents for the units (each record in each incident table has unique ID key field)


                    But I've tried everything I've read and even been on Youtube videos for answers..its probably simpler than I'm trying to make it.


                    Do I need to create a new incident table (with a new Record ID) to bring together all the incidents created for that crew member?


                    See what I have below.


                     FMPro Screen shot


                    Somehow that upper main CREW table must generate a portal that can see all the other records that are created in those other highlighted tables. I have limited scripting abilities and don't understand the more intermediate scripting using variables.  


                    But my Database looks great and super-user friendly..! which is probably my design skills coming through.


                    Just feel like I've hit the wall! If I can get this multiportal concept to work..I will feel like Wonder Woman. If I can get a solution..I'm going to play the theme in the office.

                    • 8. Re: Portal or relationship won't work

                      Looks like your database is suffering from an excess of tables. Just using your Crew D1 U1 through Crew D6 U2 tables for an example, you can store all those records in one table by adding a pair of fields to identify the day and the unit. You can then use these new fields in relationship and when performing finds to find all related records for any given day and unit designation.


                      With just one such table, your entire database then becomes much, much easier to work with.

                      • 9. Re: Portal or relationship won't work

                        yes..I thought of that..but would I be able to create separate portals when selecting during input?


                        As I have below..we think out the day's events..and who needs to be there in that unit..and make adjustments to their rate and order of call time...visually. We have to constantly adjust information..remove and add people.


                        Crew and Talent Input

                        • 10. Re: Portal or relationship won't work

                          You can set up a filtered portal or portals to display just the information for once such group of records.


                          If you click the advanced search link and search under those terms, you'll find lots of examples of this method.

                          • 11. Re: Portal or relationship won't work

                            Thanks so much..I'm going to lookin to "Filtered Portals"..and see what I can muster.

                            Get back with my solution.