Problem,
in production journal when i am posting output and consumption it prompt me GL entry locking but i am seeing ILE created. what can be reason?
i have checked all commit statement in related CU all is well.
Problem,
in production journal when i am posting output and consumption it prompt me GL entry locking but i am seeing ILE created. what can be reason?
Just add sometable.consistent(false) before calling posting routlines and sometable.consistent(true) after.
It's very simple way to protect you'r code from commit statements (or quickly find it).
Answers
2) Does it means that there are some commits between start of the process and the timeout?
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
It's very simple way to protect you'r code from commit statements (or quickly find it).
Nav, T-SQL.