Create API for GraphQL in Fabric
To create a fully functional API to access your data in Fabric, start from any workspace and select New item. In the panel that opens, under Develop data, select API for GraphQL.
Alternatively, from the Fabric portal home page, you can select Data Engineering from the list of workloads, then choose API for GraphQL. Enter a name and select Create to have a fully functional API to access your data in Fabric.
Next, connect to a data source by selecting Select data source. In the Choose connectivity option dialog, choose between single sign-on (SSO) or saved credentials. Then, select the data you want to connect.
The data source page shows all the items in your workspace available to connect. Then, you need to select which objects you want expose to the API, then select Load.
Enable or disable operations
Once you load the data, the GraphQL engine automatically creates queries and mutations for each object you expose.
You can enable or disable specific queries and mutations within the GraphQL schema, providing fine-grained control over API access and usage. This means you can manage API functionalities without changing code or redeploying.
This option is useful for temporarily disabling functionalities for maintenance, security, or performance reasons, or for controlling API operations based on user roles or other criteria.
In this example, the ProductModel table from AdventureWorksLT is the only table exposed. The engine automatically generates the queries and mutations needed for insert, update, and delete operations.
Note
When a query or mutation is disabled, any attempts to execute it will result in an error.
Manage relationships
GraphQL offers support for one-to-one (1:1), one-to-many (1:N), and many-to-many (M:N) relationships.
One-to-one (1:1): Each instance of a type is associated with a single instance of another type. For example, a User type might have a one-to-one relationship with a Profile type, where each user has exactly one profile.
One-to-many (1:N): A single instance of one type is associated with multiple instances of another type. For example, a User type might have a one-to-many relationship with a Post type, where each user can have multiple posts.
Many-to-many (M:N): Multiple instances of one type are associated with multiple instances of another type. For example, a Student type might have a many-to-many relationship with a Course type, where each student can enroll in multiple courses, and each course can have multiple students.
These relationships enable developers to create rich, interconnected data models that can be queried efficiently.
