Forum Discussion
PARTITION CONFIGURATION ERROR
Hi everone,
I imported data and made reports already. But now when I change the datasource of a table to odata, there is an error like this
I also tried another way by just importing the data, not replacing anything. But the error still incurred.
If I open a new report and import, it is ok.
I don't know what happened and how to solve it?
6 Replies
Hi all,
I imported a data and made report based on it. Now when I change the datasource of a table, there is an error like this:
"Failed to save modifications to the server. Error returned: 'Partitions that contain a full dataset (not sampled data) have to be configured for DirectQuery and Full Dataviews, or use Import query mode to retrieve data. This model apprears to have partitions that are non-compliant. Please check partition configuration.'."
I also tried another way by just importing the odata into the report, not replacing anything data. But the error still incurred.
If I open a new report and import the odata, it is ok.
I don't know what happened and how to solve it?
it appears whether it is direct query or import mode, which depends the database structure.
and it is not really depends on the user's selection.
am i right?
Anonymous,
I came across this issue as well. It appears that if you deselect the "Enable Load" on the original queries that were brought in so that only the merged query remains, the merged query will then load without giving you the partition error. Everything is still in DirectQuery but only the merged table is available to use the visuals, filters, etc. in the report.
