Small and medium business | Business Central, N...

D365 BC cloud API extension development

(8) Share

Report

Posted on by WF-14012240-0

HI
I am developing APP extensions for Business Central. Currently in the ISV success program and looking to achieve a MS Marketplace Presence
I have had success in developing a Generic - one size fits all solution - an APP extension that any BC customer can use
The next step is to have custom fields available
My approach is to have a separate app extension to handle this as a Per tennant Extension

is that the best approach?

I have tried this successfully in my demo BC org

But I have encountered a problem with the custom APP extension on a REAL customer site - the custom Query is visible inside BC but not externally (eg via postman)

I am using the same publisher name and group in both extensions. Am I missing something?

I did test the idea of publishing as a web service - this works , but I prefer to not go via Odata publishing as I am bulk fetching data and this way can be less optimal.

most appreciate guidance here from the community, many thanks

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

YUN ZHU 95,305 Super User 2025 Season 2 on at

Like (3)

Report

D365 BC cloud API extension development

Hi, Is your query an API type?
Hopefully, the following information will give you some hints.

Dynamics 365 Business Central: API query type (Develop a custom API using Query)

https://yzhums.com/57475/

Thanks

ZHU

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 5,048 on at

Like (2)

Report

D365 BC cloud API extension development

Hello,

Yes, your architecture is correct:
AppSource app for the generic product + a per-tenant extension for customer-specific fields.

But your custom query is not showing in Postman because a normal Query object is not exposed on the Business Central API endpoint.
Only API Pages and API Queries appear under:

/api/{publisher}/{group}/{version}/...

So your PTE must expose the data using:

QueryType = API
or

PageType = API

Otherwise Postman will never see it.

Using the same publisher/group is correct, you are not missing anything else.

Regards,
Oussama Sabbouh

2 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Jainam M. Kothari 15,625 Super User 2025 Season 2 on at

Like (2)

Report

D365 BC cloud API extension development

Hello,

Using a separate per-tenant extension for custom fields is a solid approach because it keeps your generic app marketplace-ready while allowing customer-specific customizations.

However, queries in per-tenant extensions aren’t automatically exposed via APIs; they need to be published as web services or implemented as API pages.

Matching publisher and group names doesn’t make queries externally accessible because API contracts depend on API page objects, not queries.

For optimal external access without OData publishing, create API pages for custom fields using the same API publisher, group, and version as your main app.

2 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Rishabh Kanaskar 6,147 on at

Like (2)

Report

D365 BC cloud API extension development

Hi,

Yes, your approach is correct: keep the generic app for AppSource and use a Per-Tenant Extension for custom fields.
The query issue occurs because standard Query objects are not exposed via the API. To make it accessible externally without OData web service publishing, create an API Page or API Query (BC 21+) with APIPublisher, APIGroup, APIVersion, and unique EntitySetName. Assign proper permissions and call it through the API endpoint.
If both apps share publisher/group, ensure unique APIVersion or entity names to avoid conflicts.

Thanks

Rishabh

Was this reply helpful? Yes No
WF-14012240-0 32 on at

Like (0)

Report

D365 BC cloud API extension development

Many thanks, It is good to know I have the right approach by having a "generic" common App extension to publish and and separate custom Per Tennant Extensions for custom work.

I still have the issue of not seeing being able to see the custom queries outside of BC

My extension is of type "API" as suggested by others

I suspect it is a permission thing with ENTRA somehow blocking / requiring re-approval for the app registration.

meanwhile I have to publish the custom query as an ODATA service to see the data externally.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 95,305 Super User 2025 Season 2 on at

Like (1)

Report

D365 BC cloud API extension development

This is a bit strange. I suggest submitting a SR to Microsoft and asking them to assist in the investigation.

Thanks.

ZHU

1 people found this reply helpful.

Was this reply helpful? Yes No