Question
Alternate BOM creation using API - What are people doing to work around this SPR/Gap?
Following up on the post below and MPMLink related bug:
- Community post - Alternative BOM: Cannot create view with different variation of WTPart using VersionControlHelper.service.insertNode API.
https://community.ptc.com/t5/Windchill-Ideas/Alternate-BOM-creation-using-API/idi-p/694409 - Call / SPR - https://www.ptc.com/en/support/article/CS277307
Issue reported to R&D on 19-MAY-2015 as SPR 4414456 with severity Low
This has been an issue since 2015. Don't understand how this can be low severity.
How other companies migrated in MPMLink alternate boms given this gap?

