This optimization doesn't apply to Role Center pages. Does this optimization apply to parts that aren't FactBoxes? Using properties such as SubPageView is preferred to writing trigger code to update a FactBox. The use of these properties has no effect on the sequence of loading content on a page. Does this optimization work with SubPageLink or SubPageView properties? For more information about asynchronous processing in the background, see Designing page parts for page background tasks. This optimization is simply a controlled sequence in which triggers are run, still within the same session as the hosting page. Once a FactBox is loaded, it isn't loaded again for as long as the page remains open. In this scenario, the OnOpenPage trigger is only run the first time. How often are triggers run if the FactBox pane is expanded, collapsed, and then expanded again? The trigger is only run when the FactBox is visible and within the user's view. Avoid having triggers on the hosting page that call into a FactBox because this condition forces the FactBox to ignore performance optimizations and load along with the content of the hosting page, adding to the total loading time.įAQ about performance Are any FactBox triggers run when the FactBox is hidden?.Learn more about Using Page Background Tasks. For FactBoxes that require heavy processing, consider processing in the page background task.Learn more about Choosing the Visibility of Parts. Consider hiding any FactBoxes that represent secondary content that only some users will require.If the FactBox pane is collapsed, no FactBoxes are loaded until the user expands the FactBox pane.īelow are some practical tips to help you make the most of this optimization: FactBoxes that aren't within view are only loaded when the user scrolls them into view.FactBoxes having the Visible property evaluate to false won't be loaded.The FactBox pane is loaded next, where each FactBox is loaded independently in sequence starting from the top.Content on the hosting page is loaded first, and users can immediately begin interacting with it.To improve responsiveness and the time it takes to load the page, Business Central 2020 release wave 2 and later optimizes the sequence in which content is loaded. Having a page composed of multiple FactBox pages that each process data from different sources can degrade performance. Part(CustomerList "Customer Details FactBox") Example page 50101 "Simple Customerlist Page" You can also filter on a constant value or set of conditions. To implement this functionality, you set up a table filter that associates a field in the table that is used by the Customer Details page with a field in the table that is used by the Customer List page, as shown in the example below. When a user selects a customer in the Customer List, the Customer Details page displays information about the selected customer. For example, if the main page is a Customer List, you can have a FactBox that includes the Customer Details page that shows information about a customer. In many cases, you want to change the content that is displayed on the page in the FactBox based on the content of the main page. Filtering data that is displayed on a page in a FactBox These values are ignored in the Business Central Web client. These values are only supported by the Dynamics NAV Client connected to Business Central (which has been deprecated after Business Central Spring 2019). The systempart keyword also includes an Outlook and MyNotesvalue, for example, systempart(Outlook Outlook). You can add a FactBox area control on the following page types. The FactBox area control acts as a placeholder to which you can add different parts for the FactBox. You define the FactBox by adding a FactBox area container control to the page. For example, Bing maps, PowerBI, Microsoft Social Engagement, and more. Visualize related data or display from external sources which are modeled as CardParts containing a Client AddIn.For more information, see Designing Role Centers. Show related KPIs which are modeled as CardParts with charts or Cues.Show related records/fields which are modeled as ListParts or CardParts.The following list highlights a few categories of FactBoxes: For example, on a page that shows a sales order list, you can use a FactBox to show sell-to customer sales history for a selected sales order in the list as shown below. Typically, you can use a FactBox to display information that is related to an item on the main content page. This area is used to display content including other pages, charts, and system parts such as Notes, and Links. 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.
0 Comments
Leave a Reply. |