Bob or anyone else listening...
My rant was only for this one Manu, or others that have the 2k limit. The EZMatch process works great for others and is one of the best reasons to use Si5. For the first time in years ALL our pricing data is up to date. In fact if a vendor does not provide Excel or EZip pricing we let them know they will not be receiving any future orders.
Also, by adding a "Date Last Updated" field (CustProp10) to the Excel (csv) Data, we now know the date of the pricing document when the item was last updated. This allows our team to trust the pricing.
Before each price update we set ALL Items for that Manu to "Unapproved". We then run EZMatch with the csv Items set to Approved and the date field as mentioned above. Now the user can trust the pricing since it was matched with an automated process and the Date tells them the date of the pricing document received from the Manu.
Now I just want to get access to all the data you and your team have worked hard to produce. I was a little unfair in my post. I let my frustration get the better of me.
Two things would make this work.
1) Eliminate the 2k requirement
2) Allow the user to choose the Unique Key field(s) for matching (EzMatch). This way I could match Price data on SKU if needed and D-Tools data on Model. Allow the user to chose either Manu-Model or Manu-SKU for updates against the MasterTable or the D-Tools Data.
Then for vendors such as Extron, AMX, Crestron, Shure, ... I could get both price updates and D-Tools data.
I know it is a "hack" but it would solve a LOT of issues.
-ch
|