The data set component is meant to be used in conjunction with an evam definition Entity view action mapper • Australia ServiceNow AI Platform Capabilities • Docs | ServiceNow
If you look at the example payload in the docs for the data set component you'll notice that it is quite complex.
You can test it out with the "evam data resource" data resource and just bind the compositeDataViews property to the data property in the data set component.
As for graphql are you able to create the api and resolvers or do you struggle with the creation of the data broker?
The schema for an api looks like this. You can use the @source notation to resolve values from a gliderecord directly. Just return the gliderecord object in your resolver for getIncidents for example
schema {
query: Query
}
type Query {
getIncidents(limit: Int = 5): [Incident]
}
type Incident {
sysId: String @source(value:"sys_id.value")
number: String @source(value:"number.value")
}
For the data broker the query is defined like so, you can also test it out in the graphql explorer. Notice in servicenow you have to include the app namespace and the schema namespace
query($limit: Int){
x934661 {
incidentGet {
getIncidents(limit: $limit) {
sysId
number
}
}
}
}In trying to figure out evams or graphql apis it is just best to look at what is available oob and try and replicate by copying.
