Related Record enhancement

[Jfeger310]

would be awesome to define the record type of the related object record we want to set in the table and in creating new. This could allow for using a single object multiple times thoughout an application, and controll it by record type.

[Jfeger310]

This has been added to stl, by BP and a new custom field on ref app if you want to look at it. passing a json string, of object and api of lookup field on targeted object

[effordDev]

Discussed in https://github.com/effordDev/sf-application/issue/92

@Jfeger310

^{Originally posted by @Jfeger310 December 4, 2023}
I've seen 2 use cases for this so far, and have a 3rd, so in broadband infrastructure the application had list recent projects, which could be 1 or 10, then cda had list board members, then an insurance company had list beneficiaries. what's similar here is it's not really data they want or need from an org stand point to report on, no list view, no report no search, so no need in a way to create a custom object to house, it's really only relevant and used on an application. So we've done a generic object to handle this. if it's an enterprise use of an application is it more efficient to have 10-15 custom object each with 2-10 fields that just supports application tables, or have one object with 10-15 record types, and all the fields on the one object..I kind of see the solution as one or the other, but am open to other ideas