Neptune DXP Documentation
Neptune DXP - Naia Build

Connect data sources and APIs

Aim: Add your system data sources to the application context via the Data tab, so that all subsequent prompts can produce UI and logic that correctly references real data structures, field names, and operation types.

Why data connection comes before deep logic generation

Naia Build shares data schema metadata (field names, types, operation types) with the AI model on every request once data sources are added. This means prompts like Show a list of work orders sorted by priority. produce correctly typed, properly bound components rather than generic placeholder code. Connect your data early and every subsequent prompt benefits automatically.

Prerequisites

Procedure

Neptune DXP - Open Edition

  1. Open the Data tab. This is where you manage all data sources, API connections, and data bindings for your application.

  2. Add an API operation by selecting Add API and select from API definitions already configured in the API Designer, for example, GET /workorders, POST /workorders/{id}/status.

    Only field names and types are shared with the AI. Endpoint URLs, credentials, and response data are never transmitted. See Security and data.

    If your application integrates with SAP, add these through the MultiModel component. The Data tab supports SAP API operations alongside standard REST APIs.

  3. Confirm APIs are visible in context. In the Chat tab, enter a prompt such as What data sources are available in this application?.

  4. Prompt Naia Build to generate or update UI components that reference your real data.

    Result: Naia Build uses the schema metadata to produce correctly bound components.

Neptune DXP - SAP Edition

In Naia Build for Neptune DXP - SAP Edition, the Data tab connects to SAP Edition APIs and Ajax calls.

  1. Open the Data tab. It displays each connected SAP Edition API and Ajax call together with its operations.

  2. Add a SAP Edition API or Ajax call for Naia Build to reference.

  3. Confirm the data source is in context. In the Chat tab, enter a prompt such as What data sources are available in this application?.

  4. Prompt Naia Build to generate or update UI and logic that references the data.

    Result: Naia Build uses the SAP schema to produce correctly typed and bound components, referencing real field names, types, and operation types rather than placeholder bindings. The same applies to generation driven by Ajax calls.

Naia Build operates within the context of a single application per session. If you need to reference data structures from another Neptune application, those must be exposed via a data source that is explicitly added to this application’s Data tab.

Result

  • Your system data sources are connected and visible to Naia Build via the Data tab. Subsequent prompts produce UI components and logic that correctly reference your real data structures, field names, and operation types.

Next steps

Related topics