Tagged: qExcelviewer
- This topic has 6 replies, 3 voices, and was last updated 8 years, 8 months ago by Deepak Tyagi.
- AuthorPosts
-
- 12/18/2014 at 3:39 am #7469
AnonymousParticipantHi,
n
Sorry, this is a bug for qExcelViewer web part, I have log it into TFS track the status, the TFS number is #420983.
n
To be a workaround, you can use the PDF export format in qListView. That can avoid this issue. Thank you.
n
–
- 01/22/2016 at 9:20 am #7226
AnonymousParticipantHi ,
n
The same issue occurs in the Excel Export function for qListview and qSIListview web parts. When the column contains leading zeros – for example, 012345.9999, they are treated as number instead of text, so the leading zero is dropped (i.e. 012345.9999 becomes 12345.9999).
n
Please kindly advise if there is a workaround for this issue?
n
Thanks again!
n
n
n
- 01/24/2016 at 1:43 am #7227
AnonymousParticipantHi ,
n
n
The export to excel logical in qListView and qSIListView is the same with qExcelViewer. This is the same bug there. I have updated the #420983.
n
n
As an workaround, please use export to PDF function.
n
n
n
- 01/25/2016 at 5:36 am #4593
AnonymousParticipantHello,
We are using QuickApps v.6.3. In my original list, the Client No. column is defined as a text column. However, this field was converted to number in qExcelViewer, so all the leading zero’s are mssing – for example, 09988 became 9988, etc. Could I change the display format of this column so that the leading zero can be preserved in Excel Viewer? I didn’t see a way to create a custom column there, unfortunately.
Please advise.
Thank you!
- 01/25/2016 at 5:36 am #7229
AnonymousParticipantOK – thanks!
- 04/16/2016 at 12:19 am #10302
Laurinda ChiParticipantHi there,
Just curious – has this issue been resolved in v.6.6? The TFS number is #420983.
This is regarding Export to Excel function (stripping leading zeros), which occurs whether we use qExcelviewer or the Actions > Export function.
Please kindly advise on the eta?
Thank you!
Laurinda Chi
- 04/21/2016 at 5:30 am #10307
Deepak TyagiModeratorHello Laurinda,
This issue has not been taken up in 6.6 version .we will resolve this issue in further releases and we will update you accordingly.
Thank you!
Deepak
-
- AuthorPosts
You must be logged in to reply to this topic.