Error during upgrade - Field of type RELATION is a many to one relation but does not have a join col | Twenty | Page 1

static wadi Oct 5, 2025, 6:19 AM

#

Hi community! During another attempt to upgrade my Twenty instance, I got stuck at the error described in https://github.com/twentyhq/twenty/issues/14896. Any ideas how to resolve this?

restive fiber Oct 5, 2025, 7:14 AM

#

Hey @static wadi, could you please share your workspace version in database located at core.workspace.version ?

static wadi Oct 5, 2025, 7:16 AM

#

It's 0.53.0

restive fiber Oct 5, 2025, 7:19 AM

#

Please make sure to have a backup of a functional db dump

#

Please try running

yarn command:prod upgrade:0-52:migrate-relations-to-field-metadata

#

an re-attempt 0.53.6 upgrade ( not 0.54 ) lets try fixing your instance on 0.53 first

static wadi Oct 5, 2025, 7:21 AM

#

0.53.6 does not exist (as a Docker image), do you mean 0.53.8 ?

#

Running the command you suggested yields:

ERROR [MigrateRelationsToFieldMetadataCommand] Error in workspace edd7b1fd-3e21-49ea-aeaf-cb5d3be614ca: relation "metadata.objectMetadata" does not exist

restive fiber Oct 5, 2025, 7:38 AM

#

are you re-using an instance that you attempted to upgrade to an higher non incremental version ?

static wadi Oct 5, 2025, 7:39 AM

#

It's the same instance that I previously (yesterday) move from 0.53.0 to 0.54.6.

restive fiber Oct 5, 2025, 7:41 AM

#

What version are you currently running commands on ?

static wadi Oct 5, 2025, 7:45 AM

#

0.53.0

restive fiber Oct 5, 2025, 7:46 AM

#

Has your 0.53 instance been healthy/working before ?

static wadi Oct 5, 2025, 7:47 AM

#

Yes

restive fiber Oct 5, 2025, 7:47 AM

#

I assume you've: ( on same pg instance )
0.53.0 -> 0.54.6
0.54.6 -> 0.53.6
0.53.6 -> 0.53.0

#

Please try going back to 0.54.6 and running

yarn command:prod upgrade:0-52:migrate-relations-to-field-metadata

static wadi Oct 5, 2025, 7:53 AM

#

Same error. What I now did though is:

Drop database and load clean backup corresponding to (non-upgraded) state at 0.53.0
Run the command you sent
Upgrade to 0.53.8 -> was successful

Now I tried to go to 0.54.6 and am getting a new error now:

QueryFailedError: column viewFilter.subFieldName does not exist

restive fiber Oct 5, 2025, 7:56 AM

#

Ok cool checking

#

please try running

yarn command:prod workspace:sync-metadata

static wadi Oct 5, 2025, 8:00 AM

#

static wadi Oct 5, 2025, 8:25 AM

#

Does this error tell you anything?

#

Gotta bounce now, will get back here later today. Thanks a lot for your support already!

restive fiber Oct 5, 2025, 8:38 AM

#

Unfortunately on mobile atm ! Will investigate tomorrow in what db migrations is introduced this column
Latest attempt could be running an

yarn database:migrate:prod

#

No worries !

static wadi Oct 5, 2025, 8:42 AM

#

Didn't help, unfortunately.

restive fiber Oct 5, 2025, 8:50 AM

#

Ok I will reach back with further information

restive fiber Oct 7, 2025, 4:28 PM

#

Hey @static wadi, nothing new on your side ? I can take some time tomorrow to dig if still an issue

static wadi Oct 7, 2025, 6:50 PM

#

Hi @restive fiber, yes, unfortunately I did not manage to resolve the issue in the mean while. Neither of the command you sent seem to have helped. Would be super thankful if you could have another look into it!

restive fiber Oct 8, 2025, 11:34 AM

#

static wadi Same error. What I now did though is: - Drop database and load clean backup cor...

Hey could you please share the context around the
QueryFailedError: column viewFilter.subFieldName does not exist

static wadi Oct 9, 2025, 7:25 PM

#

Sorry for the late reply, have been busy 😐

Here you go: https://paste.dismail.de/?a0da3f8abb77de24#7o7sDFCUtFVUkESmSBtsXG4icSvNLEsTcxX6r5bfooCL

Hope that helps!

static wadi Oct 11, 2025, 6:14 AM

#

Does it? 🙂

restive fiber Oct 12, 2025, 5:57 PM

#

Unfortunately there's still not the logger name in the shared log

#

Can't if it comes from the upgrade command or classic api usage

#

Though manual sync metadata and migrations run should be enough here

static wadi Oct 12, 2025, 7:37 PM

#

The error occurs when I open my Twenty instance in the browser. Running sync-metadata or upgrade commands both yield this error: https://paste.dismail.de/?90163cf5dd05dea8#FzBMTRrL4MEag6ywRyWn881zbFD8JwjFysp1UJF8SSYP.

restive fiber Oct 14, 2025, 9:48 AM

#

Hey @static wadi I think the easiest would be to setup a call so we can sync our schedule and handle the migration together
I'm free tomorrow CEST 4pm for 45 mins

static wadi Oct 16, 2025, 8:46 PM

#

Sorry, didn't check Discord recently. I'd be available tomorrow between 9 am and 2 pm CEST

restive fiber Oct 18, 2025, 5:22 AM

#

Hey, would you be available on next monday 2pm CEST ?

static wadi Oct 20, 2025, 7:25 PM

#

Unfortunately no. Are you available on Friday somewhere between 9 am and 2.30 pm?

restive fiber Oct 21, 2025, 11:06 AM

#

yep lets book friday 11am CEST
Is that ok for you ?

static wadi Oct 21, 2025, 8:52 PM

#

Sure, please send me a calendar invite to [email protected]

static wadi Oct 24, 2025, 9:08 AM

#

Hey man, are you there?

restive fiber Oct 24, 2025, 9:29 AM

#

Hey so sorry

#

@static wadi I was in a tunnel wasn't aware of time
I can definitly create a timebox for you during the afternoon please let me know

#Error during upgrade - Field of type RELATION is a many to one relation but does not have a join col