Konstantin Nesterov

As a note the issue is specifically with `em.populate`, so when we do ``` async function pseudoGraphQL() { const { em } = getRegistry() const companies = await em.find(Company, {})...

> But I know there is one extension you can use to generate nested populate definition for GQL query or something like that. Not sure how up to date is...

Let me put https://github.com/mikro-orm/mikro-orm/issues/3383#issuecomment-1211846740 in production to verify again, but I think somehow even though on the top level we were pre-populating the fields children could not get access to...

I am pretty sure that data is in the database :) When fetching with `em.findOneOrFail(Image, {companyLogo: parent.id})` everything work as expected I can confirm what I wrote in https://github.com/mikro-orm/mikro-orm/issues/3383#issuecomment-1211846740: pre-populating...

I will try to provide a better (failing) example, but one thing to note is that most likely you will not be able to replicate it with `sqlite` as a...

In the meantime do you think we can provide any useful debug info from our prod environment? I could install some patched version of mikro-orm if needed

Would be happy to test the dev version to assist

@B4nan I have added a check in the code to see whether field existed pre- and post-populate, will update you tomorrow

@B4nan so far our logs show the following: ``` const [companies, count] = await em.findAndCount(Company, where, { limit, orderBy, populate: ['logo', 'image'], }) ^ not sure what state is at...

I've added more logs to check for `.logo` and `.image` immediately after `em.findAndCount` and sometimes those are also `undefined` :(