ADO.NET Provider for GraphQL

Build 25.0.9434

ExposeDynamicProcedures

Specifies whether the provider exposes GraphQL mutations as dynamic procedures in the schema.

Data Type

bool

Default Value

true

Remarks

The ExposeDynamicProcedures property determines if GraphQL mutations are represented as dynamic procedures in the schema.

Example Schema

For example, consider the following GraphQL schema:

type Mutation {
  createUser(input: CreateUserInput!): User
}

input CreateUserInput {
  name: String!
  email: String!
}

type User {
  id: ID!
  name: String!
  email: String!
}

When this property is set to true, mutations are exposed as dynamic procedures, allowing them to be invoked like standard callable operations. For example, a mutation such as the following would be exposed as a dynamic procedure:

mutation {
  createUser(input: { name: ""John"", email: ""[email protected]"" }) {
    id
    name
  }
}

This enables you to easily call the mutation by passing parameters in a structured format, simplifying integration with GraphQL APIs.

When set to false, mutations are not exposed as dynamic procedures. This can simplify the schema structure by excluding mutation-based operations, which might be useful in scenarios where you only need read access to data or want a simpler schema for certain tools.

Enabling this property is useful in scenarios requiring robust interaction with GraphQL APIs, where you need to perform complex operations like resource creation, or deletions.

Copyright (c) 2025 CData Software, Inc. - All rights reserved.
Build 25.0.9434