Skip to main content

Extend CardPageId on List and ListPart Pages in Business Central 2025.

Hi,

Introduction

One of the most highly requested features in Business Central is finally here! Microsoft has introduced the ability to extend CardPageId on List and ListPart pages in Business Central 2025. This enhancement allows developers to modify which Card Page is displayed when a user interacts with list-based pages, enabling greater customization and flexibility.

In this blog, we will explore the business value, feature details, benefits, and implementation of this new functionality.

Business Value

Previously, CardPageId was a non-extensible property, meaning that developers could not modify the Card Page association for a list or listpart page through a PageExtension. This limitation caused challenges for many Business Central implementations, especially when:

  • A list did not have an associated Card Page, but developers wanted to add one.

  • The existing Card Page did not meet business requirements, and a replacement was needed.

With the new extensible CardPageId feature, developers can now override or define a custom Card Page, improving the user experience and workflow efficiency.

Feature Details

With Business Central 2025, developers can now modify the CardPageId on List and ListPart pages through a PageExtension.

🔹 How It Works:

  • If a base page has a CardPageId, a PageExtension can now override it.

  • If a list does not have a CardPageId, you can add one via a PageExtension.

  • If multiple PageExtensions modify the same property, the last applied extension takes effect.

  • Per-tenant extensions are applied after AppSource apps, meaning custom implementations can override AppSource modifications if needed.

How to Extend CardPageId in AL

💡 If the "Payment Terms" page didn’t have a Card Page, this extension adds one.

Benefits of Extending CardPageId

Enhances Customization – Developers can now modify Card Pages to fit business needs. 

Improves User Experience – Users can access relevant Card Pages when interacting with list views. 

Overrides Unwanted Defaults – If the default Card Page is not suitable, it can be replaced. 

Resolves Race Conditions – Per-tenant extensions allow fine-tuning even when multiple AppSource apps modify the same property.

Availability

This feature will be available in Business Central 2025 Wave 1 (April 2025) for all developers, admins, and makers.

Conclusion

The ability to extend CardPageId is a long-awaited feature that brings more control and flexibility to Business Central development. Whether you need to override a default Card Page or add a missing one, this update will significantly improve customization in list-based pages.

💡 What do you think about this new feature? Share your thoughts in the comments below or on our social media!

📌 Subscribe for more Business Central updates and tutorials! ðŸš€
https://youtube.com/c/sauravdhyani

#BusinessCentral #ALDevelopment #MicrosoftAL #D365BC #BusinessCentral2025 #MicrosoftDynamics

 Regards,
 Saurav Dhyani

Comments

Popular posts from this blog

Microsoft Dynamics NAV 2016 - How to Configure Phone Client.

Hi All, In this article we will discuss how we can connect Microsoft Dynamics NAV 2016 with New Client Launched i.e. Phone Client. This Article Contain Steps for a Android Phone as I have Only Android Phone. I am doing it having all tiers on my windows 8 machine, steps remain same for multiple servers but issues might be different. What we Need (Other what we discuss in this article) -  The Service Tier should be on Public IP . Some of the Data-card does not Provide you Public IP. check it for sure.

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.

🚀 Exploring Vibe Coding with GitHub Copilot for Business Central.

Hi All, In a recent #BCOpenDiscussion session, we delved into the fascinating concept of Vibe Coding —a new way of building software where developers collaborate with AI (like GitHub Copilot) to co-create solutions.  The session covered practical setup, how AI understands context, and even touched on Microsoft's new Model Context Protocol (MCP) integration for enhanced learning. Let’s break down the journey, step by step.