Upsert fail in bulk update

Banny · May 22, 2023, 9:38am

I have…

[X] Read the following guideline: https://docs.squidex.io/01-getting-started/installation/troubleshooting-and-support. I understand that my support request might get deleted if I do not follow the guideline.
[X] Used code blocks with ``` to format my code examples like JSON or logs properly.

I’m submitting a…

[ ] Regression (a behavior that stopped working in a new release)
[x] Bug report
[ ] Performance issue
[ ] Documentation issue or request

Current behavior

I am using the Squidex SDK in C# program.
There is a function “BulkUpdateAsync”.
When I used it to update multiple contents, it will response “ID “xxxx” is currently exists”.
But I just want to update the content rather than create a new one.

Here is my sample code,

var job = testList.Select(x => new BulkUpdateJob
{
   Id = x.Id,
    Data = x.Data,
    Status = x.Status,
    Type = BulkUpdateType.Upsert
}).ToList();

var bulkUpdateTask = new BulkUpdate
{
    Jobs = job,
    DoNotScript = false,
    Publish = true
};
await squidexClient.BulkUpdateAsync(bulkUpdateTask);

Expected behavior

Bulk Update Successfully

Minimal reproduction of the problem

In fact, I don’t know how to reproduce the issue. It happened suddenly.

Environment

App Name:

[x] Self hosted with docker
[ ] Self hosted with IIS
[ ] Self hosted with other version
[ ] Cloud version

Version: 5.6.0, Squidex Client Library is using 5.6.0 as well

Browser:

[x] Chrome (desktop)
[ ] Chrome (Android)
[ ] Chrome (iOS)
[ ] Firefox
[ ] Safari (desktop)
[ ] Safari (iOS)
[ ] IE
[ ] Edge

Others:

Banny · May 23, 2023, 7:32am

Here is the sample response,

{
    "contentId": "10360889-8d1d-426e-aabf-1a9c41054d2b",
    "error": {
        "message": "Entity (53f9afd0-9838-4f08-830b-aa373d10689a--10360889-8d1d-426e-aabf-1a9c41054d2b) already exists.",
        "traceId": "|fe209977-4c08d04efc39136d.2.fb9472dd_",
        "type": "https://tools.ietf.org/html/rfc7231#section-6.5.8",
        "details": null,
        "statusCode": 409
    }
},

Sebastian · May 24, 2023, 9:38am

Do you have the same ID multiple times in your bulk update?

Banny · May 24, 2023, 9:55am

If you are talking about the content Id, I checked that all of it are unique.

Sebastian · May 24, 2023, 9:57am

Do you reuse Ids over multiple schemas? They must be globally unique.

These are the only ideas I have. if this is a bug I would not fix it, because the version is already very old.

Banny · May 24, 2023, 10:10am

How can I find that the id is duplicated in other schemas?

Sebastian · May 24, 2023, 11:03am

You have to write a script for that…

Banny · May 25, 2023, 2:59am

I tested with several ids. Those ids cannot be found in other schemas and should be unique.
So you suggest to update the version?

Sebastian · May 31, 2023, 7:33am

Yes…(sorry for letting you wait so long)

Banny · May 31, 2023, 10:27am

Which version will you suggest? Since I want to keep the current layout.
BTW, I found that if I cannot update in UI, bulk update function will return the above error as well (i.e. “ID “xxxx” is currently exists”).

Sebastian · May 31, 2023, 3:30pm

What do you mean with “current” layout? You have to update to the latest version, otherwise you will not receive bugfixes.

You could also provide me a backup of your database and I can have a look. AFTER the update.