Filters did not apply on "Date" virtual table

Isaland

Hello all,

Do you know why it can be possible?
The Date virtual table is ignoring filters via code \ page \ report.

RockWithNAV

Can you show us the code that you have written. Reopen this Page and try to put Filter again and check please.

Slawek_Guzek

works for me:

Isaland

@RockWithNAV

DateRec.SETRANGE("Period Type",DateRec."Period Type"::Week);
DateRec.SETFILTER("Period Start",'<=%1',WORKDATE);
DateRec.FINDLAST;

@Slawek_Guzek

It also work for my machine. Restart NAV server helps, but after some time it will occure again.

Slawek_Guzek

If it works and stops working after some time then it is likely some NST bug. If restarting the NST helps it only confirms that hypothesis.

You could try SELECTLATESTVERSION before SETRANGE, to try to workaround the problem. The SELECTLATESTVERSION will clear session buffers and reduce memory pressure, which might help if problems are somehow related to memory.

Regardleds the SELECTLATESTVERSION helps or not try the newest CU, and report the bug to Microsoft

Isaland

@Slawek_Guzek thank you for idea with SELECTLATESTVERSION. Will try it. Of course we will send report to microsoft about it.

Isaland

@Slawek_Guzek SELECTLATESTVERSION did not help. I will update this topic after Microsoft respond.

Slawek_Guzek

Thanks for the feedback. I was curious if it could help.

Looking at the code you posted above - is this related anyhow to the test page you've shown? I mean is this just a snippet of the code used on the test page to filter someting, or you have build the page is just to demonstrate the problem, and the sample code posted later is from another place in the system?

Isaland

@Slawek_Guzek I built the page just to check issue. The code part from another piece of the system.

AntHillMob

Can I ask what version/cumulative update you are using?

I have seen this issue. It appears to apply to all virtual tables , not just the date table and is a NST bug. Restarting the NST resolves the issue. The issue appears to be caused by making objects changes and therefore I have only seen this in a development environment and not on any production environments.