Closed effordDev closed 9 months ago
@Jfeger310 I think we need to revisit this. I'm not sure the value/advantage of consolidating different types of data into one object.
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
I guess this should have been a discussion/idea not an issue
Move to discussion #87
Discussed in https://github.com/effordDev/sf-application/discussions/87