Hi All,
I am working to change the tables codes and code units to stop sales-lines date fields; such as shipment date, Planned Shipment Date, etc... being populated/changed at all by sale header change(s) or sale lines being created or changed.
Will my change(s) create any problems or do I have anything to concern or take care to ensure no advert change(s) to system or business validation?
Thanks in advance
0
Comments
Thanks.
Is there some particular value you're trying to save like an entry date or something?
http://www.BiloBeauty.com
http://www.autismspeaks.org
Why?
All I can do is answer your original question:
YES!
I do suggest you let us know the real reason they shouldn't be filled in. "It's the way our business runs" is about as helpful to the problem as someone saying "Navision is broken. Fix it.". Without an understanding of the issue it's very difficult to provide an answer.
Good luck.
My Blog - nav.education
http://www.BiloBeauty.com
http://www.autismspeaks.org
My company would like to have those Shipment Date, Planned Shippment Date, Promised Shipment Date to have the initial value as blank when the order line first entered, or after the partial shipment was posted to the order line. Another thing, per the sytem we have acquired, these 3 fields always been updated to have the same value, if any change(s) made to either Shipment Date or Promise Shipment Date. Are these updates standard per Navision?
Thanks again for your response.
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
Alex is correct. Again, you didn't provide a business reason for needing the change. Just that you don't want the fields filled in for some reason. Go to your NAV Partner, talk to them about what you want to do. If they are a good partner they will set you up with some training. If they aren't, they will just blindly make the change and you will probably be up a creek.
My Blog - nav.education
I have known these changes, if done, must be meticulously checked and double-checked to verify and be sure the system business logic not been broken, shortchanged, or crippled by any manner. Otherwise, I would be up to my neck in my own... stuff!
I hoped that someone would have done these changes themselves so I could learn from their experiences or tips to cut short the learning curves and the time to go over to those few million character codes/programs from at least 2 tables and 10 code units (the byte size of the code and definition of the Sales Line table alone is roughly 500,000 characters; more than 32000 lines) to figure out what has to be done.
Thanks all for your response.