Lookups not responding as expected

[Mark Appleby]

I am real trouble here. My lookups are not responding as they should. when I create a record in a portal the values in lookup fields (there are several) are not looking up.

If I put it in a second time It does lookup where am I going wrong!

[CobaltSky]

Hi Mark,

It is just possible that your problem is that the portal is not refreshing, rather than that the lookups are not working.

Before you tear any more hair out, test the lookups out in the file that they are set in and see if they work there. If they do, set up the two files side by side so that you can see the field in both files at once. If the problem is refresh-related, that will become evident.

One of the things that can impede portal updates is if there is an invalid sort defined for the relationship the portal is based on. Another is if there are fields from another relationship in the portal. If that is the case, you may be able to make some changes to the portal to improve matters - otherwise you may wish need to consider setting up an 'update' script to refresh the portal (eg looping through to the last row then exiting the record).

[Mark Appleby]

Ray,

Thanks for getting back to me reagrding this problem, I put the same question out a few weeks ago but got no answers. I now have to tackle this problem.

The problem is as you suspect. The lookups work if I create a parent record then go into the child child file and create items there. The whole problem seems to be in the portal.

The thing is, I need to be able to enter the informaiton in the portal as to switch between databases will take too long, as I usually only have to change a few details between a number of the children. It would be best if I could enter it this way.

Both files are sorted on the parent key (linking field) followed by the child record ID.

What I can tell you is that when the lookup doesn't work I just delete the portal row then add a new one. This time it will work. Would this mean that it is a refresh problem? If this is the case is there any way I can get over it without making the user having to start a script?

[CobaltSky]

Sorry I missed your post first time round!

It does sound like a refresh problem, Mark. From what you are sayin, it may well be linked to the fact that the key field for the relationship is included in the sort (since the portal records are being selected by the key field, it has no meaning to simultaneously sort by that field).

I suggest you take the sort off and see if that makes a difference.

If a script is necessary to force refresh (it shouldn't be if everything is set up properly) you could make it relatively painless by putting a button to trigger the script in the portal rows, so users don't have to go anywhere. At least it's a lot easier than what you're doing at present - deleting the row and adding a whole new one...

Cheers,

[Mark Appleby]

Ray,

Your help on this has been very welcome.

I have removed all sorts for the moment. The problem is still there. Where could this not be set up properly?

I tried the refresh script and everything works fine. While I would prefer not to use it. If I have to I would prefer as little mouse use as possible in order to speed up data entry.

In order to try get to the bottom of the problem I even deleted the relationship and re-created it. I can not see where I could go wrong.

Thanks,

Mark

[CobaltSky]

Sounds like the problem is with the portal rather than the relationship. Portals generally 'bounce' and refresh everytime you exit the record.

If you want to get to the bottom of it, I'd suggest re-building the portal one field at a time, seeing if it will refress on exit. It could be that there is a particular field or object in the portal that is constraining it (as I mentioned before, a clac field referencing several files or a field sourced via a different relationship are examples of things that could mess with the referential integrity of the portal).

Failing that, you might want to consider placing the refresh script on the menu so that it can be called from the keyboard. Not your ideal solution, I know.

Cheers,

[Mark Appleby]

Ray,

I have tried recreating the portal but I am getting the same problem. I checked all fields but they are all from the child file.

I think that the problem is more that the Parent record needs to refresh before I enter the protal. This would get rid of the problem completely. At the moment I have included the macro but I would love to get to the bottom of this.

Many thanks

Mark

[Gabriela]

Hi,

I have the same problem, but have found that the child file looks up fine from other related files, but not from the parent file. Like Mark, I have found that the problem only occurs on the first portal entry, even then not always.

I have overcome it by putting a re-lookup into the print script. It works for my situation because I don't need to see those look-up values in the portal, but need them when printing (in this case an invoice).

Would like to hear if anybody finds a solution to this.

Gabriela

[Vaughan]

What relationship is the lookup based on that isn't working?

[Ugo DI LUCA]

Hi everyone,

Hi,

I know this is an old post, but...

If someone found the problem, please tell. If not, here is a very simple file that illustrate that strange behaviour. FM5.5 on MACOS8.6.

When procesing a new PO, the Customer ID doesn't enter in the Line Item on first line of portal.

Thanks for any help here.

ProblemLookup.zip