I don't see how that chart can work from just the data in a single portal row. Seems like you need this data for all locations.
I would do the following:
Add a "count of" summary field to the portal's table.
I would use a layout based on the portal's table, not the parent table.
Set up the Summary field as your Wedge data series and the location field as your wedge label series.
Perform a find to find only the records needed for this chart.
Sort the records by location to group them so that you get just one wedge for each location.
Thanks!! I will give that a try today.
It worked just as you described. THANK YOU. To find the records I needed I had to do a little fancy footwork.
I wanted to find the latest location entry for each "car". (in the script the actual object is called a flatrack). I may have gone about this weird but I sorted the list of locations by Flatrack ID and Date Entered (decscending). Then the script goes to each record... if the following record has the same Flatrack ID as the previous one.. it's omitted.. till all i'm left with is a single entry for each flatrack with the most current location / date.
I've attached a picture of my script for anyone to tear apart and critique. :)