You’re offline. This is a read only version of the page.
Announcements
6
Hello,
I’ve created a custom API page in Business Central (On-Premise) for exposing data to Power Apps. The API page is defined with PageType = API, and includes valid EntityName and EntitySetName properties. The API is successfully published and accessible via browser at the following endpoint:
The JSON response appears correctly when I access this URL directly, so I’m confident the page is functional. However, when I try to connect from Power Apps using the Business Central (On-Premise) connector, the custom API page (salesorder) is not listed in the available tables. Even when I manually enter the EntitySetName in the "Enter custom table name" input, the Connect then it shows not found.
I suspect this may be related to how the connector interprets custom APIs or some limitation in listing custom API pages via the standard connector. If anyone has encountered this issue or knows of a configuration step that might be missing—such as additional metadata publishing or service tier configuration—I'd appreciate any help or suggestions.
Thanks,
Tushar
Hi Tushar,
Thanks for your detailed explanation! You're on the right track—this issue is commonly related to how the Business Central On-Premise connector interacts with custom API pages.
Here are a few things to check:
OData Metadata Publishing: Ensure that your custom API page is included in the OData metadata document. You can verify this by accessing:
Look for your EntitySetName in the XML. If it’s missing, the connector won’t recognize it.
API Page Configuration:
Share
Report
All responses (
Answers (
PageType = APIEntityName and EntitySetName are unique and correctly definedWeb Services Publishing: In Business Central, go to Web Services and verify that your API page is listed and published. If not, add it manually.
Connector Limitations: The On-Premise connector may not automatically list custom API pages. Try using custom connectors in Power Apps with the full endpoint URL if the standard connector fails.
Service Tier Configuration: Ensure that the OData services are properly configured and enabled in your Business Central service tier settings.
If all else fails, consider using Power Automate with HTTP actions or a custom connector to consume the API directly.
Hope this helps!
Please mark this response as helpful if it answered your question.
Best regards!
