In my daily work I often encounter interfaces and web services of any kind. Whether inbound or outbound, they usually use some kind of payload in the form of JSON these days. No matter if it’s the outgoing object or the response of the web service.
A FactBox is the area that is located on the right-most side of a page and it is divided into one or more parts that are arranged vertically. This area is used to display content including other pages, charts, and system parts such as Notes, and Links. Typically, you can use a FactBox to display information that is related to an item on the main content page.
Today, I was working on new Merging for Upgrade to Business central and i came across FACTBOX in Business Central. So i thought of sharing this with you.
Factbox area is normally located on the Left side of the page and is used to display content including other pages, charts, and system parts such as Notes, and Links.
Today, I was working on a new E Foqus product and this is something that needs a fair amount of FactBoxes.
It could be solved using a single FactBox object throughout the system. I started with a C/Side approach, trying to get the information from the parent page into the FactBox with SubPageLink but that didn’t work. I was even trying to be too creative with the new SystemId field.
Factboxes are more then ever a powerfull way for presenting related information. Normally you link your Factbox through properties, but now and then you need to do this from code.
This works fine if your page has at least one record, because the filtering is set on the “OnAfterCurrRecord” trigger of the page. So when there is no records, no filter is set on you factbox and then all related records are shown.