Column values truncating when exported to excel from OBIEE dashboard

Hi,
I am fairly new to OBIEE. recently I am facing an issue, when I try to export a report using the download to Excel or download to excel2000 option, one of the 18 digit column value is truncated to exponential value. Like for example the column is ESN with 18 digit numbers like 268235457500823991. But when I export it I get only 268235457500823000 or 2.68235E+17. Please help what could have been the issue.....
Thanks in advance!

Convert it to text before you export it.
regards
John
http://obiee101.blogspot.com

Similar Messages

How to remove values formatting in export to excel from ALV grid

Hi all,
I have small issue, I have ALV Grid with some data, but the problem is with columns containing e.g. gross amounts, because it is displayed in the grid as e.g. 1.764,81, and after export to excel it is still in this format (with dot and comma), so excel doesn't treat it as numeric value but as text, and then when I try to calculate total on the column then this values are not taken to the total. Do you know if that is possible to remove column formatting?
kind regards,
Marcin

I replied too soon to Peter's suggestions. For some reason, I was able to add new info. to my first new row, but not the second. However, I finally figured out the problem.
I found the Help Center page on: "Here are ways to change custom formats and apply changes to table cells:"
To change the elements associated with a custom format that’s been applied to cells, select the cells and click Show Format in the Format pane of the Table inspector.
I saw that the "cell format" was listed as "automatic," so I changed it to "Custom;" then left the new custom window at it's default settings. Now my cells would accept pasted info. without spreading it through the lower rows. Whatever automatic was in the table, it was not what I wanted. Doing this to other new cells, solved my problem. Thanks again.

Error: Invalid Export dll when exporting to Excel from VB,NET 2008

Version: Crystal Report 2008
Front End: Visual Basic 2008
Hello,
I am trying to export a report to Microsoft Excel [2003] when I get the error "Error in File_Temp......Invalid Export dll or export format".
from the Windows Form Viewer.
I have looked in C:\Program Files\Common Files\Business Objects\3.0\bin and found crxf_xls.dll and crxf_xls_res_en.dll, but am not sure if these dlls' are the error source.
Do these dll files need to be reregistered? Re-installation hasn't worked.
Thanks
eburton

Duplicate

Character drops zeros when exported to Excel

I have a template that when exported to Excel from E-Business Suite, drops the leading zeros. We want those zeros to be there.
For example, Project Number 000400 is SEGMENT1 of PA_PROJECTS_ALL so when viewed in Word, it shows the full text string. When the user exports to Excel, it drops the three leading zeros and just displays 400.
Is there a way around this?
Thanks,
Rob

Use a special character called a non-breaking-space and that should resolve your issue. Put it before or after your xml field
Insert->Symbol->Special Characters Tab->Nonbreaking Space
or
Ctrl+Shift+SpaceIf this works, don't forget to give me some points. :-)
Ike Wiggins
http://bipublisher.blogspot.com

Missing report header when exporting to Excel

When exporting to Excel from an ASP.NET application (Visual Studio 2003), some reports do not include the report header section. The reports headers are there when exporting to PDF.
I cannot see any obvious difference between the reports that export the report header and those that do not. I believe that I have the latest service pack.

I am using Microsoft Development Environment 2003 Version 7.1.6030. The About Box only says Crystal Reports for Visual Studio .NET. It does not show a version number.
I have not been able to find any information regarding ExportHeaderAndFooter or even ExportHeader. They do not appear to be options in this version of Crystal.
I have tried reducing the report header to a simple text object that works OK on another report but it will still not export on this one. The report footer does export OK though.

Column values shift towards left for null values when export to excel

Post Author: pssuresh
CA Forum: Exporting
All,
I have a strange problem when using crystal report 10 export through C# Code. Consider in a row there are 3 columns and i am exporting to excel. ex.Student_id,Student_name,Student_Section. If Student_name values are null, then student_section values get displayed under student_name. There is a column shift towards left when there are null values. If anybody has already faced this problem, please post ur answer.
Note: When i just export to excel directly from crystal report, it works fine. i face problem only when i export through .Net code. I guess it is the problem with some formatting through code. if any body has fix, let me know.
Thanks,
Suresh.P.S

Post Author: pssuresh
CA Forum: Exporting
Thanks for your reply. Even i have done the same thing yesterday to solve that problem. But we have nearly 100 of reports and started migrating now. The best solution crystal reports suggest is this.
http://support.businessobjects.com/library/kbase/articles/c2014430.asp
Thanks,
Suresh.P.S

Megge column when export to excel

User is requesting Excel column header to split for infoobjects that are displaying key & text. See attachment showing the column header splitting.
(Currently all key & text headers merge when exported into Excel apart from last object in row.

Hi,
this is not posibble. You can switch on the parameter REPEATED_TEXTS_DISPLAYED at the Analysis Item, but this only repeats the characteristic values, not the headers.
The export to Excel shows the same as you see in the Analysis Item in Web.
best regards
ARNE

Lost collapsing columns when export to excel

I have created a report with row grouping, works correctly working in Report Server Browser,
after export the report to excel, when clicking on the + in Excel only 1 or 2 of about 100 lines appears, or there is no + head to click for other groups
a similar report works when exported to excel.
any solution what to do or whats possibly wrong?
thank you

Hi Karl,
According to your description that you are experiencing the issue when you export the report to excel, drill down report not display all the fields after expand the "+"and some group which should have "+" not shown, right?
I have tested on my local environment and can’t reproduce the issue, the issue can be caused by the incorrect setting of the visibility and also can be related to the excel rendering.
Microsoft Excel has limitations with how it manages hidden and displayed report items when they are exported. Groups, rows, and columns that contain report items that can be toggled are rendered as Excel outlines. Excel creates outlines that expand and collapse
rows and columns across the entire row or column which can cause the collapse of report items that are not intended to be collapsed. In addition, Excel's outlining symbols can become cluttered with overlapping outlines. To address these issues, the following
outlining rules are applied when using the Excel rendering extension:
The report item in the top-left corner that can be toggled can continue to be toggled in Excel. Report items that can be toggled and share vertical or horizontal space with the report item that can be toggled in the top-left corner cannot be toggled in
Excel.
To determine whether a data region will be collapsible by rows or columns, the position of the report item that controls the toggling and the position of the report item that is toggled are determined. If the item controlling the toggling appears before
the item to be toggled, the item is collapsible by rows. Otherwise, the item is collapsible by columns. If the item controlling the toggling appears beside and above the area to be toggled equally, the item is rendered with row collapsible by rows.
To determine where the subtotals are placed in the rendered report, the rendering extension examines the first instance of a dynamic member. If a peer static member appears immediately above it, the dynamic member is assumed to be the subtotals. Outlines
are set to indicate that this is summary data. If there are no static siblings of a dynamic member, the first instance of the instance is the subtotal.
Due to an Excel limitation, outlines can be nested up to 7 levels only.
Article about the show and hide in the excel for your reference:
http://msdn.microsoft.com/en-us/library/dd255234.aspx
Thanks for your understanding.
Regards
Vicky Liu

Merge columns when exporting to excel data only

Hi,
I have a report with headers in fowling format.
Quantity |
first day | last day |
When exporting to excel data only I want output in following format and want to merge upper header cells.
Quantity
First Day
Last Day
Please reply.Thanks.

Hi,
You can achieve this requirement Please follow the below document.
How to WYSIWYG SAP Crystal Reports Export to XLS
I hope this is the best formatting example suited for this requirement.
Ludek thanks for preparing this document and sharing with us......This is the best formatting ex.
Refer Link: Crystal Reports Crystal to Excel
Thanks,
DJ

Formatting lost when exported to excel

When I export a worksheet results to excel the formatting is being lost like in my worksheet I wanted a line and space for every grouped item which is lost in excel sheet. Is there a way get around for this ?
Thanks

Not exactly sure what formatting you're having a problem with, but I'll list some of the points I can think of, of exporting to Excel and will hopefully cover it. I believe you may be referring to point 1 below, but just in case ...
1. If you have group sort on for a column or more, then when exported to Excel, you won't have those 'blank' values for the column(s) that's grouped. That's why when you know someone will be exporting to Excel, it's a pain as all group sorts are usually taken back off (which can screw up exactly what you're trying to point out in the workbook).
2. If you have a page -> item (ie: lots of values you pull down like a LOV), then I believe, that you won't get an Excel worksheet for each value in the LOV but only for the one currently displayed when you performed the File -> Export.
3. When you export to Excel, you only get actual values, no functions of how it was calculated (ie: it'll be static, not dynamic).
4. You can export to Excel using Plus and might not get the formatting characteristics you want in Excel. I've seen users specifically bring up Viewer just to get the formatting characteristics (colors, fonts, etc.) when they export from that Disco version.
5. Sometimes when you export from Disco to Excel, that actual value that gets posted in Excel is different. I know ... it sounds wierd, but it's a fact. The problem is NOT Disco, but is a problem with Windows and a setting has to be altered (although I'd have to hunt what that setting is now though). However, I've only seen this happen a few times, so definitely not the norm.
Russ

Any method to Import & Export to Excel from Client Side

Hi,
Is there any method to Import and Export to Excel from the Client side. I have one procedure to export to Excel , but the excel file will be opened in the Application Server only, even if it executed from the client side. Also this procedure will not work if OLE2 chnaged CLIENT_OLE2. I am writing my procedure, Is there any idea to get it in the client side.
PROCEDURE pr_Forms_to_Excel(p_block_name IN VARCHAR2 DEFAULT NAME_IN('system.current_block')) IS
-- Declare the OLE objects
application OLE2.OBJ_TYPE;
workbooks OLE2.OBJ_TYPE;
workbook OLE2.OBJ_TYPE;
worksheets OLE2.OBJ_TYPE;
worksheet OLE2.OBJ_TYPE;
cell OLE2.OBJ_TYPE;
range OLE2.OBJ_TYPE;
range_col OLE2.OBJ_TYPE;
-- Declare handles to OLE argument lists
args OLE2.LIST_TYPE;
-- Declare form and block items
form_name VARCHAR2(100);
f_block VARCHAR2(100);
l_block VARCHAR2(100);
f_item VARCHAR2(100);
l_item VARCHAR2(100);
cur_block VARCHAR2(100) := NAME_IN('system.current_block');
cur_item VARCHAR2(100) := NAME_IN('system.current_item');
cur_record VARCHAR2(100) := NAME_IN('system.cursor_record');
item_name VARCHAR2(100);
baslik VARCHAR2(100);
row_n NUMBER;
col_n NUMBER;
filename VARCHAR2(100);
ExcelFontId OLE2.list_type;
BEGIN
-- Start Excel
application:=OLE2.CREATE_OBJ('Excel.Application');
OLE2.SET_PROPERTY(application, 'Visible', 'True');
-- Return object handle to the Workbooks collection
workbooks:=OLE2.GET_OBJ_PROPERTY(application, 'Workbooks');
-- Add a new Workbook object to the Workbooks collection
workbook:=OLE2.GET_OBJ_PROPERTY(workbooks,'Add');
-- Return object handle to the Worksheets collection for the Workbook
worksheets:=OLE2.GET_OBJ_PROPERTY(workbook, 'Worksheets');
-- Get the first Worksheet in the Worksheets collection
-- worksheet:=OLE2.GET_OBJ_PROPERTY(worksheets,'Add');
args:=OLE2.CREATE_ARGLIST;
OLE2.ADD_ARG(args, 1);
worksheet:=OLE2.GET_OBJ_PROPERTY(worksheets,'Item',args);
OLE2.DESTROY_ARGLIST(args);
-- Return object handle to cell A1 on the new Worksheet
go_block(p_block_name);
baslik := get_block_property(p_block_name,FIRST_ITEM);
f_item := p_block_name||'.'||get_block_property(p_block_name,FIRST_ITEM);
l_item := p_block_name||'.'||get_block_property(p_block_name,LAST_ITEM);
first_record;
LOOP
item_name := f_item;
row_n := NAME_IN('SYSTEM.CURSOR_RECORD');
col_n := 1;
LOOP
IF get_item_property(item_name,ITEM_TYPE)<>'BUTTON' AND
get_item_property(item_name,VISIBLE)='TRUE'
THEN
-- Set first row with the item names
IF row_n=1 THEN
------updated by faisal-to give Bold font-----
--FOR k IN 1 .. 3 LOOP
     args := OLE2.create_arglist;
     OLE2.add_arg(args, 1);
     OLE2.add_arg(args, col_n);
     cell := OLE2.get_obj_property(worksheet, 'Cells', args);
     OLE2.destroy_arglist(args);
     --cell_value := OLE2.get_char_property(cell, 'Value');
     ExcelFontId := OLE2.get_obj_property(Cell, 'Font');
     OLE2.set_property(ExcelFontId, 'Bold', 'True');
--END LOOP;
baslik:=NVL(get_item_property(item_name,PROMPT_TEXT),baslik);
args:=OLE2.CREATE_ARGLIST;
OLE2.ADD_ARG(args, row_n);
OLE2.ADD_ARG(args, col_n);
cell:=OLE2.GET_OBJ_PROPERTY(worksheet, 'Cells', args);
OLE2.DESTROY_ARGLIST(args);
OLE2.SET_PROPERTY(cell, 'Value', baslik);
OLE2.RELEASE_OBJ(cell);
END IF;
-- Set other rows with the item values
args:=OLE2.CREATE_ARGLIST;
OLE2.ADD_ARG(args, row_n+1);
OLE2.ADD_ARG(args, col_n);
cell:=OLE2.GET_OBJ_PROPERTY(worksheet, 'Cells', args);
OLE2.DESTROY_ARGLIST(args);
IF get_item_property(item_name,DATATYPE)<>'NUMBER' THEN
OLE2.SET_PROPERTY(cell, 'NumberFormat', '@');
END IF;
OLE2.SET_PROPERTY(cell, 'Value', name_in(item_name));
OLE2.RELEASE_OBJ(cell);
END IF;
IF item_name = l_item THEN
exit;
END IF;
baslik := get_item_property(item_name,NEXTITEM);
item_name := p_block_name||'.'||get_item_property(item_name,NEXTITEM);
col_n := col_n + 1;
END LOOP;
EXIT WHEN NAME_IN('system.last_record') = 'TRUE';
NEXT_RECORD;
END LOOP;
-- Autofit columns
range := OLE2.GET_OBJ_PROPERTY( worksheet,'UsedRange');
range_col := OLE2.GET_OBJ_PROPERTY( range,'Columns');
OLE2.INVOKE( range_col,'AutoFit' );
OLE2.RELEASE_OBJ( range );
OLE2.RELEASE_OBJ( range_col );
-- Get filename and path
args := OLE2.CREATE_ARGLIST;
OLE2.ADD_ARG( args, p_block_name );
OLE2.ADD_ARG( args,'Excel Workbooks (*.xls, *.xls');
filename := OLE2.INVOKE_CHAR( application,'GetSaveAsFilename',args );
OLE2.DESTROY_ARGLIST( args );
-- Save as worksheet
IF NVL(filename,'0')<>'0' THEN
args := OLE2.CREATE_ARGLIST;
OLE2.ADD_ARG( args,filename );
OLE2.INVOKE( worksheet,'SaveAs',args );
OLE2.DESTROY_ARGLIST( args );
END IF;
-- Close workbook
--OLE2.INVOKE( workbook ,'Close');
-- Release the OLE objects
OLE2.RELEASE_OBJ(worksheet);
OLE2.RELEASE_OBJ(worksheets);
OLE2.RELEASE_OBJ(workbook);
OLE2.RELEASE_OBJ(workbooks);
--OLE2.INVOKE(application, 'Quit');
OLE2.RELEASE_OBJ(application);
-- Focus to the original location
go_block(cur_block);
go_record(cur_record);
go_item(cur_block||'.'||cur_item);
END;
Thanks in advance.
Rizly Faisal

Alternatively you could use OLE2 to do the bulk of the importing and exporting and then use the webutil file transfer functions to move the file to the client and then simply open the file there...That might be more efficient in terms of performance as well.
Regards
Grant

Header of ALV with space when exported to excel using Standard ALV

Hi,
I am Using Reuse alv grid display    to dispaly my report and it works fine and I am using the standard SAP application tool to export it to excel.
But for some of the header fields I am getting space in the excel sheet but there is no space while displaying through ALV.
I am using the following field catalog for the same.
wa_fieldcat-col_pos = 10.
wa_fieldcat-fieldname = 'SOLLWERT'.
wa_fieldcat-seltext_l = 'text-t10'.      "Target value (* this has no space here)
wa_fieldcat-outputlen = 32.
wa_fieldcat-colwidth_optimize = 'X'.
APPEND wa_fieldcat to it_fieldcat.
but there are still space for this Colomn when exported to excel if after optimizing the column.
kindly suggest what field needs to be passed to the field catalogoe to avoid spaces in excel for the header.
Thanks
Ritesh

hey all,
Thanks everyone for the reply.
I am using the foloowing field cat:
l_col_pos = l_col_pos + 1.
    wa_fieldcat-col_pos = l_col_pos.
    wa_fieldcat-outputlen = 32.
     wa_fieldcat-fieldname = 'SOLLWERT'.
     wa_fieldcat-inttype   = 'P'.
*    wa_fieldcat-tabname = 'i_final'.
    wa_fieldcat-seltext_l = text-t11.         "Target Value
    APPEND wa_fieldcat TO i_fieldcat.
    CLEAR wa_fieldcat.
I have use this also in the field cat but stil i get space in the excel header.
wa_fieldcat-REF_FIELDNAME = 'SOLLWERT'.
*    wa_fieldcat-REF_TABNAME = 'QAMV'.
Also the space comes with the descrip[tion in the cell of excel.
its like [space Target Value] and i dont need this Space.
I have also used wa_layout-colwidth_optimize = 'X'. but it doesnt wrk.
Please suggest

Error when exporting to Excel for SharePoint 2010 List

We have few users who are getting the following error message when they try to export to Excel from the SharePoint list:
"An operation that uses the database driver could not be completed. If the driver is a Microsoft driver, make sure the driver file isn’t damaged, and if it is, reinstall the driver by reinstalling Microsoft Query. For other drivers, contact
your database administrator or driver vendor.‘
The export option works for me on my machine and also tested it out on other users' machines without issues. The list is currently holds 29763 items.
1. Created a view that filter the list to show few items, and the user was able to export without issues.
2. Followed the steps in the following Blog:
http://www.sharepointserverrecovery.com/blog/troubleshooting-problems-when-exporting-sharepoint-list-data-to-excel-spreadsheet-and-fixing-database-corruption/ and the user was able to export the original list.
3. My colleagues and I don't have any issues exporting to Excel. (Note: even my test account, that does not have any special permissions or members of any SharePoint group(s)).
4. Some Blog/Forums suggest to increase Threshold limit in Central Admin, which we don't want to do, since the issue only affect certain users.
Any idea on how to troubleshoot/resolve the issue?
Thanks,
Yassar

Do they have to export all the information or is a subset of it ok?
Creating an index on the columns that your users interact with the most and then creating views that limit the returned results will be useful. This will then allow an export.

Prblm in Date format when exported to excel

Hi ,
I had a problem when using the Export To Excel option from Portal. The data is getting fine populated in Excel but it's in General No Specific Format. But I wanted the data to be in its original format even when exported to Excel. Like...
Country -
Date Goods Delivered
India----
01.01.2001
America----
05.12.2004
Singapore----
12.04.2003
Here the country should be of type TEXT FORMAT and Date Goods Delivered should be in DATE FORMAT(Here its visible as date but it's in General format)
I am facing problem with date, it is displayed(01.04.2006) as shown above but it's in general format. I wanted it to be in date format at excel.
I am in BW3.5 with portal version EP7.0
Please suggest the solution and I had even gone through previous forum questions related to this but couldn't get.....the solution.
points will be assigned...
Regards,
rudra.

Hi,
My end users requirement is to get all data in Standard format. We can't ask to select the date column and change the format in excel as there are more date fields(columns ).
Using macro i had one problem,even though i am not sure..
i can't enable the macro to get enabled in page load of export to excel as it is to be done at users end...
If theres any possibilty of enabling....pls let me know
Thanks for your valuable suggestions...
Regards,
rudra.

SSRS XML Errors when exporting to .xlsx from Dynamics NAV Database

We use Dynamics NAV for our ERP and have many SSRS reports. We get xml Errors when exporting to Excel .xlsx. I've seen this happen since SQL 2008 R2 and have posted in many places trying to find an answer, but was hoping MS would solve the
issue. The numeric data types in the Dynamics NAV database are all decimal(38,20) and when the value is zero the Excel renderer throws the errors.
We now have over 400 reports and we export them to Excel 2003 format. I'm starting to feel like this is my new Y2K issue when Excel 2003 is set to sunset. I'm fearing that I'll have to do conversions on all numeric data types for all reports.
Both of these are Microsoft products so I'm wondering is this even on their radar.
We're running SQL Server 2012 SP2, and just rolled out CRM 2015 on SQL Server 2014. I get the errors in SSRS 2008R2, 2012, and 2014. Has anyone seen this before?
Timothy Kruse

Hi Skywalker73,
According to your description, when you export the report to Excel, the error “Excel was able to open the file by repairing or removing the unreadable content.” throws out when opening the Excel file.
Based on my research, it has reported the same issue when exporting to Excel. The issue could cause by numeric columns has a precision of 16 or higher. To fix the issue, we could change data type in the table to a support lower precision, or convert
the numbers in the stored procedure that populates the report. For more information, please refer to this article:
SSRS 2012 Bug – “Excel found unreadable content”. Besides, please refer to this
article to check if non-printing characters exist in the report.
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu
Qiuyun Yu
TechNet Community Support

Column values truncating when exported to excel from OBIEE dashboard

Similar Messages

Maybe you are looking for