too many UOM Classes
it becomes increasingly difficult/unreasonable to keep adding more and more UOM classes when a large majority of them only contain one or two UOM's. The list of UOM classes is getting quite large. It would be more helpful to have another choice for UOM's that are needed but will not necessarily be used for any conversions.
One possible idea being a UOM class that can be marked/forced to be unconvertable . . . a Misc. UOM Class.
pH is a good example of a UOM class that has to be created that for all practical purposes only has one UOM and would never be converted to anything else.
We strive to provide a basic set of UOM classes that we felt would be useful for our general customer base. We also understand that each user has different needs, which is why users can provide their onw UOM class based on their needs. This request seems to fit that model in that you can add a UOM class for your specific needs.
Roger Palmen commented
This makes a lot of sense. I frequenly create UoMs with only one Unit in the Class, without requiring conversion, just to make the unit explicit and avoid confusion.
This might also help to create UoMs that are inherently not suited for conversion, like /month or /year units.