web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

Unable to Hide Fields Conditionally in FactBox

(4) ShareShare
ReportReport
Posted on by 40

I have several fields in a FactBox, and I want to control their visibility dynamically based on certain conditions.

However, even after setting the Visible property (or using a Boolean variable), I am unable to hide those fields—they remain visible.

Is there any limitation or specific approach required to control field visibility in a FactBox page?

Has anyone encountered a similar issue or knows the correct way to hide FactBox fields conditionally?

  • Suggested answer
    OussamaSabbouh Profile Picture
    19,544 Super User 2026 Season 2 on at
    Hello,
     
    Yes, this is a common FactBox limitation: you cannot control visibility of FactBox fields from the parent page—only the FactBox page itself can do that. To hide fields conditionally, the logic must live inside the FactBox (CardPart/ListPart) using a global Boolean variable bound to Visible, usually marked with [InDataSet], and set in OnAfterGetCurrRecord or OnOpenPage, often followed by CurrPage.Update(false) so the client refreshes. If the condition depends on context (where it’s opened from), expose a public procedure on the FactBox and call it from the host page. Expecting the host page to hide individual FactBox fields is not supported.
    Regards,
    Oussama 
  • Rudylar Profile Picture
    117 on at

    [InDataSet] is going Obsolete…

    My Usecase: PageA lists records of TableA. Factbox (has SubPageLink with PageA) is located on PageA. TableA/Field1 (integer) shall be Visible only if value>0. Factbox shall be updated on record selection in PageA.

    “global Boolean variable bound to Visible, usually marked with [InDataSet], and set in OnAfterGetCurrRecord or OnOpenPage, often followed by CurrPage.Update(false) so the client refreshes” → does not work for me

     

    “If the condition depends on context (where it’s opened from), expose a public procedure on the FactBox and call it from the host page.” → public procedure on the factbox side and using a CurrPage.Factbox.Page.PublicProcedure(Rec) would NOT work either.

    Seems that only fields' values are being updated while selecting another record in the main page. Everything visual only gets loaded OnPageOpen(). I also could update it OnInit().
     

  • Suggested answer
    Ahmad Subhani Profile Picture
    827 on at

    Hi,

    This is a known limitation in Business Central. FactBox field visibility works correctly only when controlled through a Boolean variable bound to the Visible property, but you must trigger the update via 

    • CurrPage.Update() 

    • OnAfterGetRecord

    • OnAfterGetCurrRecord

    of the FactBox page itself (not just the parent page) otherwise the FactBox doesn't re-render.

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the August Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 720 Super User 2026 Season 2

#2
YUN ZHU Profile Picture

YUN ZHU 436 Super User 2026 Season 2

#3
AndrewThomas81 Profile Picture

AndrewThomas81 409 Super User 2026 Season 2

Last 30 days Overall leaderboard

Featured topics

Microsoft Training Manuals

Product updates

Dynamics 365 release plans