I’m hoping someone can help in testing a bug. Support says they cannot reproduce in their version (2022.1.15) but it is happening in my version (2022.1.11). If anyone has either of these versions and can test for me, it is appreciated.
The bug is in the Kinetic UI only, both web and client. You cannot enter a Rev for a part on the fly. This is in Quote, Order, and Job. Additionally, you cannot change a Rev. Client screen in old UI works.
John,
I can confirm that I also see this issue in 2022.1.10, 2022.1.14, and 2022.2.4
It looks like the Rev dropdown is not set up to accept user-defined values. It must exist in the list, which for Part on the Fly obviously there is nothing to select.
Awesome! Thanks for your help.
One warning with POTF and Revs, they can cause future issues if the same P/N is used for another POTF. Or maybe I’m thinking of UOMs…
Either way, a POTF was entered on an order, and then later the same POTF was used with a different Rev (or UOM?) and it caused problems.
I submitted a ticket to this effect back in May 2022. They closed and gave me a problem: PRB0250509 I never looked back to see if they did anything with it. HAH! The problem record says, “not found”. That about sums it up I guess… EDIT: I found the problem ticket. It has been rejected. So, I would say this is working as designed! 
UOM is the issue if it is in a different UOM class. Rev shouldn’t be a problem.
Thank you all. I’m going to go back and ask for them to submit it to Development. Losing this ability would be a huge issue for us.
Might it have something to do with the inventory by rev functionality just introduced? 
Although Nate says he had found this back in May.
It’s just an oversight on Epicor’s part. Their ‘Part Rev Description’ component doesn’t allow custom values in the Rev combobox, but it should.
In Application Studio I added a combobox, enabled ‘Allow Custom’, and bound it to the JobHead.RevisionNum field. It works as expected.
@jkane you might be able to use this as a workaround until Epicor (hopefully) fixes this.
Is this open as a PRB then? Or?
I misunderstood support, it is already fixed in a coming release. I asked for the release. I’ll post when I get it.