Parent Child Relationship
Is there such a concept as child records for a lead? For instance if I have survey responses with field values x, y and z that I want to store repeatedly each time a client completes a survey, I'd prefer a method that puulates the same fields each time but within unique records. I'm trying to avoid exploding the number of custom fields so I'm cusrious what the best practices are for this kind of thing. I have other use cases in addition to the surveys where "child" records could be beneficial.