The structure of legacy custom objects was more like a denormalized or NoSQL data structure as child objects and arrays could be stored in the data as object fields. This reduced the number of objects required and records.
The structure of custom objects 2.0 is more like a normalized database and will require more objects and more records to store the same data. While testing I identified the need to split one object into 3.
This impacts the number of API calls required. Is there a way to fetch related records at the same time or fetch related records via the API ?
Example: Object A and Object B with lookup to Object A. Knowing Object A Id how do I fetch all of Object B which lookup to Object A
Please sign in to leave a comment.