I have recently started getting this error when I debug my python function app: (BadRequest) Message: {"Errors":["One of the specified inputs is invalid"]}

我最近在调试python函数应用程序时开始出现此错误：（BadRequest）消息：｛“错误”：[“指定的输入之一无效”]｝

The function app works perfectly well for my coworkers and they are not getting this error.
The error occurs whenever I attempt to access the azure cosmos db.

该功能应用程序非常适合我的同事，他们没有收到这个错误。每当我试图访问azure cosmos数据库时，就会出现错误。

Sample

样品

item = { "firstname": "John", "lastname": "Doe"}
container.upsert_item(item)

The issue seems to be that insert into the database is missing the "id" field. If I add this field to the item before calling upsert_item(item) it works correctly.

问题似乎是插入到数据库中缺少“id”字段。如果我在调用upsert_item（item）之前将此字段添加到项目中，它将正常工作。

Why did I not originally need to do this (coworkers don't need to) and what setting did I change to stop it from auto adding the id field?

为什么我最初不需要这样做（同事不需要），我更改了什么设置来阻止它自动添加id字段？

I am using visual studio code, coding in python, installed the azure tools extension. I have tried deleting the code from disk and re-cloning it, removing all the extensions and reinstalling them, and I even completely uninstalled visual studio code. Whatever setting changed is still there.

我使用的是visualstudio代码，用python编码，安装了azure工具扩展。我试着从磁盘上删除代码并重新克隆，删除所有扩展并重新安装，我甚至完全卸载了visualstudio代码。无论环境发生了什么变化，都仍然存在。

EDIT

编辑

Added the container properties

添加了容器属性

Container properties {'id': 'person', 'indexingPolicy': {'indexingMode': 'consistent', 'automatic': True, 'includedPaths': [{'path': '/*'}], 'excludedPaths': [{'path': '/"_etag"/?'}]}, 'partitionKey': {'paths': ['/lastname'], 'kind': 'Hash'}, 'uniqueKeyPolicy': {'uniqueKeys': []}, 'conflictResolutionPolicy': {'mode': 'LastWriterWins', 'conflictResolutionPath': '/_ts', 'conflictResolutionProcedure': ''}, 'geospatialConfig': {'type': 'Geography'}, 'analyticalStorageTtl': -1, '_rid': 'O-pDAPQSY5Y=', '_ts': 1654191756, '_self': 'dbs/O-pDAA==/colls/O-pDAPQSY5Y=/', '_etag': '"00003b31-0000-0100-0000-6298f68c0000"', '_docs': 'docs/', '_sprocs': 'sprocs/', '_triggers': 'triggers/', '_udfs': 'udfs/', '_conflicts': 'conflicts/'}

Found the answer to my issue.
I had updated azure cosmos db to the latest version (4.3.0) globaly (which is why it only affected me, should have put it in the requirements.txt instead) which does not allow for the automatic creation of ids.

找到了我问题的答案。我已经将azure cosmos db更新到了globaly的最新版本（4.3.0）（这就是为什么它只影响我，应该把它放在requirements.txt中），它不允许自动创建id。

There is a single line change (from 4.2.0 to 4.3.0) in the upsert_item(...) function that is difficult to spot (worded very similarly) when you are looking at a wall of code.

upsert_item（…）函数中有一行更改（从4.2.0更改为4.3.0），当您查看代码墙时，很难发现（措辞非常相似）。

Azure-Cosmos-4.3.0 github link to the line

Azure-Cosmos-4.3.0 github连接到线路

Annoyingly this line is hard coded. Why they decided to prevent the user from auto generating ids is beyond me.

令人恼火的是，这行代码很硬。我无法理解他们为什么决定阻止用户自动生成id。

If people are still looking for this:
You can now add the enable_automatic_id_generation flag to the create_item method.

如果人们仍在寻找：现在可以将enable_automatic_id_generation标志添加到create_item方法中。

Example:

示例：

result = container.create_item(
    {
        "data": "hello world",
    },
    enable_automatic_id_generation=True,
)