Unable to select layout! Cannot build the page 9660, the metadata object was not found.

Celicni
Member Posts: 10
Hello all. I ran across a very weird problem that was bugging me, and after finding the solution I wanted to share it with everyone, it may help someone else.
On production environment, client was unable to "select layout", whether from the "report layout selection" page, or by running the report directly and choosing layout from there. Nothing would happen upon clicking the button.
I wanted to manually open the "Report Layouts" page by editing the URL to the page (9660), but upon doing that I was presented with this error:

Cannot build the page 9660, the metadata object was not found.
That made no sense to me, it's a Microsoft base (or system or whatever) application page, how can it be missing?
Well, as it turns out, it most definitely is NOT part of either system, system application, or base application, but rather part of an "invisible" extension called "_Exclude_ReportLayouts".
This extension, as well as a couple others, need to be installed upon doing an upgrade from a lower version. But they are "invisible" and cannot be seen in the "extension management" page and there is pretty much no indication that they're missing.
Turns out that the extension management page has a filter to exclude these specific extensions.
Upon installing the _Exclude_ReportLayouts extension, everything is working properly.
On production environment, client was unable to "select layout", whether from the "report layout selection" page, or by running the report directly and choosing layout from there. Nothing would happen upon clicking the button.
I wanted to manually open the "Report Layouts" page by editing the URL to the page (9660), but upon doing that I was presented with this error:

Cannot build the page 9660, the metadata object was not found.
That made no sense to me, it's a Microsoft base (or system or whatever) application page, how can it be missing?
Well, as it turns out, it most definitely is NOT part of either system, system application, or base application, but rather part of an "invisible" extension called "_Exclude_ReportLayouts".
This extension, as well as a couple others, need to be installed upon doing an upgrade from a lower version. But they are "invisible" and cannot be seen in the "extension management" page and there is pretty much no indication that they're missing.
Turns out that the extension management page has a filter to exclude these specific extensions.
Upon installing the _Exclude_ReportLayouts extension, everything is working properly.
0
Answers
-
Use schema synchronization as force sync in launch.json.0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions