Great question! Even if your app works without DrillDownPageID and LookupPageID, including them adds clarity, consistency, and better UX in Business Central.
✅ Why Use DrillDownPageID and LookupPageID?
1. LookupPageID
Specifies which page opens when users use the lookup (🔍) on a field that links to your table.
Example: When selecting "Radio Show Type" from "Radio Show", it opens the Radio Show Type List.
Benefit: Ensures users see the right lookup page with proper filtering, layout, and actions.
2. DrillDownPageID
Used when a user clicks on a field with a FlowField or drill-down capability (like quantities or balances).
Opens the page that lets them “drill into” that data.
It’s less common for simple lookup tables but critical in financial/reporting data.
---
🔍 What Happens If You Don’t Use Them?
AL tries to guess the best page to use — which may work, or may not.
You lose control over UI behavior, especially if users expect a specific experience.
Features like page customization, navigation, or data entry flows may not work as intended.
---
🔁 In Your Example:
When you set:
LookupPageID = "Radio Show Type List";
…it lets users open a proper lookup page from the "Radio Show" table and even create new records from that list.
> It connects the field to a specific page experience, rather than relying on BC’s default behavior.
---
💡 Summary:
✅ Use LookupPageID for fields with TableRelation → better control of lookup pages.
✅ Use DrillDownPageID if your table is involved in FlowFields or reporting.
🧩 They aren’t required — but skipping them is like not labeling doors in a big building: people might still get in, but it’s not great UX.
Mark below checkbox to make this answer Verified if it helps you.
