3
When creating a new API page with a table relation, you can expand (OData $expand) the table relation if the related record type has a page of type API.
For example, if you create an API page for Sales Header, and another API page for Customer, then you can expand the Sell-to Customer No. using $expand=customer.
This does not work when there are multiple table relations to the same table - it doesn't work for Bill-to Customer on the same page as there is only one NavigationProperty added per related table type.
It would be good if we could define the NavigationProperty Name on fields that have a table relation. This would allow us to have multiple NavigationProperty elements for the same record type.
Something like this:
For example, if you create an API page for Sales Header, and another API page for Customer, then you can expand the Sell-to Customer No. using $expand=customer.
This does not work when there are multiple table relations to the same table - it doesn't work for Bill-to Customer on the same page as there is only one NavigationProperty added per related table type.
It would be good if we could define the NavigationProperty Name on fields that have a table relation. This would allow us to have multiple NavigationProperty elements for the same record type.
Something like this:
STATUS DETAILS
Needs Votes
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