For a Type Ahead Block, what cannot be used as a data source?

• A. DataRaptor Extract Action
• B. Remote Action
• C. HTTP Action
• D. Integration Procedures

Answer: (D)

The Type Ahead Block is built to fetch a list of quick, lightweight suggestions as the user types. It needs a data source that can return a small, simple list fast. DataRaptor Extract Action, Remote Action, and HTTP Action are designed to provide quick, direct results from Salesforce data, a server-side action, or an external service, which fits the need for real-time suggestions.

Integration Procedures, while powerful for orchestration, aren’t exposed as a direct data source for Type Ahead. They’re heavier, multi-step processes that run as their own operation and aren’t optimized for the ultra-low-latency feedback a Type Ahead control requires. If you need to use Integration Procedure logic, you’d typically trigger it via another mechanism (like a Remote Action or HTTP call) and then return the results to the Type Ahead, rather than using the Integration Procedure itself as the data source.