Forum Discussion

aukev's avatar
aukev
Helper III
6 years ago
Solved

Avoiding a circular dependency when having a calculated column that references the other table

I have these two tables. Now I've added a calculated column to the Order table (see dax below). The idea is that this is a best estimate of which call belongs to which order. This works fine but now...
Need Help
  • mauriciosotero's avatar
    mauriciosotero
    6 years ago

    Now I've undertand.

     

    You have to create a CallID in the two table. For the table Calls, the CallID will be the primary key, and in the Order table the CallID will be the foreing key.

     

    In the Calls table, create a CallID like:

    CallID = CONCATENATE(callDate, Customer Phone)

     

    and in the Order table:

    CallID = CONCATENATE(dateKey, Phone)

     

    After thar, you can create the relationship.

mauriciosotero's avatar
mauriciosotero
Resolver III
6 years ago

Now I've undertand.

 

You have to create a CallID in the two table. For the table Calls, the CallID will be the primary key, and in the Order table the CallID will be the foreing key.

 

In the Calls table, create a CallID like:

CallID = CONCATENATE(callDate, Customer Phone)

 

and in the Order table:

CallID = CONCATENATE(dateKey, Phone)

 

After thar, you can create the relationship.

  • aukev's avatar
    aukev
    Helper III
    6 years ago

    Hi, thanks. The problem is that there can be multiple calls on the same day and these are not necessarily connected with an order.

    So creating a call id like that on the calls table will create multiple calls ids that are the same.

     

    But then again maybe it's okay if these have the same id as multiple calls to the same customer probably mean that it's about the same order.