AI-Assisted JSON Report Editing
Environment
| Product | Progress® Telerik® Reporting |
| Version | 20.2.26.1007 or higher |
| License requirement | An active Telerik Reporting trial or subscription license |
Description
I want to explore AI-assisted edits to an existing JSON report with Telerik Reporting schemas and validation APIs. Which examples can I review and adapt?
Solution
The Telerik.Reporting.Schema package provides schemas for Reporting model types and APIs to validate JSON definitions. See JSON Schema for Telerik Reporting Types and Validating JSON Report Definitions for the API contracts and requirements.
The helper project and AI skill in the samples repository provide an example of how to combine these APIs with an AI-assisted workflow. Use them as starting points: review the code and instructions, adapt them to your environment and requirements, and test the results before use in your application.
Sample Project and Skill
The AI-Assisted JSON Report Editing sample contains the following assets:
- Standalone helper project—A .NET console application for type discovery, schema retrieval, and JSON definition validation.
- Example AI skill—Instructions for targeted edits to existing
.trdjreports, including changes to text, style, layout, and report items.
The sample's README covers package and licensing prerequisites, helper commands, skill installation, and an example prompt. The skill does not create complete reports or report books from scratch.
Reviewing and Adapting the Sample
The sample demonstrates one way to use schemas and validation APIs in an AI-assisted editing workflow. Start by reviewing the helper code and skill instructions, then adapt them to your assistant, permissions, and requirements. If you try the workflow, use a copy of a report that you are authorized to share. For data-bound changes, provide the exact field names and types for the relevant data source.
The sample skill instructs the assistant to read the entire report definition. Depending on your AI tool, report content and validation diagnostics may be sent to its provider. Review the report before sharing it, and check your organization's data rules and the provider's and client's data-handling terms.
Keep credentials, connection strings, and license keys outside files accessible to the assistant. Named/shared connections keep connection strings outside the report, but do not remove queries, expressions, personal data, or other sensitive content from it.