Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
1 year ago
Solved

Fabric - Create Reports model via Microsoft Fabric API

Hello Everyone, I'm using the Microsoft Fabric REST API to programmatically deploy a report to a workspace. The semantic model already exists and is verified in the workspace. I'm sending a POS...
Need Help
Tips and Tricks
  • v-achippa's avatar
    v-achippa
    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

Anonymous's avatar
Anonymous
Not applicable
1 year ago

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-achippa's avatar
v-achippa
Community Support
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

  • Anonymous's avatar
    Anonymous
    Not applicable
    1 year ago

    ok let me redifine the workflow again and will provide an update here.

    • v-achippa's avatar
      v-achippa
      Community Support
      1 year ago

      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?
      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

      • v-achippa's avatar
        v-achippa
        Community Support
        1 year ago

        Hi @raza19,

         

        We wanted to kindly follow up to check if the solution I have provided for the issue worked.
        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