Relations not being picked up during create statement

Bug description

Our createUser() function has stopped working, erroring that we aren’t providing an institutionUid when we are using the connect func. Prisma reports it is using UserUncheckedCreateInput, which doesn’t have the relations beyond the uid. Not sure why this is now the default.

(I noticed @matthewmueller closed off uncheckedScalarInputs as stable 4 hours ago, not sure if a change has been made during that time or if that’s just a coincidence).

How to reproduce

1. Run a prisma.[table-goes-here].create({}) query with a connection, such as:

institution: {
  connect: {
    institutionUid: institutionToAdd.institutionUid,
  },
},

1. Errors

Expected behavior

The query to succeed.

Prisma information

PrismaClientValidationError: 
Invalid `prisma.user.create()` invocation:

{
  include: {
    institution: true,
  },
  data: {
    userUid: '374174ea-2204-4a62-b033-9795a3fc31b3',
    institution: {
    ~~~~~~~~~~~
      connect: {
        institutionUid: 'df25802e-6cf5-4c21-bafc-141e2c296d58'
      }
    },
+   institutionUid: String,
  }
}

Unknown arg `institution` in data.institution for type UserUncheckedCreateInput. Did you mean `institutionUid`?
Argument institutionUid for data.institutionUid is missing.

Environment & setup

• OS: macOS
• Database: PostgreSQL
• Node.js version: v12.18.1 (using ts-node version 8.10.2, typescript version 3.9.7)
• Prisma version:

prisma               : 2.17.0
@prisma/client       : 2.16.1
Current platform     : darwin
Query Engine         : query-engine 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at ../../../.config/yarn/global/node_mo
dules/@prisma/engines/query-engine-darwin)
Migration Engine     : migration-engine-cli 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at ../../../.config/yarn/global
/node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine : introspection-core 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at ../../../.config/yarn/global/n
ode_modules/@prisma/engines/introspection-engine-darwin)
Format Binary        : prisma-fmt 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at ../../../.config/yarn/global/node_modu
les/@prisma/engines/prisma-fmt-darwin)
Studio               : 0.353.0

(edit: realised my prisma versions were out of sync so updated the client to 2.17.0, same issue persists)

[brantchoate]

@lucasjohnston I’m having the same issue

[andrew-hwahin]

I’ve just verified in my own codebase, if one of the fields is using the format of postId instead of post:{connect:{id}} then it will automatically switch into unchecked mode. Once it switched into unchecked mode, then we’re not able to use the connect checked method anymore. Hence to use the checked mode, we need to switch all to use the checked method.