Each Extract Step adds complexity to the generated query and data retrieval process. As additional objects are joined and processed, the Data Mapper requires more resources and can increase the risk of governor-limit issues, especially in high-volume environments. Salesforce Data Mapper best practices recommend minimizing the number of related objects and using relationship notation whenever possible to improve performance. There is no requirement to automatically convert the solution to Apex, nor does Salesforce impose a visibility restriction after three object levels. JSON truncation is also not a standard consequence of multiple Extract Steps. From an architectural perspective, large multi-object extracts should be simplified, broken into reusable components, or orchestrated through Integration Procedures to improve scalability and maintainability.