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.

Explanation
A DataRaptor Extract can retrieve data from multiple related objects. A DataRaptor Extract is a tool that can read data from a Salesforce object or invoke a Salesforce API, using SOQL queries or Apex methods. A DataRaptor Extract can also use filters, joins, and formulas to manipulate the data. A DataRaptor Extract can retrieve data from multiple related objects by using lookup or master-detail relationships in the SOQL queries or Apex methods

Explanation
The OmniStudio tool that should be used to meet this requirement is FlexCards. A FlexCard is a tool that can display data and actions in a card format. The consultant can use FlexCards to show all of the customer's related information on one screen, such as account information, contacts, cases, etc. FlexCards can also have actions that can invoke OmniScripts or Integration Procedures for further interactions, such as creating new records or updating existing ones