When my kids have visitors to the house almost always, without fail, they show them our laundry room. It’s sort of their way of saying “See how crazy my mom is!” Call it an idiosyncrasy, an obsession, or whatever you want, but I like things orderly and in their place, and I simply REFUSE to sort anyone else’s dirty laundry!
Our laundry room has, not one, not two, but five laundry hampers. Each one has a laminated, color coded sign hanging from it to describe the clothing that goes into the hamper: Dark Colors, Bright Colors, Bleachable Whites, Delicates, and Jeans. There’s a place for everything and everything goes in its place. Because of that, my laundry room is neat and efficient. I can start a load of laundry in less than a minute.
I also REFUSE to sort through a cabinet full of items in my bathroom. There is a bin for everything – Skin Care, Hair Care, First Aid, Dental, Cleaning Supplies - you get the picture. And yes, the bins are labeled (I love my label maker!).
As NAV developers, we have to learn to say “I REFUSE” to a few things for the sake of maintaining an efficient and orderly database. When adding data to a database, you have to think long term. Once data is there, it’s usually not removed. Databases change hands, security measures evolve - or even dissolve, and what is in your database can become a threat to your company.
I’ve come up with a short list of things a NAV developer should refuse to store in a NAV database. This is by no means an all-inclusive list, and I encourage you to add to the list (see that comment box below?).
Things A NAV Developer Should Refuse to Store in NAV:
Go ahead…say it with me: I REFUSE TO TRASH MY DATABASE! Sometimes the developer has to be the keeper of the database and police how it is used. Otherwise, our happy little playground could turn into an unorganized mess…much like the huge bag of laundry my son brings home from college about once a month. That’s right, once a month. Lord, have mercy!
Use the comments box below to tell us about data issues you’ve seen in NAV databases. What have you seen that should not have been in the database, and why?
Other Microsoft Sites
I'm a Customer
I'm a Partner
Follow Microsoft Dynamics