Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Major |
| Complexity | Unknown |
| Component | Visual Analytics |
| Version | 17.0 |
We currently have a COUNT function which returns the number of items in a group. NULL values are not counted.
We want a new function called COUNTD which returns the number of unique items in a group. NULL values are not counted.
|
|
46 KB
|
363 KB
|
|
27 KB
|
|
56 KB
Areas to test:
-- persistence
-- Default Properties > Aggregation
-- undo / redo
-- COUTND : the #s shown are correct
-- COUNTD: calculated field formula
-- backwards & forwards migration. To understand this better, look at bug fixes #5243 & #5153 which are included in this build.
Verified in ads build 17.0.3-2
When we apply countd function to a measure field and perform backward migration i.e v17 to v16,the field is displayed as valid field and blank chart is displayed,on right click on a measure field we can remove this field and can use the workbook.
On forward migration, it treats the measure field with COUNTD as invalid,on right click on invalid field we can remove this field and can use the workbook.
Verified in ads build 17.0.3-2
When we apply countd function to a measure field and perform backward migration i.e v17 to v16,the field is displayed as valid field and blank chart is displayed,on right click on a measure field we can remove this field and can use the workbook.
On forward migration, it treats the measure field with COUNTD as invalid,on right click on invalid field we can remove this field and can use the workbook.
Issue #14265 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build 17.0.3-2 |
| No time estimate |
Areas to test:
-- persistence
-- Default Properties > Aggregation
-- undo / redo
-- COUTND : the #s shown are correct
-- COUNTD: calculated field formula
-- backwards & forwards migration. To understand this better, look at bug fixes #5243 & #5153 which are included in this build.