I admit I've found this question asked before (#2811), but I'm asking again hoping something has changed since 5.2.
What is the recommended approach to adding additional properties/columns (beyond two PKs) to a link table created by a many-to-many navigation collection?
I have a pretty simple use case: an entity/table of Parts and an entity/table of Assemblies. The link table defines which parts go to an assembly (bill of materials), but I also need to include how many of each part are in the assembly. The obvious solution is to add a "Quantity" column to the table joining PartId and AssemblyId, but what's not obvious is how to do that via Suite, or via customization that isn't wiped out by a later Suite-initiated code generation.
I understand the availability of Object Extensions to extend objects managed by modules, but as the Object Extensions page points out, this shouldn't be necessary with my own classes.
Are Object Extensions still the recommended approach to this? Can you provide a complete example of using Object Extensions in this application? I honestly find it hard to believe this isn't a standard feature at this point. At the very least, a method is needed to prevent the overwriting of CRUD object customizations when, for example, a new property is added. As it stands now, it seems I have one chance to get an entity perfect in Suite before I customize and can no longer touch it.