web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Blogs / viko's NAV blog / Bug in NAV 2013 R2 preventi...

Bug in NAV 2013 R2 preventing correct execution of GETRECORD, SETSELECTIONFILTER and it's workaround

Views (10554)
viko Profile Picture viko

Yesterday I've discovered a bug in NAV 2013 R2 (I used build 7.10.37221) that results in inappropriate execution of GETRECORD and SETSELECTIONFILTER functions.

 

Problem description:

Both GETRECORD and SETSELECTIONFILTER always retrieve first record from SubPage despite other record is selected.

 

For demo of the bug I've copied Sales Order page with SubPage, removed unnecessary controls and created two actions:

- GETRECORD

- SETSELECTIONFILTER

with following code:

 

 

Both GETRECORD and SETSELECTIONFILTER retrieved first line of the document despite third one was selected. So the bug is that whichever record is selected in SubPage both functions always retrieve first record.

 

Workaround

 

After few attempts to find out what's wrong I discovered that workaround is very simple - both functions work correctly when I place any code (or even empty comment) to OnAfterGetCurrRecord() trigger of SubPage:

 

I hope this bug will be fixed soon :)



Comments

*This post is locked for comments

  • Community Member Profile Picture Community Member
    Posted at

    Thanks for the workaround, just used in in NAV2016 (bug still present)

  • Community Member Profile Picture Community Member
    Posted at

    Thank you!

  • viko Profile Picture viko
    Posted at

    Hi, as you can see I used build 37221, so I would recommend to upgrade NAV platform to this build and then apply workaround.

  • aavio Profile Picture aavio 895
    Posted at

    this solution seems to be not working always.

    Nav build 36366

    Please advise whether its fixed in any recent release.

  • Community Member Profile Picture Community Member
    Posted at

    Thanks for the advice. Workaround also works in NAV2015, where the bug is still (or again?) present.

  • X. GARONNAT Profile Picture X. GARONNAT
    Posted at

    Many thanks for this ! Help me to resolve a bug when printing/navigating in FR bank module...

    (the "bordereau" for connaisseurs...)