Usability annoyance regarding data uploads

Would be nice to be able to delete uploads when in the "Upload Data" section (besides being able to update them) and be able to update them in the "Uploads" section. When trying to work around the issues I have with the upload and put the data into an acceptable form, having to switch between these two screens ("Upload Data" and "Uploads") gets quite annoying.

I’m sad

Inappropriate?

Reply to this idea

3 people like this idea

I like this idea! Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.

The company has this under consideration.

Create a customer community for your own organization

Plans starting at $19/month

EMPLOYEE

Remove Inappropriate?
Delete or Edit for 15 minutes

ZD, Official Rep, replied on December 09, 2008 10:02

Yep, you are right. We will take this on account in the upcoming UI redesign that we have planned for January.

Nice catch!

this is one of the best points

Add a comment This is one of the best points Mark as a company good point
Remove Inappropriate?
Delete or Edit for 15 minutes

Arjen de Ruiter replied on May 04, 2009 20:33

Yep deleting uploads is required to easily recover from incorrect loads.
You could work around updates by pushing a delta from your data warehouse to GoodData. You need to capture Before Image and After Image to calculate the delta.

Before image, sales order ID 1234 = USD 100
After image, sales order ID 1234 = USD 110
Delta, sales order ID 1234 = +10

Now push a new record with the delta to GD and group by sales order ID 1234 and you have SUM sales 100+10=110. SAP BI cubes work this way, and probably that is also why it is so slow :) But with small, highly aggregated data sets it will work.

I’m undecided

this is one of the best points

Add a comment This is one of the best points
EMPLOYEE

Remove Inappropriate?
Delete or Edit for 15 minutes

Petr Olmer, Official Rep, replied on May 06, 2009 07:57

Arjen, I don't think we're going by SAP way. So far, we're more concerned about snapshoting historical data. If sales order ID 1234 was $100 and is $110, we want to store both values with timestamp, understand why it was changed, and allow users to analyse it.

Otherwise, we could use the ROLAP advantages, and just update the ID 1234 record with new value. We don't calculate any cubes during data upload.

I’m excited

this is one of the best points

Add a comment This is one of the best points Mark as a company good point
EMPLOYEE

Remove Inappropriate?
Delete or Edit for 15 minutes

Jerome Pineau, Employee, replied on October 10, 2009 18:53

Actually what I'd like to see is the ability to upload a file and its corresponding DDL as well so i dont have to manually enter all the column info. Even being able to paste DDL somewhere would be nice.

this is one of the best points

1 Comment Add a comment This is one of the best points Mark as a company good point
Remove
ZD, (Official Rep), commented on October 12, 2009 09:38

There are few different ways how to load data into a Good Data project. These differ in the amount of data that the product requires from user.

We have started with implementing web UI for the simplest one. We plan on introducing an advanced data loading options that will allow specifying metadata in some more declarative format. We are considering extending the MAQL language with some DDL statements.