Openbravo Issue Tracking System - Openbravo ERP | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0018889 | Openbravo ERP | A. Platform | public | 2011-10-26 19:56 | 2022-02-01 08:09 |
Reporter | mtaal | ||||
Assigned To | Triage Platform Base | ||||
Priority | normal | Severity | major | Reproducibility | have not tried |
Status | new | Resolution | out of date | ||
Platform | OS | 5 | OS Version | ||
Product Version | |||||
Target Version | Fixed in Version | ||||
Merge Request Status | |||||
Review Assigned To | |||||
OBNetwork customer | |||||
Web browser | |||||
Modules | Core | ||||
Support ticket | |||||
Regression level | |||||
Regression date | |||||
Regression introduced in release | |||||
Regression introduced by commit | |||||
Triggers an Emergency Pack | No | ||||
Summary | 0018889: Add an excel mode to the XML webservices | ||||
Description | The xml webservices can be used as a datasource in Excel, the xml should be simplified however, an example of a sales order xml: <SalesOrder> <County>Holland</Country> <Amount>5</Amount> </SalesOrder> <SalesOrder> <County>Holland</Country> <Amount>10</Amount> </SalesOrder> In addition: - what is the number format expected by excel (decimal dot without grouping probably). >>> no grouping definitely. The "decimal separator" should be a user-specific thing--if not possible in the short term, it should at least be set as a client-wide preference? (comma vs. period). If not possible I would go for period, and then see if the people needing comma can override with Excel formatting. Thousands separator is not needed (just Excel column formatting) - what is the date time format expected >>> I think if you go for yyyy-mm-dd that is fine (can then change via Excel column formatting) - does it make sense to also output the database id (technical but unique)? >>> for the user, I think a practical alternative would be to take it a step further and provide the actual link, so the user can click on it and drill back into the application, for example ale beer. The syntax in Excel is =HYPERLINK("http://live.builds.openbravo.com/int-full-pgsql/?tabId=180&recordId=8A64B71A2B0B2946012B0BC4345000FB", [^] "Ale Beer"). For simplicity for now, I would just add a generic column called Link, and also put the string "Link" as the second parm in the hyperlink function. That way, no extra setup required to determine which field in an entity should be clickable. I would actually put "Link" as the first column in the result set, since I think it is great for demos--you can really only "drill back" like this with a web-based system and many users will be amazed. If I had this capability, I would demo it every week in the live demo! Though it is very simple, it is practical and useful for end users, and shows how the web can be easily integrated to desktop apps like Excel. | ||||
Steps To Reproduce | . | ||||
Proposed Solution | |||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2011-10-26 19:56 | mtaal | New Issue | |||
2011-10-26 19:56 | mtaal | Assigned To | => mtaal | ||
2011-10-26 19:56 | mtaal | Modules | => Core | ||
2011-10-27 20:35 | hgbot | Checkin | |||
2011-10-27 20:35 | hgbot | Note Added: 0042179 | |||
2011-10-27 20:35 | hgbot | Status | new => resolved | ||
2011-10-27 20:35 | hgbot | Resolution | open => fixed | ||
2011-10-27 20:35 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/devel/pi/rev/bbf8582fbc5d8304c5dea6f2378c22ddfb5f2244 [^] | ||
2011-10-27 20:35 | hgbot | Checkin | |||
2011-10-27 20:35 | hgbot | Note Added: 0042181 | |||
2011-10-27 20:35 | hgbot | Fixed in SCM revision | http://code.openbravo.com/erp/devel/pi/rev/bbf8582fbc5d8304c5dea6f2378c22ddfb5f2244 [^] => http://code.openbravo.com/erp/devel/pi/rev/490e626bad9801d19cfacc2af82f31ccdedecdca [^] | ||
2011-11-02 10:29 | mtaal | Note Added: 0042434 | |||
2011-11-02 10:29 | mtaal | Status | resolved => new | ||
2011-11-02 10:29 | mtaal | Resolution | fixed => open | ||
2011-11-02 10:29 | mtaal | Target Version | 3.0MP5 => 3.0MP6 | ||
2011-11-04 13:57 | hudsonbot | Checkin | |||
2011-11-04 13:57 | hudsonbot | Note Added: 0042587 | |||
2011-11-04 13:57 | hudsonbot | Checkin | |||
2011-11-04 13:57 | hudsonbot | Note Added: 0042589 | |||
2011-11-15 10:25 | iperdomo | Target Version | 3.0MP6 => | ||
2016-10-21 11:02 | mtaal | Status | new => closed | ||
2016-10-21 11:02 | mtaal | Resolution | open => out of date | ||
2016-10-21 13:17 | mtaal | Tag Attached: MT_closed_out_of_date | |||
2016-10-21 14:08 | mtaal | Assigned To | mtaal => platform | ||
2016-10-21 14:09 | mtaal | Status | closed => new | ||
2016-10-21 14:10 | mtaal | Tag Detached: MT_closed_out_of_date | |||
2022-02-01 08:09 | alostale | Assigned To | platform => Triage Platform Base |
Notes | |||||
|
|||||
|
|
||||
|
|||||
|
|
||||
|
|||||
|
|
||||
|
|||||
|
|
||||
|
|||||
|
|