AnsweredAssumed Answered

Portal relationship to global field

Question asked by VeronicaDaigle on Jul 11, 2012
Latest reply on Jul 11, 2012 by philmodjunk


Portal relationship to global field


I am creating a layout which shows any records that have been modified in a date range specified by the user. Since I want to show a summary for multiple tables in one spot I figured the easiest way to do it would be to make a portal for each table, and each table has a field called "InRange" which is a calculation field that is equal to "Yes" when the ModificationDate (an autoentered calculation field for each record) is within the date range selected by the user. This part of the solution is working perfectly. 

So then I made a new table called Activity which my summary layout is based on. The only field in this table is a global field called "InRange" which is a calculation field set to always equal "Yes". I then made a relationship between this global InRange field and each of the InRange fields in the tables I want to display the modified records from. So theoretically, whenever the user selects a date range, all of the records that were modified in that date range become related to this global field, and show up in the portals on the Activity summary layout. But right now nothing is displayed in the portal, even though I have checked that the modified records do indeed have a value of "Yes" in their InRange field.

I figure it must have something to do with the relationship being based on a global variable, or the way the calculaion fields are stored. I tried creating a record in the Activity table, and making the InRange field not global (but still always equal to "Yes" to see if that was the problem, and that didn't work. I tried to make the InRange fields in each table into a stored calculation, but it said I could not because it made reference to a global field (the user defined date range). I figured all of the InRange fields in the tables needed to be calculation fields so that they would automatically update, and when I try making them into a text field with a calculation they do not update correctly as I suspected.

Can anyone see offhand where I am going wrong, or is there another approach I haven't thought of that might work better?