Summary

When invoking an OData service, you do not get the expected response but data with HTML code to render an error page:

Applies to

Bizagi 11.1 version and above.

Symptoms

No OData service seems to work with a different response. Rendering the HTML code into an .html page, you will see the following detail, having a path indicating the cause of the error:

Cause

Paying close attention to the path, you will notice that there should be a typo for either the odata or data/metadata part of the URL.

Solution

Ensure you adjust the URL avoiding typos (ensure you use data exactly or metadata exactly):

The image above shows incorrect use (adata is the typo). For this example, once you adjust it to data, the OData service should work correctly.