| Anonymous | Login | Signup for a new account | 2010-09-06 16:05 EDT |
| Main | My View | View Issues | Change Log | Roadmap | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | Edit | [ View Advanced ] [ Issue History ] [ Print ] | |||||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||||||
| 0891 | [InfoQube] Bug | average | always | 2010-02-13 23:13 | 2010-03-09 18:23 | ||||||||
| Reporter | Armando | View Status | public | ||||||||||
| Assigned To | |||||||||||||
| Priority | normal | Resolution | fixed | ||||||||||
| Status | resolved | Product Version | Latest build | ||||||||||
| Summary | 0891: Hierarchical/row Recalculation (shift F9) equals null when an item doesn't have any children | ||||||||||||
| Description |
see : http://www.sqlnotes.net/drupal5/index.php?q=node/1455 [^] This is fine in most cases, except when sub items are non existent or don't meet the hierarchical equation's conditions (i.e. : the user uses some conditions in the hierarc.equation to filter items out from the equation) . When sub items are non existent or don't meet the hierarchical equation condition, the result will always be null, and recalc will never always result as a null -- at least, that's what seems to happen here. Could this be changed so that when there are no items available to calculate the equation/function, row equations have priority ? |
||||||||||||
| Additional Information | |||||||||||||
| Tags | No tags attached. | ||||||||||||
| Attached Files | |||||||||||||
|
|
|||||||||||||
| There are no notes attached to this issue. |
| Mantis 1.1.1[^] Copyright © 2000 - 2008 Mantis Group |