Hi there! I’m having a marketplace error which apparently requires a specific right-side/left-side order within links.
The error is "[link type name] requires [some rid], but [some other rid] was provided". Another user mentioned they fixed this error by “inversing the order of the objects in the link definition”, without changing the cardinality of each object type.
However, I am struggling to do this: I’ve tried recreating my link starting from either one of the objects, but it always ends up in the same undesirable order (in my case, with the “many” object on the left and “one” on the right) when I save.
Does anyone know how I can specify this order? Or is this a red herring? Thanks!
To give some more context, in case the right/left thing is a red herring:
- There are 3 object types (lets call them C, T, U) that are being used in links with this error.
- The erroring links (one to many) are U->T and C->T.
In marketplace:
- C’s properties, including primary key, seem to all be mapped without error.
- T’s properties, including primary key, seem to all be mapped. However, some of them (not including PK) are giving an error:
The configured parent object type does not match the expected parent object type.
- Only 4 of U’s properties (of which there are nearly 200) appear in Marketplace. These do not include the PK. They are mapped without error.
I would assume the error is coming from T, given it’s the commonality between links, but U’s lack of PK is suspicious…
Fixed! Ultimately the LHS/RHS issue was indeed a red herring. The problem came from mapping multiple marketplace inputs to the same object type (in this case, mapping both T and T2 to T).