RTC, Standard Export to Excel resulted faulty output

cwhmy
cwhmy Member Posts: 24
in NAV Three Tier
Hi Experts,

From a Page of 15 rows records with multiple fields, through clicking the Standard Export to Excel button (upper left the "Print & Send" -> "Microsoft Excel") exported the Excel file,

in one machine running Nav7 exported without seeing one of important Fields (not printed/exported). e.g. Name field of a group of customer is disappeared, but other fields are exported.

in another machine running Nav601 exported with wrong name, first name in the rows is carrying down to every subsequent rows. e.g. 15 rows of records, on the Name field, the output is Peter for all 15 rows.


Important Note: the Name field was set in a function being called under DataCaptionExpr property of the page.


Is this a known issue? Anything you would suggest? TQ

Answers

  • Kishorm
    Kishorm Member Posts: 921
    edited 2016-10-25
    You should call the function in the OnAfterGetCurrRecord() OnAfterGetRecord() instead of DataCaptionExpr.

    DataCaptionExpr is used to dynamically get different captions for a field not different values for a field.
  • cwhmy
    cwhmy Member Posts: 24
    Hi Krishorm, it doesn't help for any change the output of exported Excel
  • Kishorm
    Kishorm Member Posts: 921
    Sorry, I meant OnAfterGetRecord()
  • cwhmy
    cwhmy Member Posts: 24
    edited 2016-10-26
    Thanks but it doesn't either.

    Found out something here through a series of quick attempts:
    1. Nav700 paired with Excel 2013 => Passed. Perfect Output
    2. Nav700 paired with Excel 2016 => Failed. Name field is disappeared/missing

    3. Nav800 paired with Excel 2013 => Failed. first name in the rows is carrying down to every subsequent rows.
    4. Nav800 paired with Excel 2016 => Failed. "Microsoft Dynamics NAV Excel Add-in encountered an internal error ...... bla bla"

    side note: Nav602 paired with Excel 2013 works like a charm too. => Passed. Perfect Output.


    It looks like the built in feature is not so supported.

    Besides manually construct it heavyly, anyone any other idea? TQ

Categories