Forum Discussion
Calendar relationship issues
- Anonymous9 years ago
Please review my reply in this similar thread, the above issue could occur when you change the format of the opportunity Date field from DateTime to Date, in this scenario, not all the datetime values in your opportunity table match the date values in your calendar table.
Regards,
Lydia Zhang
YEp it is mapped to that date, and the calendar object is made up of Min(opportunity date) and Max(opportunity Date)
IF I change the parameters of the If statement to = historical date
It pulls through the date fine using the relationship as expected,
If I change the parameters of the column to = createddate
Nothing pulls through
- vanessafvg9 years agoCommunity Champion
that is strange, if you created the opportunity date in power query rather than dax in a calculated column would that make a difference maybe?
- Voose9 years agoHelper III
How would I create it in Power Query? -> Edit Queries then? - I can't merge it with my Calendar tables as obviously thats a calculated table :(
- vanessafvg9 years agoCommunity Champion
what i would do is first try and figure out why the date is not working in the one you have created i.e create 2 columns opporunitydate 1 and opportunitydate 2 one without createddate and one with and see where the differences are and see if you can correct it in the if statement.
it is hard to figure out what the issue is without seeing the structure of your tables, if you could post a screen shot of your relationships that might help.
the power query option is for me a better option because its shaping the data how you want it, i.e create calculated column exactly like you have in dax in the table you currently have it, unless the table its created in now is the calculated table that is calculated in dax not power query ? i.e in power query add column / create custom column and then have the same if statement i.e
if historical date = "" then createddate
else historicaldate
i am not sure what difference it would make but it might.