MMPD Data Sync Best Practices - Page 2 - D-Tools Forum

JoseM · 10-25-2009, 05:59 AM

Originally Posted by Ryan Brown

Hey guys it is my understanding that items marked unapproved on a local machine do not sync off that machine to the server, they remain local only. The idea being that a db manager keeps it local until he's ready to send it out to everyone to use.

Can anyone confirm?

Christian, maybe use a Keyword1 = Unapproved or something. This can be easily filtered in the Product Grid (to locate these items and verify the data) and should not affect other areas of the software. Just a though, haven't fully thought it through. It's Saturday I need to get off here!

Ryan - That is correct, items marked as unapproved in the MMPD will not be included during the LANSync synchronization with the server or other clients.

You can still use unapproved items in the proposal on the local machine. When creating a proposal using the add product tool, you will see a small check box that allows you to display those unapproved items for that particular proposal.

**Dave Kirn** · 10-25-2009, 11:09 PM

Ryan might be correct on this, when I confirmed that "unapproved" items could be added to a project I only verified it on the same machine that the item was listed as "unapproved". I will give it a try on another machine and report back.

Nice catch Ryan, did not think about looking to see if the unapproved item synced with the server.

**Dave Kirn** · 10-25-2009, 11:22 PM

Well I did not see Jose's post until now, but I have checked this and that is correct that the item(s) that would be marked as "unapproved" will not sync

ChristianB · 10-26-2009, 08:42 AM

Riiight. So, all good suggestions on how this can be resolved is welcome. Maybe have them to use a generic item and rename it within the project?

**Dave Kirn** · 10-26-2009, 03:52 PM

It really will depend on what type of equipment that is needed.

Example
We recommend to dealers that they create a "generic" line of products under their company name for items that might not be completely specified at time of proposal. For example a tilting wall mount for a flat screen display - items like this tend to be offered under specials so instead of specing a Sanus mount and then later changing to a SnapAV mount we suggest that the dealer create a item with their company name as the manufacturer and a generic model number and use that on their proposals. Same concept can be used with alot of different products.

I would be careful not to have them change the description of a generic part to match a part that needs to be added - that just seems like a source for problems.

**Kevin Mikelonis** · 10-26-2009, 04:13 PM

Dave's suggesstion is indeed a good practice and can be further bolstered by using the SKU field to specify the MFG and MODEL of your preferred 'go-to' item.

It is importatnt to consider the technical knowledgebase of the back office staff in your company that may be asked to process orders off the project data, in which case the go-to item in the SKU field can guide that staffer.

**Dave Kirn** · 10-29-2009, 02:15 AM

Kevin's suggestion is great - it would definately be a benefit for non-technical staff that might be ordering product.

For the record I guess that makes +1 for Kevin

fryeguy · 11-16-2009, 11:54 PM

so back to data syncing, are the "sole data manager" environments limiting Add/Edit Data & Delete Data permissions for other users? any other permission limitations related to this?

How does this look for you guys in action? Everyone can sync but only the data manager can Add/Edit Data & Delete Data? Is it that simple?

**Dave Kirn** · 11-17-2009, 04:16 PM

Fry -

As far as permissions I generally restrict the following:

1. Add/Edit Data
2. Delete Data
3. LANSync Administrator
4. Data Administration Page

Basically every user can sync to the LANSync Server to get updates. The only person who can make changes is the D-Tools Database Administrator

ChristianB · 11-17-2009, 07:56 PM

Btw: how does the master table what data to sync and not? If I do a lot of updates in the product database, sync it and then one of my collegues who hasn't been logged on for 3 weeks syncs his? The data entrys for those products will be different. Does each product get a datestamp that tells each client when it was last modified?