How can we improve Azure Search?

Make errors and warnings as helpful and constructive as possible

Please try not to provide cryptic error and warning statements that are only understandable by project developers but rather try to provide HELPFUL and CONSTRUCTIVE errors and warnings that more quickly help the poor user.

I'm a newbie who quickly encountered the error:

400: {"result":{"Message":"Missing request parameters: definition"}}

when I tried to create a new index without a fields element. Why couldn't it provide (it certainly "knows" what the problem is) a more helpful, constructive error like

400: {"result":{"Message":"Missing required fields element when creating a new index"}}

11 votes
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
You have left! (?) (thinking…)
Harold Perry shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

0 comments

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base