[MGNLCTS-29] XLS integration: handling the numbers Created: 24/Sep/13 Updated: 30/Oct/13 Resolved: 25/Oct/13 |
|
| Status: | Closed |
| Project: | Content Translation Support |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.1.4 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Zdenek Skodik | Assignee: | Chunhua Liu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Date of First Response: | |||||
| Epic Link: | Support | ||||
| Sprint: | 4.5.13 | ||||
| Description |
|
Excel wraps any numeric values into a non-string cells by default. Importing such content fails then on the exception attached so one needs to encode all these cells with a single quote beforehand, in fact they become strings. Similarly if you have a property of just a numeric value that is a subject of export, Excel is not able to read it properly at the moment, unless it's converted to a string cell. The module can easily be more content editors friendly. Alternative XLS editors, like LibreOffice, used to be able to cope with it as they cast to string implicitly. |
| Comments |
| Comment by Chunhua Liu [ 25/Oct/13 ] |
|
Can't distinguish Date from Number from API, so date will be treated as number. |
| Comment by Chunhua Liu [ 25/Oct/13 ] |
|
Not sure if export is incorrect, seems everything will be exported as string which is correct, can't test because no Windows. |