"The metadata object Page 0 was not found."

BhagwanBhagwan 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

Comments

  • BhagwanBhagwan Member Posts: 11
    td2xtnwcdre3.png

    in this pic "1222" caption field is new created which working fine ,but second standard one giving me error.
  • JuhlJuhl Member Posts: 724
    Check that the fields are pointing the same page.
    Restart NST.

    Page 0 Metadata error is normally related to missing page.
    Follow me on my blog juhl.blog
  • BhagwanBhagwan Member Posts: 11
    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.
  • JuhlJuhl Member Posts: 724
    Check if there are customizations or personalizations, and delete these from the tables.
    Follow me on my blog juhl.blog
  • mohana_cse06mohana_cse06 Member Posts: 5,504
    check what do you have in LookupPageID and DrillDownPageID properties of table Detailed Cust. Ledg. Entry
  • BhagwanBhagwan Member Posts: 11
    edited 2017-10-31
    Thanks mohana for reply.
    in both value is "Detailed Cust. Ledg. Entries"
  • BeliasBelias Member Posts: 2,998
    "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" PAGE
    -Mirko-
    "Never memorize what you can easily find in a book".....Or Mibuso
    My Blog
  • BhagwanBhagwan Member Posts: 11
    edited 2017-10-31
    sorry its "Detailed Cust. Ledg. Entries" only ,
    still i am not able to find out why its giving this error?
  • Slawek_GuzekSlawek_Guzek Member Posts: 1,690
    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 flowfields
    Slawek Guzek
    Dynamics NAV, MS SQL Server, Wherescape RED;
    PRINCE2 Practitioner - License GR657010572SG
    GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-03
  • BhagwanBhagwan Member Posts: 11
    { 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" }
  • Slawek_GuzekSlawek_Guzek Member Posts: 1,690
    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-03
  • BhagwanBhagwan Member Posts: 11
    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.
  • Slawek_GuzekSlawek_Guzek Member Posts: 1,690
    ..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... probably :)
    Slawek Guzek
    Dynamics NAV, MS SQL Server, Wherescape RED;
    PRINCE2 Practitioner - License GR657010572SG
    GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-03
  • BhagwanBhagwan Member Posts: 11
    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.. :)
Sign In or Register to comment.