Products not linked to MMPD - D-Tools Forum

Bezy9530 · 01-31-2011, 07:26 PM

I would like to add a colum to d-tools that shows me if a product in the project already resides in our d-tools database of products we carry
. What's happening is...some of our products are getting altered in the project directly, and not in the MMPD. I would like a column that shows if i product in a project is linked to a product in the MMPD, or if it is kinda just floating in that particular project.
For instance, if we have a model "2000 TV" in our MMPD, and the client wants a "3000 TV", but that's not in our database, we will add the "2000 TV," and just rename it in that particular project "3000 TV" and change the price. At that point, it is really no longer linked to anything in our MMPD.

fryeguy · 01-31-2011, 09:28 PM

When an item is added to a project from MMPD and then modified in the project, a prompt should appear asking if you would like to update the product in MMPD.
If you change the Model, as you suggest, from "2000 TV" to "3000 TV" MMPD will see this as a new product if you allow the update.

**Dave Kirn** · 01-31-2011, 10:40 PM

OK, so maybe this is just because part of our business is product database work with our DataPro data subscription, but this statement just scares me.

Where I see the issue is that there seems to be no process in place to manage who has access to adding products to the database (which is the most important piece of your overall D-Tools environment). My suggestion has always been to have one individual that is responsible for managing the database - I know that this is not always the most convenient process, but it is the one with the least amount of headaches and problems.

As far as a method to avoid having the problems that you are experiencing here is the process that we recommend. When having just one person that is responsible for your database (database admin) there will be times that a proposal needs to be completed and for some reason it is not an option to have the database admin add the product to the database. Either use the Generic product data that is part of D-Tools standard database or create your own Generic products. If a new product needs to be added then simply add a Generic product that is close to the new product (ex Generic 46" LCD for a Sony 46" LCD). Once the database admin is able to add the product, they can simply search for all products with the manufacturer of "Generic" and then using the Replace function replace that product with the newly added product.

Make sense?

fryeguy · 01-31-2011, 11:05 PM

It used to scare me too. I was a strong and almost unbending proponent of the Database Admin model of managing data. This lasted two weeks once we actually had more than two people actively working in D-Tools. For most small companies there is little value in limiting data manipulation to a single user because they only have a single user.
But there is still hope for anyone offended by my cavalier, gun slinging approach to add items to the database. If the thought of recklessly clicking YES on the "Update Product in MasterTable" Dialog Box makes you sweat, fear not! A user can easily be limited from adding new items to the shared MasterTable by limiting a few Permissions. To allow a user to sync his database only downstream, that is only receive new data from the server but not send data to the server, simply remove these permissions:

LANSync Administrator
Add/Edit Data
Delete Data

With this setup a user can still manipulate local data but not overwrite server data when syncing. I understand this does not work for everyone and it does not specifically identify reconciliation of these new items with other users or the server MasterTable.

All that said, I am still an advocate for implementing D-Tools in an environment with good control of data. The benefits are worthwhile. The reality is that locking down data doesn't work for every company.

**Dave Kirn** · 01-31-2011, 11:45 PM

Yes Permission settings can prevent changes to the MasterTable on the server and make sure that the overall "system" database is not changed. However there still will need to be a process in place to handle the products that are just added for proposal use.

I am sure that your process works good for you and within your company, I firmly stand behind the thought that the number of users that have the ability to add/modify/delete data should be limited to one or two people (depending on the size of the company). I have yet to see a company where each user was allowed full control of the data where issues have not arisen. Especially when it comes to keeping pricing updated, who is responsible?

Changing to a process with a single Data Admin (while may seem impossible at first since it is a change) it is very easy to implement and has been done with many of our clients successfully.

fryeguy · 02-01-2011, 12:12 AM

Quote:

However there still will need to be a process in place to handle the products that are just added for proposal use.

No doubt that this is not an ideal solution.

Quote:

Changing to a process with a single Data Admin (while may seem impossible at first since it is a change) it is very easy to implement and has been done with many of our clients successfully.

I can't agree more that a single Data Admin is the way to go. If this model worked for my company I would lock down the database today!

**Dave Kirn** · 02-01-2011, 04:55 PM

Just come over to the dark side, it will be OK

sadmemories20 · 04-25-2011, 02:43 AM

My suggestion has always been to have one individual that is responsible for managing the database - I know that this is not always the most convenient process, but it is the one with the least amount of headaches and problems.

timw · 04-29-2011, 05:42 PM

FYI, In the latest release of SI5 editing a product model # DOES NOT create a newly renamed product, it updates the existing product. You have to first edit the product, click "no" on the update master table prompt, THEN right click the locally edited product and select update to master table.

MelissaDaisy99 · 06-17-2011, 08:40 AM

I have yet to see a company where each user was allowed full control of the data where issues have not arisen. Especially when it comes to keeping pricing updated, who is responsible?