Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0002772 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Openbravo ERP] 07. Sales management | minor | always | 2008-03-29 00:26 | 2008-07-08 11:53 | |||
| Reporter | cromero | View Status | public | |||||
| Assigned To | cromero | |||||||
| Priority | normal | Resolution | fixed | Fixed in Version | 2.40beta | |||
| Status | closed | Fix in branch | Fixed in SCM revision | |||||
| Projection | none | ETA | none | Target Version | ||||
| OS | Any | Database | Any | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Product Version | SCM revision | |||||||
| Merge Request Status | ||||||||
| Review Assigned To | ||||||||
| OBNetwork customer | No | |||||||
| Web browser | ||||||||
| Modules | Core | |||||||
| Support ticket | ||||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0002772: Use numbering vs string ordination in dimensional rpts | |||||||
| Description | In dimensional reports, if you use a string ordination in the ORDER BY clause the result can be: 1,10,11,2,3,4,5.... when you expect to be 1,2,3,4,5,..10,11 Well the solution is to use a TO_NUMBER(VALUE) in the ODER BY to use a numbering ordination instead of a string ordination | |||||||
| Tags | No tags attached. | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0003383) cromero (viewer) 2008-03-29 00:32 edited on: 2008-06-12 09:25 |
Logged In: YES user_id=1500614 Originator: YES This error causes that the grouping label was not correct in these reports: ReportInvoiceCustomerDimensionalAnalyses_data.xsql ReportInvoiceCustomerDimensionalAnalysesJR_data.xsql ReportInvoiceVendorDimensionalAnalysesJR_data.xsql ReportMaterialDimensionalAnalysesJR_data.xsql ReportPurchaseDimensionalAnalysesJR_data.xsql ReportRefundInvoiceCustomerDimensionalAnalyses_data.xsql ReportRefundSalesDimensionalAnalyses_data.xsql ReportSalesDimensionalAnalyze_data.xsql ReportSalesDimensionalAnalyzeJR_data.xsql ReportShipmentDimensionalAnalyzeJR_data.xsql |
|
(0003384) cromero (viewer) 2008-03-29 00:40 edited on: 2008-06-12 09:25 |
Logged In: YES user_id=1500614 Originator: YES Bug fixed in revision 3114 Luckily only the ReportInvoiceCustomerDimensionalAnalyses_data.xsql and the ReportInvoiceCustomerDimensionalAnalysesJR_data.xsql have more than 9 dimensions (in the other reports ordination was working "satisfactorily") |
|
(0003385) psarobe (viewer) 2008-06-09 13:49 edited on: 2008-06-12 09:25 |
Logged In: YES user_id=1500703 Originator: NO Can you give the steps to reproduce it? |
|
(0006361) user71 2005-06-01 00:00 edited on: 2008-06-12 09:43 |
This bug was originally reported in SourceForge bug tracker and then migrated to Mantis. You can see the original bug report in: https://sourceforge.net/support/tracker.php?aid=1928341 [^] |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2008-07-08 11:53 | plujan | Status | resolved => closed |
| 2008-07-08 11:53 | plujan | Fixed in Version | 2.40alpha-r2 => 2.40beta |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |