createMany dosen't insert realation

[MHZarei]

Bug report

Required System information

• Node.js version: v16.16.0
• NPM version:
• Strapi version: 4.5.5
• Database: Sqlite
• Operating system: ubuntu 22.04

Describe the bug

If your entity have relation with another entity, and on createMany use id of it to insert, it doesn't insert relation data!
For example this code just insert rate and date and the user information doesn't inserted.

await strapi.db.query('api::rate.rate').createMany({
      data: [{ date: 1672788743747, user: 1, rate: 1 },
                 { date: 1672788743747, user: 2, rate: 2 },
                 { date: 1672788743747, user: 3, rate: 5 },
        ],
    }); 

Expected behavior

I expected the relation information (for above example: user) saved in the database;

[derrickmehaffy]

These will need to be an array of ids that already exist or you will need to loop through and create them beforehand and grab the IDs. We don't support creating nested data at any level.

[github-actions]

This is a templated message

Hello @MHZarei,

First thank you for reporting this feature need.
To manage feature requests and the Strapi roadmap, we are using Canny.
You will be able to access the Public Roadmap here: https://feedback.strapi.io.

In your message, please mention the URL of this thread in case some messages are posted there. But the most important is to have your feedback posted on our feedback/roadmap site.
The product team is reading EVERY comment, that really helps us to develop the project in the right direction. We are keeping all feature requests and project insights in one place, our feedback website.

In order to keep our GitHub issues clean and for valid bug reports this issue will be marked as closed, but please feel free to continue the discussion with other community members here.

Thank you for your insight and have a good day.

[dzcpy]

@derrickmehaffy
This is actually a bug not a feature request. It doesn't save any relations (using id), when this entity has already been created and is available with that relation ID.

[dzcpy]

To prove it, try to create a content type named post, and add a relation author to the user (user_permission) entity. Then try this:

await strapi.db.query('api::post.post').createMany({
  data: [{ author: 1 }],
});

It doesn't save the author field even if user 1 does exist.

[alicanso]

why is it closed? problem is still exist?