Forum Discussion
UI Import - Not replacing reports in folders
Hi.
I've come across very weird issue. I couldn't find if it's already a known issue.
I have python script deploying my reports to the workspace using imports API. At first I though it is something wrong with my code, because the reports which had path Workspace/someFolder were not replaced - instead new report with exact same name and connection was created in Workspace, instead of replacing the one in the Folder. When the report is in the workspace, not within the folder, then replacing works fine.
I know it's not issue with the code because by using simple Import in the workspace, I come across the same exact issue. It seems weird to me..
Anyone came across that? Thank you in advance.
Could you share a quick example of the Python request you’re using? Specifically: any query parameters you’re passing (subfolderObjectId, etc.)
It would help confirm whether the call is folder-aware. Microsoft recently added the subfolderObjectId parameter, so if your code doesn’t include that, the import will always create the report at the workspace root even when a folder exists.
3 Replies
Could you share a quick example of the Python request you’re using? Specifically: any query parameters you’re passing (subfolderObjectId, etc.)
It would help confirm whether the call is folder-aware. Microsoft recently added the subfolderObjectId parameter, so if your code doesn’t include that, the import will always create the report at the workspace root even when a folder exists.
Hi, this answer is actually amazingly valuable. That's the fact, /imports call expects subfolderObjectId. The biggest problem was which call to retrieve that as I was expecting it from GET /reports. The one listing reports and its folders is Fabric API GET /items. I added both to the flow and it's working fine! Thank you!
I seem to recall that folders are not yet supported for the import calls.
