Filtered portal not working in IWP

[Breitenbush Office]

I am using relationships to display certain records within a portal row. I use this in a number of areas within my database that is intended to be used via IWP. Everything worked fine until I recently added another criteria to one of the relationships. Now I am having an issue where when you first log into the database via IWP the portal row shows as empty (even though there should be data). If you navigate to a different record, and then navigate back the data suddenly appears. The issue is not present when using the database with Filemaker.

The first page that appears on login displays data from a Global table. In the relationship graph the Global table is related to the Day table (date = date), and then the Day table is related to the Session table (date = date AND field1 NOT EQUAL TO field2). The portal row that displays is showing data from the Sessions table. The date field in the Globals table is automatically set to today's date by the startup script.

I figured out it isn't related to fields contained within the portal row (I removed all fields from the portal except for one basic text field and the issue persists).

I also created a very simple database with the same structure and am able to reproduce a very similar issue (the main difference being that I can't get the portal data to display at all in IWP, even when navigating to a different record and back). I will attach the file to this message.

It works fine in FMP, but if you access it via IWP the portal row is empty.

I have asked a friend who is an expert with FMP and she cannot figure this out. Thanks in advance to anyone who can help with this!

-shawn-

iwpissue.zip

Edited February 23, 2010 by Guest
Added file as attachment.

[IdealData]

Your link to the file "fmpissue.zip " does not exist. You would be better off attaching the file to your posting.

[IdealData]

Everything worked fine until I recently added another criteria to one of the relationships

That must be where the problem lies.

[Breitenbush Office]

I think I finally figured out what was causing this issue. "Field1" in the relationship was set up as a global field and I tried changing it to a normal field with auto-enter of the desired value. This appears to have remedied the issue. I thought the global field set up with an auto-enter value would work fine for this situation, but it must of been causing some weirdness for IWP.

[bobearl]

It sounds like you have it worked out, so this may not be helpful; however, I had a similar issue where filtered portals were not working in IWP though they worked fine on the local client. It appears that the global fields used for the relationship must be actively set in each IWP session, so one way to do this is to explicitly write your global fields needed for the relationship in a startup script.

I found a helpful post about this which I can't find, but I think it may have been from bcooney, in a search for something along the lines of global fields IWP portal. I'm sorry I can't find the link, but