Others

How to Reference @odata.nextLink in Fabric Data Pipeline

Elise Williams Sep 27, 2026 869 views

Question details

The user needs to correctly reference the @odata.nextLink property within a Fabric Data Pipeline expression.

How to Reference @odata.nextLink in a Fabric Data Pipeline

Product: Fabric Data Pipeline
Device & OS: not provided
Scenario: Handling Microsoft Graph API pagination in a data pipeline.
Observed behavior: The @ symbol in the property name requires specific expression syntax to be parsed correctly without causing pipeline errors.

Before you start

Ensure you have the exact JSON output from your previous activity and identify the exact nesting level of the @odata.nextLink property before writing your expression.

Solution 1Recommended

Consult the Microsoft Graph Community for Syntax Help

Because special characters in JSON properties require exact expression syntax in Fabric Data Pipelines, consulting Microsoft specialists is the most reliable way to resolve the issue.

Microsoft Graph pagination dynamically generates an @odata.nextLink URL to fetch subsequent pages of data. Because the '@' symbol often acts as a reserved character in expression languages, standard dot-notation might fail.

To get the most accurate syntax for your specific Fabric Data Pipeline version, reaching out directly to the Microsoft Graph community with your pipeline logs is highly recommended.

Collect your activity output

Run your pipeline and extract the exact JSON response output that contains the @odata.nextLink property.

Document your current expression

Copy the Fabric Data Pipeline expression you are currently trying to use, noting any specific syntax errors it generates.

Submit your query

Navigate to the Microsoft Graph community at https://learn.microsoft.com/en-us/answers/tags/161/ms-graph and post your question, including the activity logs and JSON structure.

Consult the Microsoft Graph Community for Syntax Help

Tip for Special Characters: In many pipeline expression languages, replacing standard dot notation (e.g., body.odata.nextLink) with bracket notation (e.g., body['@odata.nextLink']) helps bypass issues with special characters.

Free Microsoft Office alternative

Boost Your Productivity with WPS Office

While resolving advanced data pipeline configurations, you can easily document your API workflows, architectures, and logs using WPS Office. It is a highly compatible, free, and lightweight suite designed to streamline your daily tasks.

1. Download the Installer: Visit the official WPS Office website and download the free installation package.
2. Install the Suite: Run the installer and follow the straightforward on-screen instructions to set up the software.
3. Open and Edit Files: Launch WPS Office to instantly start working on your spreadsheets and documents with familiar tools.

Seamlessly document API workflows and data pipeline architectures in Writer.High compatibility with Microsoft Excel (.xlsx), Word (.docx), and PowerPoint (.pptx) formats.Lightweight design ensures fast startup times and minimal system resource consumption.

microsoft office alternative - wps office

Frequently Asked Questions

What is the @odata.nextLink property used for?

In Microsoft Graph and other OData-compliant APIs, the @odata.nextLink property contains the URL required to retrieve the next page of results when the response data is paginated.

Why do special characters like '@' cause issues in pipeline expressions?

Many data pipeline expression languages treat the '@' symbol as a reserved character or function prefix. When it appears in a JSON key, the parser may misinterpret it, requiring the use of bracket notation or escape characters to read it as a literal string.

How can I view the raw JSON response in a Fabric Data Pipeline?

You can review the raw JSON output by clicking the 'Output' icon next to your Web or Copy activity in the pipeline run monitoring view. This allows you to confirm the exact spelling and nesting of properties.

Office Quick Solutions