Skip to Content

Equijoin not validating in BO 4.1 IDT

I have a UNX universe that was converted from a UNV universe, and in the UNX version I have an equijoin that will not validate. This join will validate in the UNV version of the universe. The problem join is below.


Other equijoins using the same tables, and in some cases the same columns, validate just fine.



The cardinality for all three of these joins is set to 1,n and none of them are shortcut joins. The function to detect cardinality also will not work for the problem join

Any idea why this is happening?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Nov 02, 2016 at 01:12 PM

    Hi Keith,

    I see that there is dbo. prefix on the left hand side and schemaname.dbo on the right hand side, before the tablename.column name. If both the tables are coming from one schema, why don't you update the join by removing schemaname, and then try to validate it.


    Few other things as a check: a. Please refresh the structure of the data foundation layer to see if something changed. b. Please make sure that the database credentials used to connect in ODBC and Universe connection has access to that schema and/or all the tables included in the universe.

    I know that other joins on those columns are working fine, but, reconfirmation doesn't hurt.

    Mahboob Mohammed

    Add comment
    10|10000 characters needed characters exceeded