Neutral State in Context

[former_member203645]

Hi all,

I am seeing 3 kind of states in Context in Information Design Tool.

- Green ( Include in the particular context )

- Red ( Exclude in the particular context )

- Neutral  ( ???? )

What does Neutral generally do ??

How does it impact and what kind of functionality it has ??

[Former Member]

Hello RUC,

if I remember correctly this state was introduced in IDT 4.0. Before that in UDT you had to choose if the join would be explicitly included or excluded.

Lets say your loop ends with table A and there is only one path to table B, should the join between A and B really included or excluded in one of the contexts? Actually it does not matter because that join is not in the loop and not in any of the contexts.

If in doubt or not 100% sure: Simply dont use neutral state, go old school and use explicit inclusion or exclusion.

Best regards,

Victor

[Former Member]

Hi Ruc,

Here is the explanation about states of joins

A context is defined by setting states for the joins involved in the ambiguity. In a context, a join has one  of three states:

• Included joins: In a part of the schema that is ambiguous, the context solves the loop by defining a

path with the included joins.

• Excluded joins: In a part of the schema that is ambiguous, the excluded joins define the path that

context will never take.

• Neutral joins are in a part of the schema that is not ambiguous, and are always included in the query

path of the context. Any join that is not explicitly included or excluded is neutral.

When a new join or table is inserted into the data foundation, it is neutral by default. Contexts will not

need to be updated unless the new table or join is explicitly involved.

Thanks,

Pramod.