Chad,
There is a subtle difference between the results of a simple multi-value query and an aggregation (like @Sum). In the simple multi-value query, there is an "auto-filter" applied that strips deleted and dead assets. The same is not applied to aggregation. Therefore the discrepancy you noticed is most likely caused by deleted tasks.
The following should adjust for this API quirk:
rest-1.v1\Data\Story?sel=Children.ID,Children.Actuals.Value,Children:Task[AssetState!='Dead'].@Count,Children[AssetState!='Dead'].Actuals.Value.@Sum.Value&where=Number='B-02833'
Does that return what you expect?
Ian Buchanan
Product Manager for Platform and Integrations
On Wednesday, July 18, 2012 9:08:51 PM UTC-4, Chad Peterson wrote:
Given this query:
rest-1.v1\Data\Story?sel=Children.ID,Children.Actuals.Value,Children:Task.@Count,Children.Actuals.Value.@Sum.Value&where=Number='B-02833'
I received the following in response:
<Assets total="1" pageSize="2147483647" pageStart="0">
<Asset href="/IST/rest-1.v1/Data/Story/13195" id="Story:13195">
<Relation name="Children.ID">
<Asset href="/IST/rest-1.v1/Data/Task/34505" idref="Task:34505"/>
<Asset href="/IST/rest-1.v1/Data/Task/34506" idref="Task:34506"/>
<Asset href="/IST/rest-1.v1/Data/Task/34507" idref="Task:34507"/>
</Relation>
<Attribute name="Children.Actuals.Value.@Sum">97.2</Attribute>
<Attribute name="Children.Actuals.Value">
<Value>1</Value>
<Value>2</Value>
</Attribute>
<Attribute name="Children:Task.@Count">6</Attribute>
</Asset>
</Assets>
Can someone explain why the values returned total to 3, but the .@Sum shows 97.2.
I imagine this hasw something to do with the task count of 6, but I simply cannot find 6 tasks associated with this story. Via V1 web, it should 3. The listed IDs of all children seem to indicate only 3 items.
Where are the other 3? Once I find them, I'm assuming they'll have values that are being included by the @Sum calculation.
Thoughts?
-Chad