Skip to content

Using Bing Grounding search parameters is not possible #58

Open
@RicardoNiepel

Description

@RicardoNiepel

Description:
When using Bing grounding parameters* in code, Bing is not display as Knowledge tool anymore and also the AI Foundry VSCode extension is unable to display the agent.
Defining Bing grounding parameters per extension is also not possible.

Does this occur consistently? Yes

Repro steps:

  1. Create an agent with Bing ground using search parameters
    BingGroundingSearchConfiguration searchConfig = new BingGroundingSearchConfiguration(bingConnectionId)
    { 
        Count = 5,
        Freshness = "Week",
        Market = "de-DE" 
    };

    // Create the BingGroundingToolDefinition object used when creating the agent
    BingGroundingToolDefinition bingGroundingTool = new BingGroundingToolDefinition(
        new BingGroundingSearchToolParameters(
            [
                searchConfig
            ]
        )
    );

    // Create the Agent
    PersistentAgent agent2 = agentsClient.Administration.CreateAgent(
        model: agent.Model,
        name: "my-agent",
        instructions: agent.Instructions,
        tools: [bingGroundingTool]
    );
  1. Try to load this Agent inside the extension.

Error:
Action: azure-ai-foundry.viewContext.openAgentDesigner
Error type: TypeError
Error Message: Cannot read properties of undefined (reading 'map')

Env:
Version: 0.6.0
OS: linux
OS Release: 6.1.91.1-microsoft-standard
Product: Visual Studio Code - Insiders
Product Version: 1.101.0-insider
Language: en

Call Stack
s extension.js:2:3122645
t.toAgentSchema extension.js:2:3120435
t.createAgentDesignerWebViewFromTreeView extension.js:2:3253406
V.openAgentDesignerFromTreeView extension.js:2:3109623
extension.js:2:3106971
extension.js:2:1815226
extension.js:2:1814987
l extension.js:2:1814732
extension.js:2:1815185
extension.js:2:1814621
extension.js:2:1813697
l extension.js:2:1813442
extension.js:2:1814140
extension.js:2:1771533
extension.js:2:1770488
l extension.js:2:1770233
t.callWithTelemetryAndErrorHandling extension.js:2:1771450
extension.js:2:1814130
extension.js:2:1813697
l extension.js:2:1813442
extension.js:2:1813957
Xb.h extensionHostProcess.js:120:41524
Xb.g extensionHostProcess.js:120:40601
Xb.executeCommand extensionHostProcess.js:120:40508
sz.h extensionHostProcess.js:120:43821
Xb.h extensionHostProcess.js:120:41524
Xb.$executeContributedCommand extensionHostProcess.js:120:42369
$5.S extensionHostProcess.js:29:164003
$5.Q extensionHostProcess.js:29:163783
$5.M extensionHostProcess.js:29:162872
$5.L extensionHostProcess.js:29:161977
ud.value extensionHostProcess.js:29:160774
D.B extensionHostProcess.js:27:2373
D.fire extensionHostProcess.js:27:2591
po.fire extensionHostProcess.js:29:9458
ud.value extensionHostProcess.js:361:3443
D.B extensionHostProcess.js:27:2373
D.fire extensionHostProcess.js:27:2591
po.fire extensionHostProcess.js:29:9458
lv.A extensionHostProcess.js:29:12574
ud.value extensionHostProcess.js:29:10994
D.B extensionHostProcess.js:27:2373
D.fire extensionHostProcess.js:27:2591
lS.acceptChunk extensionHostProcess.js:29:7941
file:/extensionHostProcess.js:29:7227
Socket.t extensionHostProcess.js:29:15251

Metadata

Metadata

Assignees

Labels

more infoNeed more information from customer

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions