Portal records do not display

[WilliamCB]

I'm using IWP to show some data from related tabl;es in portals. This all works fine most of the time. But then I get portals that simply refuse to display the data in IWP. Does anybody have any idea why this might be? (Obviously the portals display fine in FM itself).

A bit more background:

Portals are contained in tab panels - one per tab panel

The data to be shown depends on some complicated calculations using many related tables.

Many thanks in advance,

W.

[WilliamCB]

OK. I have an answer to this. I suspected it was that the relationships were too complex. So I went into the relationship diagram and started removing criteria from the relationships. Bingo! Data started coming up. But then I put all the criteria back in - and the data I wanted was right there.

So this is a bug with the relationship dependencies, which does not manifest itself except in IWP. And it's easy to remedy.

BTW I wish someone would create an IWP FAQ page that lists all the known limitations and problems. Because at the moment, there's a general whinge about the limitations and problems - but if we all knew what they were, they'd be much less limiting and problematic!

[IdealData]

Is the data split between separate files?

If so, you may have a relationship consideration that is using a file where the fmiwp extended privilege is not switched on.

Wanna post your file so we can share in you bug discovery?

[WilliamCB]

The whole solution is in one file, so access issues aren't part of the problem.

I don't think I can post the file itself - too big and too much IP wrapped up in it. But I'll happily try and work up a slimmed down version that recreates the problem if that is useful. But I'm slightly wary because this bug may only reveal itself in more complicated databases. And in fact, I now have a second, similar issue that only shows up in IWP...

I have a portal displaying records from a related table. The portal rows show. Fields from the related table show - except for some calculation fields. These are where the calculation is defined in the context of a table instance that is not the instance being displayed in the portal. So the portal is displaying records from "Organisations 7" but the calculation is defined in the context of "Organisations 2".

This seems to be more a limitation than a bug.