• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 671
  • Last Modified:

FM - Portal in a Trailing Grand Summary of a Report?

As you can see from the "__LeadsPortal" attachment, I am trying to change the way we render total Leads and %Vacant by Property.  We now have count, calc and % Vacant fields for each of our 80 properties.  I tried doing this by a report, but my boss doesn't like it.  I am now trying to put a portal in the Trailing Grand Summary of the report in order to show totals by each prop.  However, as you can see, the portal just keeps repeating the last property listed in the body of the report.  Where did I go wrong?  Can you just not put a portal in the bottom of a report?

I created 3 relationships to try to pull this off:  1) Leads to itself by the Property field, 2) Vacancies to Leads by the Prop field, and 3) Tenants to Leads by the Prop field.  I use the latter two only to calculate the %Vacant field, which actually looks like it works.  Thanks for your help.
--LeadsPortal.JPG
--LeadPortal2.JPG
--LeadPortal3.JPG
0
rvfowler2
Asked:
rvfowler2
  • 4
  • 3
1 Solution
 
Will LovingPresidentCommented:
Usually when you see the same value repeated in a portal it's because the portal relationship and the relationship being used by the fields within the portal are different. You'll need to check the fields in the portal to see if they reference the same (or a related) relationship.

However, in this instance, the bigger issue may be the record the portal is relating FROM. If the relationship is from "Leads to itself by the property field" - and I'm assuming you used the "=" operator - then the portal should really only be displaying one record, that of the current property. If you want it to show all properties in the portal, then you would need a global field, a constant or some other way of relating all properties so they show up in the portal. Since you do have multiple records showing up in the portal, I'm not quite sure what's going on without seeing  the relationship being used by the portal.

If that's not it, you might try putting the portal in a Leading Grand Summary and see if it give you the first record.
0
 
rvfowler2Author Commented:
No, the relationships of the portal and the fields are the same, and yes, when I put the portal in a newly created Leading Grand Summary field, it did show reps of the first record.  The relationship used by the portal is simply a copy of the Leads db and then related PropCode field to PropCode field.
0
 
Will LovingPresidentCommented:
So the point is that the Leading Grand Summary deals with relationships from the first record in the found set and the Trailing Grand Summary works from the last record in the found set. This behavior is similar to what happens with sub-summaries in that any non-summary field values displayed in the Sub-Summary part will come from the first record in each summarized section of the report.

In the case of your portal, only the Property Value of the Last (or First) record is active as a key for the relationship. To show a portal with all Property Values, the Parent key for the portal needs to be something that all Properties have in common or simply be a Cartesian relationship. You could even have the portal start from somewhere else rather than using a self-join, perhaps an Interface or Admin table with a relationship to Properties.

My question is - does a portal really get you what you want? Wouldn't a list view, possibly with 2 or 3 columns so you could fit it on on page, be more useful?
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
rvfowler2Author Commented:
Problem is that my boss would like the data you see in the report with the totals you see that I'm trying to put in the portal at the bottom.  What I'm trying to do is eliminate the maintenance of 240 fields.  Wait... let me try putting the portal in a footer instead of the Trailing Grand Summary and see if that makes a difference.  Will let you know.
0
 
Will LovingPresidentCommented:
Do you have a separate table that JUST has the Property values in it - meaning one Property per record, so 240 properties? Could you build your report from their using relationships to the Vacancies and elsewhere as required? Then you wouldn't need to deal with summarizing multiple records using self-joins the Property value...
0
 
rvfowler2Author Commented:
Excellent idea.  Let me look into it.
0
 
rvfowler2Author Commented:
Will, initial fields work fine; good suggestion.  I am now working out how to get totals of a found set  (easy to do in the Body of the report), but am having problem in showing these totals at the bottom of a report.  Trying to use global filter fields.  Will try a couple of things and post it if it doesn't work.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now