Limiting number of portal results

[James Gill]

Well, I guess I have to ask the inevitable followup question. Given the constraints of not using global fields in stored calculations, what's the best way to go about presenting each user with a "unique" portal viewing experience? I've thought about placing a user specific field that contains a viewing distance of 100 Miles in it and then setting that field manually when they navigate to the record. The only problem with this is that if two users get on the same record at the same time, then the one who was there first will see the portal change to the new view distance. Other than that it seems like the only way for the portal to act independently from one user to another.

Edited August 26, 2010 by Guest

[comment]

But the entire point of this exercise was to allow the calculations to be unstored.

[LaRetta]

I wish I could buy you an internet beer or something.

You can always send cash. :wink2: