Forum Discussion
How to edit Workspace Dataset created in Visual Studio?
Hi gmelhaff
What you can do is a combination of the following:
- Open Visual Studio and go into each table, then right click and go into table properties.
- At the same time have your PBIX open and go into Power Query Editor
- Now right click on the table in Visual Studio and select Copy
- Go into PQ in your PBIX and right click and select Paste.
- This will paste the table there.
- Do this for all your tables.
- Now to copy the measures open Tabular Editor connected to your Visual Studio Project.
- Open Tabular editor connected to your PBIX
- Then paste all the measures into the same table.
- All that is now left to do is to create the relationships.
- I typically keep my PBIX file seperate from my PBIX with the visuals. So that changes in the reporting layer area quick and easy to deploy.
I hope that helps.
Hi gmelhaff
What you can do is a combination of the following:
- Open Visual Studio and go into each table, then right click and go into table properties.
- At the same time have your PBIX open and go into Power Query Editor
- Now right click on the table in Visual Studio and select Copy
- Go into PQ in your PBIX and right click and select Paste.
- This will paste the table there.
- Do this for all your tables.
- Now to copy the measures open Tabular Editor connected to your Visual Studio Project.
- Open Tabular editor connected to your PBIX
- Then paste all the measures into the same table.
- All that is now left to do is to create the relationships.
- I typically keep my PBIX file seperate from my PBIX with the visuals. So that changes in the reporting layer area quick and easy to deploy.
I hope that helps.
HI GilbertQ Sent private message....not following originally but finally realize you were talking about opening 2 instances of tabular editor - one from within external tools in PBIX and the other for connecting to the SSAS model. Then copy paste within tabular editor works. If you try to startup tabular editor when connected to SSAS or PBI dataset it just gives an error message but when you do it from brand new pbix its happy. There was no copy from visual studio possible which threw me. Would have appreciated more clarity what you were talking about would have saved me couple hours work trying to figure this out but in the end its working well. Thank you very much.
Roadblock is this...I'm having same issue reported here...Unable to save files as Enhanced Dataset Metadata ... - Microsoft Power BI Community.
I have latest version of Power BI desktop and yet it isn't saving as V3 metadata and tabular editor is complaining and behaving badly possibly as a result of this. The bugs with powerbi seem endless 😞
Attempting to either refresh or upgrade simply results in discarding any changes made in tabular editor.
So its available here in case anyone is looking for solution....What was proposed above in the end did not work. I have resorted to manually re-creating table imports in PBIX that were used in SSAS and copy/paste DAX code from Visual Studio into PBIX. That's really not that difficult as I had assumed. Just tedious is all for large model. I would not advise attempting to do some kind of conversion - its a time suck and you'll likely even if somehow succesful end up with model that doesn't work for power bi service incremental refresh based on timestamps which is one of the advantages of using datasets on PowerBI service over SSAS server.
Learnings when attempting above...
PQ doesn't appear in VS 2019 so that's not a thing at least in the latest version.
Copying tables with tabular editor from SSAS to PBIX corrupts the pbix model.
Attempting some kind of tool-based conversion from SSAS to PBIX is a waste of time.
And even IF you were succesful in somehow copying a table that results from a SQL query it would seem to be an invalid method for incremental refresh purposes since parameterized incremental refreshes in Power BI service is very picky and requires full table import so it can add it's DAX parameters on the end of the table query. Read below article that talks about this limitation...
