We don't want a new PageType of APIPart, just make it so any API type page can be added to an existing API type page as a part wherever you can put a field.
The API Part would have link properties that would require you to set the OData Key Fields for the sub part to values derived from the parent (just like a page part does now).
Comments
Hasn't this been solved already?
Category: Development
I'm struggling to understand the status of this idea. It looks like you have implemented this already in the API v2.0 as many of the entities have parts inside repeaters.
Category: Development
I also thought that the fields that are used to join the APIPart to the parent record should be hidden automatically from the complex type in the JSON for the API and set automatically in any incoming request.
I realise that in the API 2.0 complex types have been removed from the standard APIs, but when working with interfacing, the need to send a single request to insert multiple records in different but related tables is really important for performance reasons.
Category: Development
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team