"The metadata object Page 0 was not found."

Bhagwan
Member Posts: 11
In My customer card i click on Balance it's showing me error " The metadata object Page 0 was not found."
In same table i have created new filed like existing Balance filed and it's working fine , but standard one is not working .
why this happening ,i am not able to found out reason, i had compile all objects and check metadata for list page 573 "Detailed Cust. Ledg. Entries".
Can anyone one give idea how to resolve this issue.
thanks in advance
In same table i have created new filed like existing Balance filed and it's working fine , but standard one is not working .
why this happening ,i am not able to found out reason, i had compile all objects and check metadata for list page 573 "Detailed Cust. Ledg. Entries".
Can anyone one give idea how to resolve this issue.
thanks in advance
0
Comments
-
in this pic "1222" caption field is new created which working fine ,but second standard one giving me error.0 -
Hi Juhl
thanks for reply ,
i restarted NST many times , and page is not missing because on same flow-filed formula my customize filed working fine only standard one get problem.0 -
check what do you have in LookupPageID and DrillDownPageID properties of table Detailed Cust. Ledg. Entry1
-
Thanks mohana for reply.
in both value is "Detailed Cust. Ledg. Entries"0 -
"Detailed Vendor Ledg. Entries"? It's wrong, it should be "Detailed Cust. Ledg. Entries"
Set "Detailed Cust. Ledg. Entries" as the lookup and drilldownpageid of the table, and just to be sure recompile "Detailed Cust. Ledg. Entries" PAGE0 -
sorry its "Detailed Cust. Ledg. Entries" only ,
still i am not able to find out why its giving this error?0 -
Could you post the flowfield formula used on your field and on the standard one too. The best would be if you export the table to text and paste here two sections with flowfieldsSlawek Guzek
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-030 -
{ 58 ; ;Balance ;Decimal ;FieldClass=FlowField;
CalcFormula=Sum("Detailed Cust. Ledg. Entry".Amount WHERE (Customer No.=FIELD(No.),
Initial Entry Global Dim. 1=FIELD(Global Dimension 1 Filter),
Initial Entry Global Dim. 2=FIELD(Global Dimension 2 Filter),
Currency Code=FIELD(Currency Filter)));
CaptionML=ENU=Balance;
Editable=No;
AutoFormatType=1;
AutoFormatExpr="Currency Code" }
{ 59 ; ;Balance (LCY) ;Decimal ;FieldClass=FlowField;
CalcFormula=Sum("Detailed Cust. Ledg. Entry"."Amount (LCY)" WHERE (Customer No.=FIELD(No.),
Initial Entry Global Dim. 1=FIELD(Global Dimension 1 Filter),
Initial Entry Global Dim. 2=FIELD(Global Dimension 2 Filter),
Currency Code=FIELD(Currency Filter)));
CaptionML=ENU=Balance (LCY);
Editable=No;
AutoFormatType=1 }
this is my custom filed
{ 50010; ;Test bal ;Decimal ;FieldClass=FlowField;
CalcFormula=Sum("Detailed Cust. Ledg. Entry".Amount WHERE (Customer No.=FIELD(No.),
Initial Entry Global Dim. 1=FIELD(Global Dimension 1 Filter),
Initial Entry Global Dim. 2=FIELD(Global Dimension 2 Filter),
Currency Code=FIELD(Currency Filter)));
Editable=No;
AutoFormatType=1;
AutoFormatExpr="Currency Code" }0 -
OK thanks.
Now if you could export your Page to text file, and include the sections defining your field, and also the standard field giving you an error on drill down.Slawek Guzek
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-030 -
Hi Slawek , thanks for help
it's solve now , its causes just because wrong page was attache in Cust. Ledger Entry table property .
thanks once again.0 -
..and your own field drill down was relying on the flowfield properties while the standard field has a section of the code/function call in OnDrillDown showing Customer Ledger Entries instead... probablySlawek Guzek
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-030 -
yes you are right when i wrote same code on my custom field drill down , i started same error on it also. than i got my issue exactly and i check all page properties properly.
thanks once again slawek..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