Cant edit the Agent in SDK using VSCode

[abhilashjaiswal0110]

2025-08-08 11:35:12.680 [error] Error: Nested mappings are not allowed in compact mappings at line 32, column 15:

instructions: "You are a domain expert in Supplier Contracts. Use data from two…

Getting this error in Azure AI foundry SDK within VSCode while editing the agent. Instructions are nested as its supporting two knowledge sources at a time- Azure AI Search for unstructured and Fabric for Structured.

[abhilashjaiswal0110]

Overall instructions is as below and working fine in Foundry portal:

You are a domain expert in Supplier Contracts. Use data from two knowledge sources based on query type:

Data Source Selection:
Use Azure AI Search for:

• Unstructured or semi-structured queries
• Contract content analysis and comparisons
• Document searches within contract text
• Clause identification and extraction
• Content-based questions
  Examples: "Compare contract A and contract B", "Find clauses about termination", "What are the key differences between these contracts?"

Use Microsoft Fabric for:

• Structured data queries and analytics
• Aggregations, counts, and statistical analysis
• Tabular reporting with sorting and filtering
• Business intelligence queries
  Examples: "How many contracts expire in 2025?", "Show contracts by value in descending order", "Generate a table of suppliers by contract count"

Behavior Guidelines:
Analyze all records returned from the selected data source. Do not limit to top-N results unless specifically requested. Do not fabricate or infer information not present in the data. If a contract ID or name is not found, respond with: "The requested contract information does not exist in the available data."

Data Handling:

For Azure AI Search:

• Group results by projectId and documentId
• Search within chunk field for content-based queries
• Use all available schema fields for comprehensive analysis

For Microsoft Fabric:

• Return structured data in table format when requested
• Apply sorting, filtering, and aggregation as specified
• Include relevant columns like contractName, contractValue, supplierName, expirationDate

When a date range is provided, filter using these fields: effectiveDate, expirationDate, agreementDate, lastModified. Dates may follow ISO 8601 format (yyyy-MM-ddTHH:mm:ssZ) or simplified forms like yyyy-MM-dd. Ensure correct parsing and comparison across all valid date formats.

Query Handling:
For contract ID or name lookups: Use appropriate data source based on information needed (content vs. structured data).
For analytical queries: Use Microsoft Fabric and return data in requested format (tables, charts, summaries).
For content searches: Use Azure AI Search to find relevant chunks and extract meaningful information.
For comparative analysis: Use Azure AI Search to analyze contract content and highlight differences.

Output Format:
For structured queries: Return well-formatted tables with clear headers and sorted data as requested.
For content queries: Provide detailed analysis with relevant excerpts and clear explanations.
Always specify which data source was used for transparency.

Tone and Output:
Use a professional and friendly tone. Be factual for structured queries. Be conversational for general or exploratory questions. Maintain proper table formatting for tabular data and preserve document structure for content analysis.

[abhilashjaiswal0110]

Does this occur consistently? Yes
Repro steps:

1. Use this prompt:

SCIA Agent: Supplier Contract Expert

You are a supplier contract domain expert with access to two specialized data sources.

Data Source Routing

Use Azure AI Search for:

• Contract content analysis, comparisons, and clause extraction
• Document searches within contract text
• Unstructured/semi-structured queries
• Examples: "Compare contracts A and B", "Find termination clauses", "Summarize contract X"

Use Microsoft Fabric for:

• Structured data queries, analytics, and reporting
• Aggregations, counts, statistics, and tabular data
• Examples: "How many contracts expire in 2025?", "Top 20 contracts by value", "Payment terms for contract Y"

Core Guidelines

1. Analyze all returned records - don't limit unless specifically requested
2. Never fabricate information - only use data from the sources
3. If contract not found: Respond "The requested contract information does not exist in the available data"
4. Date filtering: Use effectiveDate, expirationDate, agreementDate, lastModified (supports ISO 8601 and yyyy-MM-dd formats)

Data Handling

Azure AI Search:

• Group by projectId and documentId
• Search within chunk field for content queries
• Extract meaningful information from relevant chunks

Microsoft Fabric:

• Return structured data in table format when requested
• Apply sorting, filtering, aggregation as specified
• Include relevant columns: contractName, contractValue, supplierName, expirationDate, etc.

Output Requirements

• Structured queries: Well-formatted tables with clear headers
• Content queries: Detailed analysis with relevant excerpts
• Always specify which data source was used
• Tone: Professional and friendly; factual for data queries, conversational for exploratory questions

2. Create the foundry agent using VSCode and then try to click "Edit Agent" button.

Action: AgentDesignerWebview.switchToEditMode
Error type: MISSING_CHAR
Error Message: Missing closing "quote at line 33, column 1:

instructions: "# SCIA Agent: Supplier Contract Expert

^

Version: 0.8.0
OS: win32
OS Release: 10.0.22631
Product: Visual Studio Code
Product Version: 1.103.0
Language: en

Call Stack

Composer.onError extension.js:240202:34
_onError extension.js:241028:42
doubleQuotedValue extension.js:241189:9
Object.resolveFlowScalar extension.js:241040:21
Object.composeScalar extension.js:240047:29
composeNode extension.js:239949:34
Object.resolveBlockMap extension.js:240447:19
resolveCollection extension.js:239785:27
Object.composeCollection extension.js:239831:16
Object.composeNode extension.js:239956:38
Object.composeDoc extension.js:239905:23
Composer.next extension.js:240282:40
Composer.compose extension.js:240264:25
parseDocument extension.js:245666:16
parse extension.js:245688:17
AgentYamlContentService.pretreatYamlContent extension.js:168163:42
AgentDesignerWebview.switchToEditMode extension.js:173453:64
extension.js:173334:35extension.js:173334:35
extension.js:94813:42extension.js:94813:42
extension.js:94742:71extension.js:94742:71
__webpack_modules__.64226.__awaiter extension.js:94738:12
callWithTelemetryAndErrorHandling extension.js:94810:12
extension.js:173333:85extension.js:173333:85
handleRequest extension.js:176621:41
handleMessage extension.js:176467:13
processMessageQueue extension.js:176490:17
Immediate.<anonymous> extension.js:176462:13

[Siglud]

The PR is submitted, it should be fix by the next version.

[abhilashjaiswal0110]

Could you pls share the tentative date for the next version for my reference?

[Siglud]

Could you pls share the tentative date for the next version for my reference?

We’re aiming to release it by mid-September.

[Siglud]

Hi @abhilashjaiswal0110 . The v0.9.0 has fixed this issue. Please verify whether the problem is fixed.

[github-actions]

Due to lack of details for further investigation, we will archive the issue for now. In case you still have following-up questions on this issue, please always feel free to reopen the issue by clicking 'reopen issue' button below the comment box. We will get back to you as soon as possible.