Forum Discussion

akikaplan's avatar
akikaplan
Copper Contributor
Feb 13, 2020
Solved

Solved: Mismatch in numbers using table row count

edit: I'm embarrassed, the issue was good old fashioned user error... Thanks to everyone who took a look!

I'm trying to get an accurate cell count using a table row, I'm seeing a discrepancy in the results and I'm not sure what I'm missing.

 

I have two columns, for in and out of spec items. When the value is in spec, the out of spec cell in the same row is autopopulated as NaN and vice-versa. When I use the table row to count the visible cells (=SUBTOTAL(103,[In Spec]) I get 405. But, when I filter the data to show only in spec values (de-select NaN for that column) and use the table row to count the cells (=SUBTOTAL(103,[In Spec]) or even count numbers without having de-selected NaN (=SUBTOTAL(102,[In Spec]), I get 136. When added to the value I get doing the same thing in the out of spec column (267) I get 403. Where am I missing these two cells?

 

This is an example for one day of data, which I reduced to after noticing the same issue looking at data for the month which gave me a discrepancy of 43 cells between adding the number count from in and out of spec columns and the table row count (Table row gave count as 6119 and the sum of numbers from in and out of spec gave 6076). Any ideas as to what's happening? Let me know if screenshots or additional details would be helpful. Thanks everyone!

6 Replies

  • PReagan's avatar
    PReagan
    Bronze Contributor

    Hello akikaplan,

     

    A sample file would certainly be helpful in determining the underlying issue. (Please remove any sensitive information)

    • akikaplan's avatar
      akikaplan
      Copper Contributor

      Hi PReagan, I've attached the relevant columns for the month I was talking about, which gives a difference of 43 between the cell count of either column and the sum of the number counts from the two columns. I'm going to be really embarrassed if it's something simple, but I've looked for anything in the data that would cause this and I can't readily find anything. Thanks for any help you can give!

       

      • akikaplan's avatar
        akikaplan
        Copper Contributor

        PReagan, I figured it out, and it is indeed something embarrassingly simple. I've got a few entries where NaNs populate both columns. It happens twice in the first month and I'm going to go ahead and guess 43 times overall... 

Resources