Let me preface this by saying: I've only been using Dynamics for a couple months, and in a very limited scope. Most people at my company have been using it for much longer, but in a similarly limited scope. So pardon any stupid questions I may ask.
My problem is this: when I have drafted up a sales order, I can put on each line item the product number, description, the price extended to our customer, the cost from our vendor, etc. When I go to Actions --> Purchase, and generate a new Purchase Order, a few problems pop up.
1) When two or more line items have the same product number, they are automatically merged, and it seems that Dynamics picks at random which one to keep the description, pricing, etc, from. We often deal with products that have VERY long model numbers that don't fit entirely in the item number line. In these cases, we'll split it and put the first part in the item number, and the second part in the description (since it will print out in a readable manner that way), but if the first half is the same on two items, and the second half differs, Dynamics will ignore this and merge them anyway. For example, if one product number is 0123456789ABCDE and another is 0123456789FGHIJ, I can split them up as "0123456789" "ABCDE" and "0123456789_" "FGHIJ", using an asterisk or a period or a dash or anything else to trick Dynamics into thinking they are two different numbers. While this does work, it seems like having to jump through hoops to get the program to work correctly is counterintuitive, and there is probably a way to get it to do what I want that I'm just not seeing.
2) When a Purchase Order is generated, our cost is either pulled from the last time we ordered an identical item, or is set to $0.00. We want the cost on the Purchase Order to match the unit cost from our Sales Order, and have to manually enter this value every time. Is there a way to get this to pull from the Sales Order's unit cost, instead of from the Purchase Order history?
Thanks in advance, if anyone can help. Let me know if you need more details, since I'm sure there are parts I wasn't entirely clear about.
-Dan
