An option to remove records from Epicor that are transactional would be awesome. Old employees that clog up the search. Parts that were entered poorly and you never want to see again, but have been used. Etc etc.
Agreed - if we mark it as Inactive, then it should not show up. If we want it to show up for a few minutes in order to use it again, we can make it active.
Historical reports would need the values, but others would not, so Iām torn on how to best implement but Iād like it to apply to BAQs somehow. Not sure if should be at the system level like Territory security, or optional inside BAQs (like the multi company option, just include another checkbox for Inactive valuesā¦)
There are a bunch of open problems reporting for this.
It looks like this is your best option to try to escalate PRB0155013
It has been accepted by dev and has a moderate urgency. Resolution have been updated to: 10.TBD
You will need to be logged into Epicare for those links to work
Somewhat related, Iāve recently had requests to clone LIVE to TEST but remove ALL transactions (keeping only the setup)
1 Like
We DMTās in all our parts from V8, into E10, then were going to remove the unwanted ones. But we (and I mean āIā) inadvertantly updated the costs on all the part records. This created an ADJ-CST part tran record for each part, and thus sealed our fate into having those parts for ever in our system 
We did set them all as Inactive. But it would be nice to purge them, as they created no GL costs (all the parts had 0 QOH so so no GL trans). And if those Part Trans were ābacked outā, I could delete the parts.
If I run a query, I can find over 4,000 parts (we only have about 6,000 in total) with exact one PartTran record (the previously mentioned ADJ-CST).
A good use case for my between fix Former Employees - #4 by jgiese.wci we have a remove on part as well works the same way just different method
Iāve added UD fields (typically named AllowUse_c) to tables that donāt have an āInactiveā field. Like ProductGroup and PartClass. Then use customizations or a BPM on the GetList, to keep them from showing in all the various forms (Part Entry, POās, AR Invoices, etc ā¦)
2 Likes
And the opposite would be valuable too, keeping all the transactions, but leaving the setup in place.