Qlik Community

Qlik Sense App Development

Discussion board where members can learn more about Qlik Sense App Development and Usage.

Not applicable

QS Error: The object could not be saved

Hi,

We are creating an app in QS Enterprise and are using QVD to load data. While saving the app, it fails with below error:

Started loading data

BT_CUSTOMERS

(QVD (row-based) optimized)

Lines fetched: 838,772

SALES_ORGANIZATION

(QVD (row-based) optimized)

Lines fetched: 7,319

SOURCE_SYSTEMS

(QVD (row-based) optimized)

Lines fetched: 19

TIME_PERIOD_DATE

(QVD (row-based) optimized)

Lines fetched: 220,245

PRODUCTS_DIM

(QVD (row-based) optimized)

Lines fetched: 21,496,315

INVOICE_LINES_FACT << INVOICE_LINES_CURR_YEAR

(QVD (row-based) optimized)

Lines fetched: 8,785,719

INVOICE_LINES_FACT << INVOICE_LINES_PREV_YEAR

(QVD (row-based) optimized)

Lines fetched: 18,059,868

OSO_LINES_FACT << OSO_LI_MONTH_CURR_YEAR

(QVD (row-based) optimized)

Lines fetched: 16,430,666

OSO_LINES_FACT << OSO_LI_MONTH_PREV_YEAR

(QVD (row-based) optimized)

Lines fetched: 36,627,305

QUOTE_LINES_FACT << QUOTE_LINE_ITEM_PREV_YEAR

(QVD (row-based) optimized)

Lines fetched: 30,808,951

QUOTE_LINES_FACT << QUOTE_LINE_ITEM_CURR_YEAR

(QVD (row-based) optimized)

Lines fetched: 56,073,271

$Syn 1 = %BILL_TO_CUSTOMER_SKEY+%SELLING_LOCATION_SKEY+%SSID+%TIME_PERIOD_DATE_SKEY+%PRODUCT_SKEY

The object could not be saved.

Data has not been loaded. Please correct the error and try loading again.

Can someone please point out what might be the cause and how can we troubleshoot it? Any log in particular that can help?

Server: VM - Windows 2012, 32gb RAM, 4 core, 100GB HDD (40GB free)

Thanks!

2 Replies
csellei
Contributor

Re: QS Error: The object could not be saved

We're running into the same issue.

Did you solved it?

Regards.

Chrisitan.

Employee
Employee

Re: QS Error: The object could not be saved

the last line shows creation of a synthetic key that looks a little nasty... lots of fields.

I doubt its intentional.

You can enter:

qualify *;

...at the beginning of the load editor to ensure no links of any kind are formed during the data load. If it works then you know its due to to the synthetic key and you will have to address that in the model