nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

metadata relationships

peter_choe

i am trying to use metadata relationships to limit user choices based on previous. the problem i am having is that i have multiple metadata relationship that share a common metadata table. when i go to register the metadata relationship in the view set manager, i am able to register one of the metadata relationship, but not the other one. i am assuming that you can't register more than one metadata relationship if they share a metadata table.

1. is this true?

2. if this is true, is there a way around it?

Peter

Find more posts tagged with

Comments

dbguy

From what I understood, you have something like Country, State, City and relationships Country/State and State/City.

If this is your problem, the solution is to create a three way metadata relationship Country/State/City.

sphan_xell

You're probably triedd to break a single relationship: Meta1> Meta2 > Meta3 into 2 different ones.
What you did:
Relationship1: Meta1 > Meta2
Relationship2: Meta2 > Meta3
(Since each metadata field can only be registered once for each profile of a viewset, you'll have a conflict)
What you should do:
Relationship1: Meta1 > Meta2 > Meta3 (This is done at the Object Modeler step)

Hope this helps.
sphan_xell.

peter_choe

so is the following impossible to do in worksite mp?

relationship 1: meta 1 > meta 2
relationship 2: meta 1 > meta 3 > meta 4

if it is impossible, how can i set it up so that a selection on meta 2 and meta 3 is dependent just on meta 1? if i set it up so that

meta 1 > meta 2 > meta 3 > meta 4

wouldn't meta 3 be dependent on meta 2 instead of meta 1?

Edited by peter_choe on 01/05/06 01:15 PM (server time).

Migrateduser

Yes, this is a valid use case but it can lead to very tricky permutations which will be hard to handle in the field validations (especially for relationships with three or more levels). It would even harder to explain it to users. So we have limited the number of relationships that a field can participate (for a particular datasource) to one.

-bjoy

peter_choe

when you say it is a valid use case, do you mean there is a way to implement this in worksite mp? if so, do you have a suggestion on the easiest way to implement it?

what i have come up with is to make a linear hierarchy and try to figure out all the permutation for the field validation, which as you said can get messy with a large metadata field and/or levels.

Migrateduser

I am afraid, this cannot be implemented in the current configuration framework. If this is a show stopper for you, I will encourage you to discuss the topic with Product Management.

-bijoy

sample.rptdesign