OData Error in Power BI: API Cannot Be Run for This Form (400 Bad Request)

[Malav]

I’m facing an issue while connecting my data source into Power BI via OData Link. My setup involves using Priority Web Software as the backend and establishing a connection through the OData feed connector in Power BI Desktop. However, when I attempt to load data, I encounter the following error:

DataSource.Error: OData: Request failed: The remote server returned an error: (400) Bad Request. (API cannot be run for this form.)

 

Steps Taken:

1. Tested the OData URL in a browser, and it returns the metadata.
   
   
   

    

2. Confirmed that other forms from the same OData endpoint are accessible in Power BI without issues.
   
   

Questions:

1. How can I confirm whether this specific form is configured to support API requests?
2. Are there any specific configurations or permissions I need to check in Priority Web Software to make this form accessible via OData?
3. Is there a workaround in Power BI to fetch data from forms that are not directly accessible via OData?

 

Additional Context:

I suspect this issue may be related to the API configuration on the server-side, as the error indicates the API cannot run for this form. I’ve consulted the Priority documentation but couldn’t find clear guidance on enabling API access for forms.

Any insights or guidance would be greatly appreciated!

[Expiscornovus]

Hi @Malav,

Can't you reach out to Priority Software support? It is probably more likely that they can help you out, since they build the software.

It looks like they also have a Postman collection, it might be good to try and reproduce it in Postman, instead of the browser, that might give you some clues as well: https://prioritysoftware.github.io/restapi/

[Malav]

Hi @Expiscornovus ,

Thank you for taking the time to look into this and for your valuable suggestions! I appreciate your guidance on testing with Postman and reaching out to Priority Software support.

I did try using the Postman API Client, but unfortunately, it generates the same response:
400 Bad Request: API cannot be run for this form.

As per your advice, I have passed on the suggestion to contact the Priority Software support team to the responsible resource within my organization. I hope they can provide further insights or a resolution to this issue.

Thanks again for your support—it’s greatly appreciated!