10 Replies Latest reply on Aug 8, 2012 8:48 PM by vidkid98

    portal problem - adding items


      I have a database with master/child tables. When I create a new master record in a layout with a portal to the child table, the very first portal entry appears to be duplicated in an odd fashion. The attached screen shots show the progression from starting the first portal record to after another portal entriy is made--the result shows 3 portal records when only two were intended. Any ideas? I have attempted to verify that the fields in the portal are totally encompassed by the portal--the shading in the screen shots shows the boundaries of the fields from the child table that are used in the portal.



      s1 new record no data.jpg

      this shot shows portal before any data entered but field2 is active and waiting keyboard input

      s2 data in fld1 wo tab.jpg

      this screen shot shows data entered in field2 of first portal record, no tab or return key


      in this screen shot, tab key was pressed to leave field2, data was entered into field3 and cursor is now in field4


      this screen shot shows tab key was pressed through remaining fields in line2 to start another line; notice that value originally entered in Field2 for first line is now blank


      this last screen shot shows result after clicking outside of the portal--portal display is updated with original value of field2 of line 1 restored an another line (2nd entry in screen shot) showing remaining field values entered previously--now showing as a separate child record; then 3rd line shows original values for 2nd line of data entered.


      I have also attempted to recreate the entire layout from scratch and am getting the same result. the data is being pulled from a separate/external file--the data structures are stored there; the layouts are stored in the current file The relationship in the external file is the same as what I'm using in the current file--at least from what I can tell from repeated examinations of these two files' graphs.


      Any ideas where else I should start looking for a solution?



        • 1. Re: portal problem - adding items

          I believe that you have the relationship/portal set to create a record when data is entered.  So when you create a new parent record,  the portal shows a record that in reality doesn't exist.  Start entering data and the record is created and really exists going forward.  At the same time a new blank/non-existent record is created in the next portal row.  Notice that the X button in the bottom row/ non existent record is missing.  Enter data in one of the fields and the button will appear.


          A typical way around this is to remove the create record set up and replace it with a button and script to create the new records.  If you can get used to the way it is working,  you can leave it.

          • 2. Re: portal problem - adding items

            thanks for the thoughtful reply.  I'm surprised at the behavior; I've got experience with FMP starting at version 5 and this is the first time I've encountered this little delimna--seems only happening in v12.  I'll keep poking about.

            • 3. Re: portal problem - adding items

              No, it has been this way since version 3.


              You might want to employ different formatting - for example, make the fields transparent - so that  the phantom row is less conspicuous.

              • 4. Re: portal problem - adding items

                This looks different to expected behaviour to me.  When the option to allow new records based on related data is selected in the relationship graph, you will see an empty line in the last portal row as indicated by Bruce & Michael.... but I think the question here is about what is causing the values of "line 1" in field 2 and "401K Plan" in field 3 to spread across 2 portal rows.


                Some information that might help to solve this includes the following:


                1. How is the portal sorted?

                2. How are the records in the relationship sorted from the relationship graph)?

                3. Are there any filters applied to the portal?

                4. Are there any script triggers on any of the fields in the portal?

                5. What is the exact tab order number for each of the fields in the portal?

                6. How is the data between the parent and child table related?


                I had a similar issue in the past related to the way the rows were sorted, but I don't think it affected the first record like this.  As suggested by others though, the empty last line can otherwise be altered with formatting or conditional formatting, or by changing the settings for that relationship in the relationship graph.

                • 5. Re: portal problem - adding items

                  You are right: there are other issues at work here as well. It seems that the portal (or the underlying relationship) is sorted, so that the lines exchange places at commit. Another thing worth checking, IMHO, is whether the fields in the portal belong to the same TO the portal is pointing to.

                  • 6. Re: portal problem - adding items

                    I agree with Stephen, that the problem is the way lines 1 and 2 or the portal have parts of what I thouht was supposed to be line 1.  Let me try to answer Stephen's questions to clarify what problem I think I'm having.


                    1. The portal rows are not being sorted

                    2. the records in the relationship graph are not sorted -- see image below


                    3. I have not implemented any filters

                    4. No script triggers in the fields in the portal (although I've tested it with script triggers and the result is the same (more on this below)

                    5. tab sequence is the default, as the fields appear in the portal

                    6. as shown in the image above, the two tables are related through what I can the transPkey (parent) and transFkey (child); transPkey is auto-generated serial number; no user input; transFkey is a numeric field that I am assuming is created through the portal auto add field--at least that's how I've used it before and it 'seems' to work.  I've verified that transFkey is properly populated with the correct transPkey value depending on the parent/child record set I'm looking at.


                    In a previous iteration, I had a script trigger that populated the 2nd field; I have since removed this trigger.

                    • 7. Re: portal problem - adding items

                      as far as I can tell, the fields do belong to the same TO as the portal is tied to; I will reconfirm.

                      • 8. Re: portal problem - adding items

                        thanks for the feedback on this problem.  I have discovered, apparently, that the problem lies in my unwitting transfer of an application from an earlier version to FMP12--I copied the master and child tables and then created a new database and imported those field definitions--preliminary results indicate that the problem described above has been resolved.  Somehwere else on these forums someone posted a comment to the discussion topic about a developer who's leaving FM.  The comment was to the effect that you shouldn't try to take an earlier FM solution and migrated it to 12.  This appears to be the case--some funny things seem to creep into the mix when/if you migrate.  I will continue to work this as I bring my solution into FMP12 without migration.

                        • 9. Re: portal problem - adding items

                          My experience with the move to FM12 has also been that you are best to start from as close to nothing as possible and rebuild from there, especially for a big solution.

                          • 10. Re: portal problem - adding items

                            yep, I heartedly concur.  I just tried using the old framework and copy/paste into the new--no luck.  Problem persists.  So, I'll have to recreate from scratch.  It has been a painful lesson, but I'm learning from it