Phantom WO error with Advanced BOMs Hey, all. I h...
# suitescript
m
Phantom WO error with Advanced BOMs Hey, all. I have a script that creates a phantom WOs. It has worked without issue while using legacy BOMs. However, we just transitioned to Advanced BOMs and some assembly items are causing an error in the script. Upon further investigation there are sub-assemblies w/o a Revision record - this appears to be the root cause. However, if I create the phantom wo in the UI with the same parent assembly it works just fine. Any thoughts on why the missing revision record would not be a problem in the UI and how I might work around it in the script? NOTE: The team wants to be able to have Assemblies w/o Revision records, so hoping "create the missing revision record" isn't the only solution.
For anyone that may find themselves in a similar situation, this appears to be one of those order-of-field-set-is-important peculiarities of SuiteScript. To get the WO to create like it did before I... • Saved the current value of BOM Revision to a variable • Set the BOM Revision field to null • Set the Sub-assemblies Phantom to true • Set the BOM Revision field back to original value BOM successfully exploded all children is it did prior to Advanced BOMs.