Forum Discussion
Powerbi Dataset underlying Table Name change Observation
I imported a table in Powerbi , Gave the Individual dataset the same name as the Original table name and Published the dataset on the server.
TABLE NAME - ABC
DATASET NAME - ABC
WORKBOOK NAME - ABC DATASET.PBIX
I created couple of reports using the Powerbi Dataset and was told to use an earlier dataset since the 2 tables contain the same data.
EARLIER POWERBI DATASET AND UNDERLYNG TABLES
TABLE NAME - PQR
DATASET NAME - PQR
WORKBOOK NAME - PQR DATASET.PBIX
Now when I change the underlying dataset my reports start failing because the naming convention of the 2 datasets are different
ABC(CURRENT) and PQR(OLD).
I tried changing the ABC DATASET to PQR published it and PowerBI doesn't even recognize that.
Can I avoid the rework after changing the underlying dataset ?
Note : I can't change the old dataset as it already used at multiple places.
Really Appreciate the help
4 Replies
- vanessafvgCommunity Champion
can you provide the actual error you are getting?
sorry I am not actually clear on what the issue is. what does power bi not recognize, can you give more detail in into the actual error you have
from what i understand you want to point back to the new dataset? not quite sure why you are not able to? what error do you get exactly?
- Vivek26Advocate I
Step 1 . Imported Oracle Table Named ABC
Step 2 . Transformed some minor things and kept the name ABC in Powerbi Table
Step 3. Published the Dataset on PowerBI service with the name ABC dataset
Step 4. Opened a New workbook , Used the ABC dataset as live connection from Powerbi Service
Step 5 . Realized another publihsed datasource exists on Powerbi Service ( The dataset and underlying table is Named PQR)
Step 6 . Tried to change the workbook created in step 4 by using the step 5 dataset.
Step 7 . PowerBI starts giving error saying no such fields exists .
Earlier the fields were ABC[SALES_DATE] , Now the fields are PQR[SALES_DATE]
Step 8 . Went back to ABC dataset changed it to PQR republished the dataset , even then it fails to recognize .
If this was a simple Import , PowerBI would have handled it with live connection its causing an issue
- vanessafvgCommunity Champion
after you changed the dataset, did you refresh the metadata of the power bi desktop before you republished it? Even if its a live connection you will still need to update the metadata
- Vivek26Advocate I
My Problem is close what's mentioned in this thread