Is there an issue with having a WOIssueRecord for each component on a workorder

AI generated answer (using internal Slack threads):

Based on the conversations provided, there doesn't seem to be a direct discussion about having a WOIssueRecord for each component on a work order. However, there are several discussions about creating a Work Order Issue from a Work Order, and the challenges faced when dealing with the Components sublist and the Inventory Detail subrecord. From the discussions, it can be inferred that creating a Work Order Issue from a Work Order is possible using

record.transform()

. However, dealing with the Components sublist and the Inventory Detail subrecord can be challenging. One user shared a code snippet on how to handle this, but it was noted that the

insertLine

method might not be necessary for the 'inventoryassignment' sublist. It's also important to note that adding new components to the Work Order Issue might not be possible, both in the UI and via scripting. This is because NetSuite typically doesn't allow adding items that are not on the original Work Order. In conclusion, while there's no direct discussion about having a WOIssueRecord for each component on a work order, the conversations suggest that it's possible to create a Work Order Issue from a Work Order and handle the Components sublist and the Inventory Detail subrecord. However, adding new components to the Work Order Issue might not be possible. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******