Forum Discussion
UI Import - Not replacing reports in folders
- 9 months ago
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.
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.
- Wizygran9 months agoNew Member
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!