Closed calebmil closed 10 months ago
tecchan1107
commented
10 months ago Hi @calebmil ! Thanks for the report! I have confirmed the same phenomenon in my environment! Hmmm... maybe the specifications have changed...😥?
I think I will add a note to the sample README.md about grouping by a lookup column.
calebmil
commented
10 months ago It’s the time of year for unbaked code to be jammed in by MSFT in time for Ignite. Happens every year. On Nov 9, 2023, at 4:19 PM, Tetsuya Kawahara @.***> wrote: Hi @calebmil ! Thanks for the report! I have confirmed the same phenomenon in my environment! Hmmm... maybe the specifications have changed...😥? I think I will add a note to the sample README.md about grouping by a lookup column.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
Sample (which sample are you having trouble with)
group-header-remove-column-name
What Should Happen
When applied to a view with a Group By column specified, the value of that field would be rendered correctly.
What Actually Happens
It appears that a recent change (within the last three weeks) caused issues if the group by field is a lookup column. In several of our views where this had previously been working beautifully, we started seeing [object Object] instead of the lookup value of the column as was expected.
As a workaround, we were able to replace @group.fieldData.displayValue with @group.fieldData.lookupValue in views where there was only one grouping and that grouping was by lookup value. More work would have to be done to make this handle cases where there are two group by clauses where only one is a lookup field.