Databases
StackOverflow2013
Postsdbo
POLINQ Error Invalid Column Name on Group by sum
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POLINQ Error Invalid Column Name on Group by sum
    primarykey
    data
    text
    <p>For some reason, when using two sums on a group by, i run into the error "invalid column name 'id'. When i only do one sum, it works as expected.</p> <p>The following <strong>fails</strong> and throws the error:</p> <pre><code>from pd in PrDetails.Where(_pd =&gt; _pd.PrId == 46) group pd by new { pd.ProgramFund, pd.ProjectDetail.CostCenter, pd.ProjectDetail.Wbs } into g select new { g.Key.ProgramFund, g.Key.CostCenter, g.Key.Wbs, CommittedTotal = g.Sum(_pd =&gt; _pd.PrDetailPrAmounts.Sum(_pa =&gt; _pa.CommittedAmount)), OverheadTotal = g.Sum(_pd =&gt; _pd.PrDetailPrAmounts.Sum(_pa =&gt; _pa.OverheadAmount)) } </code></pre> <p>However, the following <strong>does</strong> work fine:</p> <pre><code>from pd in PrDetails.Where(_pd =&gt; _pd.PrId == 46) group pd by new { pd.ProgramFund, pd.ProjectDetail.CostCenter, pd.ProjectDetail.Wbs } into g select new { g.Key.ProgramFund, g.Key.CostCenter, g.Key.Wbs, CommittedTotal = g.Sum(_pd =&gt; _pd.PrDetailPrAmounts.Sum(_pa =&gt; _pa.CommittedAmount)) } </code></pre> <p><strong>And also</strong>, when I get the overhead total, instead of the committed total, it works great:</p> <pre><code>from pd in PrDetails.Where(_pd =&gt; _pd.PrId == 46) group pd by new { pd.ProgramFund, pd.ProjectDetail.CostCenter, pd.ProjectDetail.Wbs } into g select new { g.Key.ProgramFund, g.Key.CostCenter, g.Key.Wbs, OverheadTotal = g.Sum(_pd =&gt; _pd.PrDetailPrAmounts.Sum(_pa =&gt; _pa.OverheadAmount)) } </code></pre> <p>Why can't i get the committed total and overhead total at the same time?</p> <p>I have our basic table structure below:</p> <h2>PrDetails</h2> <p>Id (int)<br> PrId (int)<br> ProgramFund (linq class)<br> ProjectDetail (linq class) </p> <h2>ProjectDetails</h2> <p>Id (int)<br> CostCenter (linq class)<br> Wbs (linq class) </p> <h2>PrAmounts</h2> <p>Id (int)<br> PrDetailId (int)<br> CommittedAmount (decimal)<br> OverheadAmount (decimal)</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. UStaco
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POLINQ Error Invalid Column Name on Group by sum
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POLINQ Error Invalid Column Name on Group by sum
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POLINQ Error Invalid Column Name on Group by sum
      1. USMike Fielden
      1. VTFavorite
    1. COdo you have any associations/relationships set up for any of the tables?
      singulars
      1. POLINQ Error Invalid Column Name on Group by sum
      1. USAndrew Theken
    2. COYea, all the relationships exist. If the relationships weren't there, the last two LINQ queries would not have been able to run successfully.
      singulars
      1. POLINQ Error Invalid Column Name on Group by sum
      1. UStaco
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload