Duplicate Part, UOM Has Been Used

Upon Duplicate Part, the newly created part’s Inventory UOM and PartUOM are locked. The PartUOM is marked HasBeenUsed = true. I’m pretty sure this wasn’t the case in the recent past as I’ve done this before 25.2.16. Can anyone confirm whether this is the case in earlier versions? Why would Duplicate Part feature copy the HasBeenUsed value?

I’m not seeing that behavior. I just duplicated a part and the duplicate is showing HasBeenUsed = false and the Inventory UOM is available to change. Is it possible you’re looking at a UOM that isn’t Part-Specific?

Also not seeing that on my side.

The Inventory UOM will be greyed out if one of the part revisions is “approved”. But I just duplicated a part and the revisions DID copy, but were marked unapproved. I am able to change my Inventory UOM. If I approve a revision, it switches to readonly.

We don’t use the PartUOM conversion piece, so I can’t test that portion (as far as the HasBeenUsed bit).

Thanks for your replies.

It’s indeed a Part Specific UOM.

Revision had me thinking…there are no revisions on source part, but UsePartRev was true under Revision Tracking. Tried duplicate again without that and same behavior.

Are you both on 25.2.16?

PS - source is purchased part where UOM indeed has been used.

We are.

It appears UOMs are locked when Duplicating AUOM Parts having TrackInventoryAttributes = True. I’m pretty sure this wasn’t always the case, but could be wrong.

Further, setting that to false on the new part doesn’t unlock UOMs so you must Duplicate, set TrackInventoryAttributes=false, then duplicate the duplicate, then set TrackAttribs=true again. :roll_eyes:

Only a couple hurdles to remember to jump over. What could go wrong?!

jump fail GIF

It’s a shame. Lock-down logic is important, I get it. But it’s just a lazy one-way implementation. I mean I can’t change a UOM but I can delete the part. Oh Okay. :roll_eyes:

Wouldn’t that be hard to have options when you duplicate parts. toggles on WHAT gets duplicated. Part details vs revision details (methods) vs AUOM details, etc.

Wouldn’t be that hard for Epicor to make HasBeenUsed mean has been used. These one-way flags are poorly done. Especially with respect to AUOM.

Or to have a version where I can duplicate a list of parts and make the same changes. If you have more than 10 or 15 you need to duplicate, that gets tedious really quickly.