Why Can’t My Microsoft Foundry Agent Handle JSON and Excel Files in the New Interface?

0
12
Asked By CuriousBee123 On

I'm working on a Microsoft Foundry agent and I need to upload either JSON or Excel files for testing. In the latest version of Foundry, I can't seem to get it to accept files when I try to add them through the attach button. However, the same agent handled the JSON file without issue in the older version of Foundry. I'm confused about what's changed and can't find any useful documentation. It seems like files were automatically saved to a vector store in the old version, but I don't see that happening now. Can someone explain what I might be missing?

4 Answers

Answered By TechWiz42 On

It sounds like the new version has changed how it processes file uploads. In some of Microsoft’s newer services, they're making a clearer distinction between data ingestion and the agent itself. You might need to upload your file as an external resource or connection first. Have you checked to see if your file shows up independently in the workspace as an asset or knowledge source?

Answered By CloudNinja77 On

Honestly, it sounds like a feature gap in the new UI. The old version managed file handling by automatically pushing files into a vector store behind the scenes. In the new version, it seems like you need to set that part up yourself—if it’s not fully implemented yet. I’d recommend sticking with the old version for now or manually setting up file ingestion, like explicitly adding a data source or vector store if that’s available. You're not the only one feeling lost with the messy documentation!

Answered By DataDude88 On

Yeah, the new Foundry UI doesn’t auto-ingest files like the old one did. Generally, you’ll have to first add your file to a data source or vector store before testing the agent. It’s definitely a bit of extra work now.

Answered By DevExplorer99 On

I've had a similar experience while switching to the new Foundry interface. It feels a bit incomplete, and file uploads behave differently than in the old version. I noticed that my agent only recognized JSON files when the vector store was created automatically in the old UI, which doesn't happen in the new one. The documentation is lagging behind too, so it helps to compare both versions side-by-side to see what's changed.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.