<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Dec 28, 2011, at 11:37 AM, Kristopher Kiger wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: 'Times New Roman', serif; font-size: 16px; "> <Level name="day" visible="true" column="day_in_month" nameColumn="day_long_name" ordinalColumn="day_in_month" type="Numeric" uniqueMembers="false" levelType="TimeDays" hideMemberIf="Never" description="day"></span></span></blockquote></div><br><div>Your issue is likely the fact that you're uniquely identifying a member via SQL (group by) (column=) as day in month (1,2,3..30) but using a non unique method to name your members via nameColumn (7 day names) across your month.</div><div><br></div><div>What happens if you remove the nameColumn (or use a nameColumn that *is* unique across Month)?</div><div><br></div><div>Nick</div></body></html>