Hi Steven
Apologies, this was stuck in my draft folder, wondered why I hadn't heard back!
Thanks as always
Pretty much all you've suggested below is in place, the link from SR is more about the business process decision to check the box (or not) at the SR stage, this flows through to WO and then ultimately the PO. That said, the decision can be made/changed downstream of the SR or the WO so I need the attribute to exist on all three objects and thus the crossover. Yep used the TICKET2WO crossover for the SR to WO, there isn't an OOTB box crossover WO2POLINE so I've had to create one (wonum=:refwo and siteid=:siteid), I'd expect the crossover to just work.
The use case here is to actually trigger an automated GL Account code change on the PRLINE/POLINE based on the YORN value so the crossover should probably go Workorder to PR Line to PO Line (during reorder routine)
Hope this makes sense
Cheers
Peter