Quantcast
Channel: NAV Three Tier — mibuso.com
Viewing all articles
Browse latest Browse all 10032

"Restricted Record" table NAV 2017

$
0
0
In the past, up to and including Navision 2015, I have had reports that did some pre-processing in Temporary Tables.

This included lines like TempResults.DELETEALL(FALSE);

And it was never an issue before.

Now suddenly in NAV2017 it is a problem because when I call the DELETEALL, the system automatically tries to delete records (even though there is none) from Table 1550 - "Restricted Record". The problem is one is not allowed modify the database with this report.

Changing the Transaction type property of the entire report from "Browse" to "Update" or "UpdateNoLocks" makes the problem go away of course, as now I am allowing the report to be modifying the real database.

But I would like to know why this is happening, can it be stopped, or are my only options to change the report?

OR would it be ok to change the Navision standard code line that does a DELETEALL(TRUE) on Table 1550 to IF NOT ISEMPTY THEN DELETEALL(TRUE) so the new code never actually runs?

What is this new trigger? Where is it being triggered in the first place? And is it another "bug" that MS are allowing it to be triggered on Temporary Table Variables? It looks like a feature that only makes any sense on REAL tables, not temporary ones.

Viewing all articles
Browse latest Browse all 10032

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>