1 item
Captures OData batch calls and extracts the path between /sap/opu/odata and $batch. Capturing is restricted to whitelisted domains. Stop hunting through Network logs to find OData details. This extension watches SAP Fiori/UI5 pages for OData batch calls, extracts the OData service binding name, and lets you jump straight into the corresponding Service Binding in ABAP Development Tools (ADT) with one click. - Capture OData automatically: Listens for $batch requests and extracts the OData binding name for you. - One‑click ADT navigation: Click any captured binding to open its Service Binding in ADT. - Configurable parsing: Set a custom prefix and suffix so the extension reliably extracts binding names from your app’s binding patterns. - ADT link base: Customize the ADT link base, including your Eclipse project name (e.g., DCL, ZCL, DCL_EN) to match your workspace. - Domain whitelist (regex): Limit capture to specific hosts using regex so it only runs where you want. - Lightweight and private: Runs locally; no data is sent anywhere. How it works 1. Configure your prefix/suffix, ADT link base (with your project name), and whitelisted domains in the extension’s Options. 2. Visit a SAP Fiori/UI5 page; the extension captures relevant $batch calls and extracts binding names. 3. Open the popup, see the captured bindings, and click to navigate directly in ADT. Requirements - ADT installed and set up on your machine. - Your ADT link base must reflect your Eclipse project naming. Note: This tool is intended for SAP developers working with Fiori/UI5 and ABAP CDS/Service Bindings.
Nov 15, 2025
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.