We have a scenario where we need to see the percentage for each type. The overall percentage is showing accurately, and there are no issues here. However, when we apply a filter for Type1, we only see the percentage for the defects listed in Type1. We actually expect to see the results as the percentage of Type1 defects in the overall audited count. Could you please provide review the test case and assist me? A sample test case has been created in Arena, and the link is provided below.
To clarify, when you filter your table to “Type 1” you want to see the percentage of orders that are in Type 1 compared to all audit count? So we should see 3 (count of audits in type 1) compared to 151 (count of all audits)?
yes, In the type 1 category, we observed 2 significant defects, so the percentage should be calculated as 2/151 = 1.32%. However, when we apply the filter for the Type 1 category, the percentage shows as 66.67%.
The calculation in the Arena link did not cause that error. When I run into this, I break up the large calculation in to its parts and throw it on a table visual. This will allow you to see which part is causing the error.
My guess is that this is happening because there are calculations at different levels. Can you share the calculations you made based on the Arena link?
Yes, after removing that, we can see the data in the table. However, I’m not sure how to fix this issue. Could you please assist or suggest an alternative way to get the expected output? Thanks!
I don’t understand, the calculated field is now returning values but they are incorrect? Did they anonymized data that you shared in your arena match the dataset that you are using this calculation on?
Yes, we do see the data in the table when we exclude the distinct count over function, but it is incorrect. The data shown in Arena matches the dataset we are using, but we have more columns than those shown in Arena. Thank you!
The first thing I would troubleshoot is the "currentqueue <> “Not Selected”. The function is case sensitive and so you will need to make sure it matches all potential field values.
