It looks like you're new here. Sign in or register to get started.
ara3n wrote: I wouldn't think so. Why do you think it should be a bug?
Savatage wrote: Perhaps someone set the InitValue property of the field in your Ver 4 to JOB, but didn't do Ver 5? The field in the table has a property InitValue - if it bugs you, you cold change it.
Answers
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
Because it a bit strange when you insert a job, that right away the status is Order.
In 4.0 the status is planning after inserting a new job.
Tino Ruijs
Microsoft Dynamics NAV specialist
The field in the table has a property InitValue - if it bugs you, you cold change it.
http://www.BiloBeauty.com
http://www.autismspeaks.org
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
I've checked it in CRONUS 4.0 and 5.0.
And already made the change in 5.0.
No big deal, but I found it strange.
Thanks!
Tino Ruijs
Microsoft Dynamics NAV specialist