I came across this (again) recently and thought that I would share my take ...
Whether Excel displays the height correctly is related to the merged columns. Pay attention to the alignment of columns for all objects on the page. Any objects that are not attached to the data table itself (or embedded in the data table) should be aligned on the columns of the table in question, at least for cells that should carry text. If there is any overlap leading to the separation of the columns of the table and the reunification of the wrapped text cells, Excel does not recognize the row height by setting CanGrow to True or by setting the row anchor in Excel.
In the original post, the user mentioned rows with several elements inside them. It is possible that these elements caused column splitting for surrounding subtotals or adjacent groups with portable text.
If the CanGrow parameter is set to False, then by default it will simply be prevented from automatically changing the line height for both the web view and export to Excel, so I donβt know if this is the ideal solution to this problem.
source share