Sage 100

Has anyone ever asked to delete a slew of /Misc codes? Can't do it with delete utility. Any one have any ideas?

Here is 1 answer. Ask your script person to script it (or your M/D contact to create a utility). You can export the misc codes to Excel then remove the ones you want to keep. Then a button script in Misc Item Maintenance can read the XLSX or CSV and delete the /Misc codes in the system. Alternatively you can put the delete list in a UDT and the script can get to it that way.

I would guess this would not work if there is history. Looks like purging /Misc codes history is also part of the itme history purge.

You're right on both fronts KatSix! And since running Purge Item History is done by specifying a FY as opposed to misc item code range, it would purge history for items you want to keep as well (oops). The M/D approaches I would take myself for this type of situation would be either: * Modify the Purge Item History utility to allow also selecting by misc code range. While we're at it, we can delete the same misc codes from Misc Item Maint too (2 birds). * Create a button similar to script idea above where we get misc code list from a CSV or UDT but it would be able to physically delete the misc code and optionally delete it's history.

Sometimes hiding them is enough... disable the Allow use in checkboxes.

That's even better Kevin!

So I tested in v2017 to make sure I could import and change those fields to N. It will not let all those check boxes be N at least one has to be checked. Looks like I may have to see what the client has. Maybe they can all be AR and change the lookup to not show those or vice versa. May be some they use in PO also.

What a pain in the butt. Client has 4,203 Misc Codes (in PO) that they no longer want available to users because we're now using the I/M module - but they do want to retain Misc Codes history. And I realized you can't just disable a 'Use in __' field if no other 'Use in __' field is enabled as @KellySappington also stated. But this client does not use A/R, S/O or B/M. So what I was able to do was temporarily create A/R data so that I could enable (via VI) the 'Use in AR' setting and disable the 'Use in PO' setting. Then I removed the A/R data which luckily still left the 'Use in PO' setting as disabled. Lastly before doing anything else, I exited Sage to avoid any A/R-related errors that I initial got during testing.