Relationship Based on a Blank Global

[wmugrad28]

What I wanted to do was to create a self join relationship where the field "End_Date" was related to "End_Date_g_filter". I wanted the global filter to be blank so that my portal would only show records with an empty end date. If the global filter has a value and the end date matches, those records show up in my portal; however; if the global filter is empty and there are records with NO end date (aka it's blank) the portal shows NO records.

Should I create a calcuation on the table that says if the field is empty = 1 otherwise = 0 and then set the global to 1? Is there a better way?

Greg

[wmugrad28]

What I wanted to do was to create a self join relationship where the field "End_Date" was related to "End_Date_g_filter". I wanted the global filter to be blank so that my portal would only show records with an empty end date. If the global filter has a value and the end date matches, those records show up in my portal; however; if the global filter is empty and there are records with NO end date (aka it's blank) the portal shows NO records.

Should I create a calcuation on the table that says if the field is empty = 1 otherwise = 0 and then set the global to 1? Is there a better way?

Greg

[wmugrad28]

What I wanted to do was to create a self join relationship where the field "End_Date" was related to "End_Date_g_filter". I wanted the global filter to be blank so that my portal would only show records with an empty end date. If the global filter has a value and the end date matches, those records show up in my portal; however; if the global filter is empty and there are records with NO end date (aka it's blank) the portal shows NO records.

Should I create a calcuation on the table that says if the field is empty = 1 otherwise = 0 and then set the global to 1? Is there a better way?

Greg

[wmugrad28]

I tried doing the calc thing and it worked, but I had to make the calcs stored. I would like them to be unstored so that when an end date is added then the portal changes. The problem is that if I make them unstored they don't show up at all in the portal. Ideas?

Greg

[wmugrad28]

I tried doing the calc thing and it worked, but I had to make the calcs stored. I would like them to be unstored so that when an end date is added then the portal changes. The problem is that if I make them unstored they don't show up at all in the portal. Ideas?

Greg

[wmugrad28]

I tried doing the calc thing and it worked, but I had to make the calcs stored. I would like them to be unstored so that when an end date is added then the portal changes. The problem is that if I make them unstored they don't show up at all in the portal. Ideas?

Greg

[wmugrad28]

Ok, so I'm posting my own questions and answers. I just figured it out. I changed the two calcs to text with auto entered calcs. This fixed it, but why? Are unstored calcs not relationship friendly?

Greg

[wmugrad28]

Ok, so I'm posting my own questions and answers. I just figured it out. I changed the two calcs to text with auto entered calcs. This fixed it, but why? Are unstored calcs not relationship friendly?

Greg

[wmugrad28]

Ok, so I'm posting my own questions and answers. I just figured it out. I changed the two calcs to text with auto entered calcs. This fixed it, but why? Are unstored calcs not relationship friendly?

Greg

[BobWeaver]

No, unstored calcs cannot be indexed, and relationships only work with indexed fields. You can have an unindexed field on the parent side of a relationship, but not on the other.

[BobWeaver]

No, unstored calcs cannot be indexed, and relationships only work with indexed fields. You can have an unindexed field on the parent side of a relationship, but not on the other.

[BobWeaver]

No, unstored calcs cannot be indexed, and relationships only work with indexed fields. You can have an unindexed field on the parent side of a relationship, but not on the other.

[wmugrad28]

Hi Bob,

What about auto entered calculations using the Lookup function and unchecking the "Do not replace existing value for field (if any)" box? I believe these are indexable. Are they indexable because they are stored, even though they allow updates by unchecking that box?

Greg