Today I would like to briefly talk about whether we can extend TableRelation Property through a table extension.
In conclusion, yes we can, but with some limitations.
Sometimes you have to update a posted document because information that is relevant to the document has changed. On a posted sales document, this can be the shipping agent’s package tracking number, for example. On a posted purchase document, this can be a payment reference text.
In the previous blog post, I’ve demonstrated how to extend standard APIs by using them as a template for a new custom API that contains the customizations you want to do. While that approach works for most APIs, there are some APIs that are more complicated. I’m talking about APIs for sales and purchase documents. These APIs are special because they are not based on the standard tables Sales Header, Sales Line, etc.
I’ve got this question so many times: how can we extend the standard APIs with extra fields? So I decided to write a blog post about it. Actually, it’s going to be two blog posts, because one would become too long. So here it goes…
I’ve been pretty quiet on the blogging front for the last few months – settling in to a new team and a new role.
For the first post of 2021 what better topic than Item Tracking? Let’s be honest, the Item Tracking Lines page is a mess. Over 3,000 lines of code, tonnes of global variables and more than 60 methods. I don’t think the fundamental design of the page has changed much since it was introduced – it’s a bullet that no one wants to bite.
As most of you, I guess know, it is not allowed to extend Business Central API’s. This page type cannot be extended by creating a page extension object. Instead, you must create a new API by adding a page object
However, sometimes we just need to send more data about the entity: Customer, Vendor, Sales/Purchase documents etc.