Bizarre Error Concerning Portals

[Jonathan Veit]

Hello,

  

  I'm hoping for someone might point me in the right direction for this strange anomaly.  At first, I wasn't sure what was producing the error but I have to do is login through IWP and on the first page, all I have to is click edit and then submit.  This first page has two portals, one for the projects, and the second for the requests of those projects.  A few "random" projects will duplicate their title within the projectName field.  Something like "Hotel Sonesta" will become:

 

"Hotel Sonesta

Hotel Sonesta

Hotel Sonesta"

 

There is no auto-enter, and no script involved, and I've been trying to figure out what might ties this projects together but I have no clue.  Anyone have any idea?

 

Jon

[Lee Smith]

Is this a portal, relationships, related record problem, script, etc.?

Did you create the file?

Does this problem happen if they are not being served?

[LaRetta]

It sounds like the field is pointed to the wrong table occurrence in the portal.  Check each field and make sure they are pointed to the same exact table occurrence name as the portal name.

[Jonathan Veit]

Ah Thanks LaRetta, I suppose I was being ambitious putting a field related to the table occurrence for the portal inside the portal.  I got rid of this and my problem went away.  My confusion has to do with the fact it worked to certain extent.  What are the rules about doing this, is it just bad etiquette? an absolutely wrong way to do things?

 

Jon

[LaRetta]

Not wrong at all ( sometimes quite handy if the relationship works ). You will get results depending upon how the relationship between the portal and that field's table occurrence evaluate in the given context.

If the bogus field comes from a CHILD table occurrence (of the portal's ) then only the first related ( grandchild ) will be seen which could be why it worked to some extent. One way to get a clear grasp on what to expect is to create some test relationships ( 3-4 deep ) and start playing. Copying the graph and looking at the connections (1:n or n:n etc ) while you do will help you grasp context on how it translates.  Knowledge may be power but in FileMaker context is king.

Besides not understanding the context, it is also a common error when duplicating a portal ... forgetting to re-specify the fields inside. I know all too well, LOL.

Edited February 22, 2013 by LaRetta