nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle AI and Analytics

Child Item

OAS - Oracle DV - Export to excel

Sabrina Garcia

Organization Name (Required - If you are an Oracle Partner, please provide the organization you are logging the idea on behalf of):

TSE - Tribunal Superior Eleitoral

Description (Required):

We need the export functionality for excel to faithfully portray the format used in a dynamic table.

Use Case and Business Need (Required):

Oracle DV does not yet have the functionality of exporting the data in excel format, only CSV. When we use a dynamic table and put a year attribute in the column, it becomes in the row when exported to CSV. We need the export functionality for excel to faithfully portray the format used in a dynamic table.

Enhancement Request / Service Request:

Find more posts tagged with

Delivered

Analysis and Data Visualization

Status: Delivered

Comments

BJ Young

There are too many additional clicks to convert CSV into XLS. Standard Users don't know how to convert CSV into XLS and this is aff

Workspace Listing of customers with SDID.docx

ects our user adoption.

The limited functionality to only download to CSV affects our user adoption. This change will make the software more user-friendly as they can immediately start with their data analysis instead of converting and preparing the data.

More detail: As a Utility Provider, we have several instances where we have fields that are larger than 17 digits. For example, we have a customer identification number that is larger than 17 digits and we need the ability to download the raw data and not have it get transferred to a scientific formula field (that re-formats the field into the incorrect digit with a lengthy work-around to get the data re-transferred to the correct data). This is a known Microsoft issue. - when downloading to CSV file with columns that have digits over 17 digits. Downloading directly to XLS should resolve this issue.

AEP Customers who are in a deregulated state such as Texas are assigned an ESID/SDID. Service Delivery Identifier which identifies the customer with the Retail Electric Service Provider in place of AEP's billing account number.

SDIDs are 17 digits long. When exporting a list of customers with their SDID, the 17 digits are not exported accurately. Formatting the SDID cell to "Number" will display 17 digits but the last two digits are always 00. That is providing inaccurate data.

I've attached a word document with a real-life example. (attach the file again.)

BJ Young

Marcelo Finkielsztein

@BJ Young ,

Hello BJ,

The way I have worked around this problem was by converting the column to CHARACTER; more specific, convert the CSV column to something that Excel will interpret as character, e.g. prefix the column with an "S". In the DV, create a calculation that concatenates 'S' || "SDID Column Name". Then, export that as SDID value. As an alternative, if the SDID is normally formatted with dashes (or spaces, etc) in the middle, like credit cards showing like this 4519-1234-1234-1238, then you could create a calculation that concatenates digits and dashes; Excel will interpret that string as a "string". Do not prefix such string with an "=" sign. or Excel would interpret it as an Excel formula.

Ultimately, if you really really need to show the SDID numbers as only a stream of digits, you could create a DV calculation that shows an Excel formula!.

Example: a csv file with two columns, SDID and MONEY. SDID is actually an Excel formula showing the formula ="1234...7". Silly, but Excel will interpret it as formula and will show the result nicely to the user.

Note the use of double double-quotes; this is the way to "escape" a double quote in a CSV file.

As s quick test, copy-paste the following into a CSV file, and then open the file in Excel.

------ file begins on next line -------------------------------------

SDID,MONEY

"=""12345678901234567""",-500.00

"=""12345678901234567""",600.41

"=""12345678901234567""",18.22

------ file ended above this line -------------------------------------------

Hope this helps,

: ) Marcelo

BJ Young

Thanks Marcelo! Transforming the data is not an efficient use of our users' time. In Storm Mode, Dispatchers and Customer Account Managers may need to get this data out of OAC very quickly. If Oracle could offer an export to Excel, that would be a benefit to usability and user adoption.

Marcelo Finkielsztein

We would appreciate a feature that exports Formatted Excel, similar to what Classic Home Page does.

The limited functionality to only download to CSV affects our user adoption.

Thanks.

Marcelo Finkielsztein

I would be very pleasantly surprised if Oracle decided to export formatted as Excel and at the same time implement some fix that would give us longer than 16 digit numbers properly rendered. Fingers crossed.

Marcelo