Forum Discussion
Fabric - Create Reports model via Microsoft Fabric API
- 1 year ago
Hi Anonymous,
The error here is likely caused by a manually modified .pbir or report.json file, or the semantic model is not being referenced in the exact format expected by the API.
So please switch back to the byConnection which you were using earlier since the Fabric REST API supports it.
And try the above steps which i mentioned earlier like re-export the report again using power bi desktop and connect to the live semantic model in the same Fabric workspace. Do not modify any of the generated files. Encode each file in Base64 and send it to the API.
This makes sure the byConnection block is generated correctly by the backend schema.
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Thanks and regards,
Anjan Kumar Chippa
Thanks for you response
I updated my defination file
{
"version": "4.0",
"datasetReference": {
"byPath": {
"workspaceObjectId": "give-myId",
"datasetObjectId": "semantic-id"
}
}
}
I tried you solution and update byPath but got the error
Property 'workspaceObjectId' has not been defined and the schema does not allow additional properties. Path 'datasetReference.byPath.workspaceObjectId', line 6, position 26.
Property 'datasetObjectId' has not been defined and the schema does not allow additional properties. Path 'datasetReference.byPath.datasetObjectId', line 7, position 24.
In the documentation I found the important Not that we need to use byConnection while using Fabric API.
The Link of documentation is HERE
Let me known am i correct or doing something messy
Thanks!
Hi Anonymous,
Please try re-exporting the report as a Power BI Project (.pbir) using Power bi desktop with the preview feature enabled:
- Open Power bi desktop and connect to the exact semantic model in the Fabric workspace, go to File --> Export --> Power BI Project (.pbir).
- Use the generated definition.pbir, report.json, and .platform files without any modifications. Encode each file in Base64 and deploy via the Fabric REST API.
This ensures all the required fields are correctly generated and match the backend schema.
If the issue still persists after this, double check that the semantic model is published to a Fabric enabled workspace, not a classic workspace. And share the full API error response including the inner error if available.
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Thanks and regards,
Anjan Kumar Chippa
- v-achippa1 year agoCommunity Support
Hi Anonymous,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution I have provided for the issue worked? or let us know if you need any further assistance.
If my response addressed, please mark it as "Accept as solution" and click "Yes" if you found it helpful.Thanks and regards,
Anjan Kumar Chippa
- Anonymous1 year agoNot applicable
Hi Anjan,
Thanks for your response
I just re-exported but that issue is still here. The error I am facing is below:
Error response:
Property 'workspaceObjectId' has not been defined and the schema does not allow additional properties. Path 'datasetReference.byPath.workspaceObjectId', line 6, position 26.
Property 'datasetObjectId' has not been defined and the schema does not allow additional properties. Path 'datasetReference.byPath.datasetObjectId', line 7, position 24.
I just try from PATH as you mentions but facing that error. The semantic model also created in Fabric enabled workspace. But somehow while creating the reports i am facing that error.
Its still not fixed
Thanks- v-achippa1 year agoCommunity Support
Hi Anonymous,
The error here is likely caused by a manually modified .pbir or report.json file, or the semantic model is not being referenced in the exact format expected by the API.
So please switch back to the byConnection which you were using earlier since the Fabric REST API supports it.
And try the above steps which i mentioned earlier like re-export the report again using power bi desktop and connect to the live semantic model in the same Fabric workspace. Do not modify any of the generated files. Encode each file in Base64 and send it to the API.
This makes sure the byConnection block is generated correctly by the backend schema.
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Thanks and regards,
Anjan Kumar Chippa
- Anonymous1 year agoNot applicable
ok let me redifine the workflow again and will provide an update here.