Does having an optional json field effect how you parse data to it via an update?

[simondpalmer]

I have a function that usually works but for some reason it no longer updates. I think it has something to do with "sides" no being optional? Not sure, but I am sending a json object to it like before but it still errors.

def create_analysis_edges(interestId, edges):

    endDate = datetime.datetime.now() + datetime.timedelta(days=7)
    db = Prisma(
        datasource={
            'url': environ.get("PRISMA_URL")
        }
    )
    db.connect()
    analysis = db.lotinterest.update(
        where = {
            'id': interestId
                },
        data= {
            'sides': edges,
            'reportIdeally': {
                'upsert': {
                    'create': {
                        'isComplete': False,
                        'expiresAt': endDate,
                    },
                    'update': {
                        'isComplete': False,
                        'expiresAt': endDate, 
                    }
                }
            }
      }
    )
    db.disconnect()

prisma.errors.FieldNotFoundError: Failed to validate the query: `Unable to match input value to any allowed input type for the field. Parse errors: [Query parsing/validation error at `Mutation.updateOneLotInterest.data.LotInterestUpdateInput.sides`: Field does 
not exist on enclosing type., Query parsing/validation error at `Mutation.updateOneLotInterest.data.LotInterestUncheckedUpdateInput.sides`: Field does not exist on enclosing type.]` at `Mutation.updateOneLotInterest.data`

Part of my schema looks like this

model Lot {
  id            String  @id @unique @default(cuid())
  zipCode       String
  address       String  @unique
  latitude      Float   
  longitude     Float   
  place_id      String
  apn           String?
  acreage       Float?
  zoneType      String?
  zoneDescription     String?
  geometry      Json?
  zone          Json?
  street        Json?

  // Relation fields
  interest LotInterest[]
}

model LotInterest {
  id                String @default(cuid()) @id
  createdAt         DateTime @default(now())
  role              UserRole
  sides             Json?
  shared            LotShared[]
  reportIdeally          ReportIdeally?
  reportFaPropDetail     ReportFaPropDetail?
  reportFaTotalViewDetail     ReportFaTotalViewDetail?
  reportFaEasementsDetail     ReportFaEasementsDetail?

  // Relation Fields
  userId       String?  
  lotId        String? 
  user         User?   @relation(fields: [userId], references: [id])
  lot          Lot?    @relation(fields: [lotId], references: [id])
  @@unique([userId, lotId])
  @@index([userId, role])
}
model ReportIdeally {
  createdAt    DateTime  @default(now())
  expiresAt    DateTime?
  isComplete   Boolean?
  price        Float?
  codeReview   Json?
  setbacks     Json?

  // Relation Fields
  interestId   String @id
  interest     LotInterest @relation(fields: [interestId], references: [id])

}

[simondpalmer]

Oh I worked it out I hadn't run "generate" yet. My bad!

[RobertCraigie]

Ah! Hopefully we can figure something out to make this mistake harder soon.