Forum Discussion
X axis not aligned
Hey cnpdx,
No need to share the file, but if you could share the relationship between the tables that would help. Also, how is the date column (used in the graph) formatted and what is the data type? Finally, I would look at the sorting on the date column, is it sorted by another column?
Hope this helps,
Alan
share the relationship between the tables that would help.
- 1 date from the dynamic date table to many dates on a transaction table
Also, how is the date column (used in the graph)
- I use month end dates for everything-for example all sales no matter what date in july fall under 7/31
- how is it formatted and what is the data type?
- Data type: date
Finally, I would look at the sorting on the date column, is it sorted by another column?
- Its sorted by itself
thanks for your help!
Does your fact table contain records without connecting to any date?
Based on your screenshot, it looks like you have "blank" category for your fact data, and you can see you already have 12 columns before the Jan 2017. So please verify the connecting date key column in your fact table.
Regards,
Hi, thanks for getting back to me
Does your fact table contain records without connecting to any date? all fact table records contain a date. there are no blanks, guaranteed
Based on your screenshot, it looks like you have "blank" category for your fact data, and you can see you already have 12 columns before the Jan 2017. So please verify the connecting date key column in your fact table.
where are you seeing the "blank category"? Here is a screenshot of the relationship. it's one to many: transaction date id from date table to many on fact table
as you can see from this screenshot, the same data applied to 2 different views gives a different output, and this is where the alignment issue comes in. January 2017 for example-on the matrix all the data is accurate, sales aligns with the correct month. But when converted to chart format, the x-axis date label "Jan 2017" aligns with the December bar, and that is what needs to be fixed.
this holds true not matter what types of reports i am running, not just this one
