FeatureFuel
0

App sync fails when an app declares a relation to a custom object owned by another app ("has no relation target object metadata")

Source: twentyhq/twenty#26188 · opened by @admin-laicadev
An app cannot declare a RELATION field whose target is a custom object owned by a different app. twenty apply fails during "Syncing manifest...", and every later apply of that app fails too. If I create the same relation in the UI it works fine. The docs ([[extending-objects]( say apps can extend objects of other apps, including relations. Relations to standard objects (person, company, opportunity, task, ...) work fine. Closest existing thread: #25506 (discussion). Version • Self-hosted Twenty v2.41.0, Docker image twentycrm/twenty:v2.41.0 (index digest sha256:47bcefe4e497ceef232f149153a4a61379830f5c898b7da71a5b0e21fd5ea916, linux/amd64 sha256:369d52757cf70b64c3f6a54cf424add49863c6fd1f595e5d0030d574859ce9c8) • twenty-sdk 2.41.0 • Commit: tag d1bb92d111f91529478da56aa677efbdba230c00 Minimal repro Two new apps, installed on the same workspace. No other code. App A (xprobe-alpha): one object, one text field. App B (xprobe-beta): the same kind of obj…

No pledges yet. Be the first to back this.

Make a pledge

Pledge your monetary support if this feature is added.

$

Comments

No comments yet.

Replying to

Add a comment

What do you think about this feature request?


Similar requests