Forum Discussion
Problems importing PBIX by means of REST APIs
I cracked it by finally figuring out where I had to look on this board, also taking my inspiration from here. As some of you might know by now, the problem was the Connections file in the pbix zip archive that had to be altered, so that it would containsinformation about the dataset that the report is supposed to be connected to.
Looking into the structure of the connections file, it is nothing more than a hashtable converted to JSON, and if one wishes, the connection can be easily modified by renaming the pbix file to a zip file, unzipping, rewriting the connections file, zipping and renaming again.
I cracked it by finally figuring out where I had to look on this board, also taking my inspiration from here. As some of you might know by now, the problem was the Connections file in the pbix zip archive that had to be altered, so that it would containsinformation about the dataset that the report is supposed to be connected to.
Looking into the structure of the connections file, it is nothing more than a hashtable converted to JSON, and if one wishes, the connection can be easily modified by renaming the pbix file to a zip file, unzipping, rewriting the connections file, zipping and renaming again.
Anonymous wrote:
I figured it out by finally figuring out what I had to look for on this board, taking my inspiration from here. As some of you might know by now, the problem is the Connections file in the pbix zip archive that has to be altered, so that it contains information about the dataset that the report is connected to.
Looking into the structure of the connections file, it is nothing more than a hashtable converted to JSON, and if one wishes, the connection can be easily modified by renaming the pbix file to a zip file, unzipping, rewriting the connections file, zipping and renaming again.
Anonymous
So you mean someone has unzipped the pbix file and changed the connection file? By no means it is supported offcially, I'd suggest avoiding such operations.
Eric_Zhang That is exactly it, and you're right - this is also mentioned in the blog post that I referred to.
I posed the question originally, because the clone API did not seem to do what I wanted. When cloning a report from one workspace to another (as described in Sirui Sun's tutorial), the clone API would incorporate the original dataset in each of the multiple reports. I can not make sense of why it does so, and I have been using the exact same code that Sirui used for that purpose.
Im having a sililar issue. What did you have to change in the connection file?
