Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
8 years ago
Solved

two main tables, accusing ambiguity. How to proceed?

Hey guys.

 

 

First of all, i have one table with 3 date fields and 3 'users' that i need to 'unify' in one.

 

After a lot of digging in here, i found a solution that i should use a calendar table, conecting the dates, then use, instead of one, three tables (the same table, but each one with their exclusive date and user fields).

 

Ex.:

 

Previously

Date1

Date2

Date3

User1

User2

User3

 

Now

Table1

Date1

User1

 

Table2

Date2

User2

 

Table3

Date3

User3

 

All dates, unificated in the Date field, in the Calendar table.

 

The problem is that i have to unify the USERS too. If i try to connect the tables with a MAIN USER table, it accuses a ambuiguity alert.

 

Like, if i have to show what the user ALAN did (registers from Table 1, 2 and 3) on June 2018.

 

The date is solved, but my problem now is the USER fields.

 

Here is a pseudo diagram of how i think it should be. Dont know if it's right or wrong, but, after a long time, that's the only solution that came up to me.

 

 

Sorry for my bad english, btw. :)

  • Anonymous's avatar
    Anonymous
    8 years ago

    Hey Anonymous, thanks for replying.

     

    Thanks for the confirmation that my way was the 'right way', lol.

     

    I was having trouble by thinking that this idea might not be the right one.

     

    Now that you said it was right, i dig it up a little bit more and found the real problem.

     

    It was accusing ambiguity because the cross filter direction, which was both.

     

    So, I changed the direction to single and it worked perfectly.

     

    Thank you so much!

4 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    8 years ago

    You seem to have a good handle on what you need to do.  Your diagram looks correct as well.

     

     

    What do you feel you are having trouble with?  You have mentioned that the user table is going to be a problem, but I didn't see anything in your post that indicates how it will be a problem.

     

    If you are simply looking for guidence on whether you are on the right path, then I can certainly agree and state that you are doing it correctly.

    • Anonymous's avatar
      Anonymous
      Not applicable
      8 years ago

      Hey Anonymous, thanks for replying.

       

      Thanks for the confirmation that my way was the 'right way', lol.

       

      I was having trouble by thinking that this idea might not be the right one.

       

      Now that you said it was right, i dig it up a little bit more and found the real problem.

       

      It was accusing ambiguity because the cross filter direction, which was both.

       

      So, I changed the direction to single and it worked perfectly.

       

      Thank you so much!

  • Thejeswar's avatar
    Thejeswar
    Icon for Super User rankSuper User
    8 years ago

    Hi Anonymous,

    Do you mean that your tables "Table1, Table2 and Table3" have two columns each Date1, User1,....etc.?

     

    Also can you share the sample data for your tables and the expected output?

     

    • Anonymous's avatar
      Anonymous
      Not applicable
      8 years ago

      Hey Thejeswar, thx for replying.

       

      Almost that.

       

      I have something like this:

       

      Table1 Table2 Table3
      ID ID ID
      Date1 Date2 Date3
      UserInsert1 UserInsert2 UserInsert3


      Then, I accomplished to bring the registers from all three tables in one date. Ex:

       

      I Want every register that happened in March, 2018. That's OK.

       

      Now, I need to bring everything that happened in March, 2018 and the user is inserted that register is ALAN. That's my problem.