Questions about nested Headers

nestedHeaders: [
                    // 1행 - 22개
                    [
                        {label: '번호', rowspan: 5},
                        {label: '진행상태', rowspan: 5},
                        {label: '영업자', rowspan: 5},
                        {label: '발전소명', rowspan: 1},
                        {label: '설치장소', rowspan: 1},
                        {label: '공사 계약 금액', rowspan: 1},
                        {label: '계약 일자', rowspan: 1},
                        {label: '발전허가 용량', rowspan: 1},
                        {label: 'PPA 접수 일자', rowspan: 1},
                        {label: '구조 접수 일자', rowspan: 1},
                        {label: '개발 접수 일자', rowspan: 1},
                        {label: '공작물 접수 일자', rowspan: 1},
                        {label: '모듈 제품명', rowspan: 1},
                        {label: '인버터 제품명', rowspan: 1},
                        {label: '구조물 발주 일자', rowspan: 1},
                        {label: '감리 업체', rowspan: 1},
                        {label: '공사계획 접수 일자', rowspan: 1},
                        {label: '안전관리 업체/담당자', rowspan: 1},
                        {label: '사용전검사 신청 일자', rowspan: 1},
                        {label: '상업운전 개시 일자', rowspan: 1},
                        {label: '설비확인 접수 일자', rowspan: 1},
                        {label: '무자본 본심사', rowspan: 1}
                    ],
                    // 2행 - 22개
                    [
                        '', '', '',  // 번호, 진행상태, 영업자
                        '대표자',
                        '연락처',
                        '영업비',
                        '계약금',
                        '공사계획 용량',
                        '납부 일자',
                        '완료 일자/보강',
                        '완료 일자',
                        '완료 일자',
                        '용량/수량',
                        '용량/수량',
                        '통관 일자',
                        '선임 일자',
                        '기간',
                        '연락처',
                        '검사 일시',
                        '계량기 설치 일자',
                        '완료 일자',
                        '승인 일자'
                    ],
                    // 3행 - 22개
                    [
                        '', '', '', '', '',  // 처음 5개는 이미 표시됨
                        '지급 일자/금액',
                        '소비자 입금 일자/금액',
                        '발전허가 접수 일자',
                        '현장 협의 일자',
                        '',
                        '허가 기간',
                        '허가 기간',
                        '발주 일자',
                        '',
                        '현장 입고',
                        '',
                        '',
                        '',
                        '',
                        '한전계약 체결 일자',
                        '보완 일자',
                        '보증료 지출 일자'
                    ],
                    // 4행 - 22개
                    [
                        '', '', '', '', '', '', '',
                        '발전허가 기간',
                        '여유 용량',
                        '', '', '', '', '', '', '', '', '', '',
                        '',
                        '보완 내용',
                        '총 보험료'
                    ],
                    // 5행 - 22개
                    [
                        '', '', '', '', '', '', '',
                        '',
                        '납부 기한',
                        '', '', '', '', '', '', '', '', '', '',
                        '',
                        '',
                        '비고'
                    ]
                ],

If th is configured in a cascaded structure in the above code, there is a phenomenon where the first line is repeated. Is it a bug? My current version is “handsontable”: “^14.6.1”.

Hi @eh_0124

Thank you for contacting us. Please share a code demo where the problem can be replicated. It’s also worth mentioning that the current version of Handsontable is 16.1, did you try upgrading to see if that would solve the problem?

Hello,

Given your five-row cascaded nestedHeaders configuration, is the repetition of the first line a known bug in Handsontable version 14.6.1, and does it specifically occur due to the use of rowspan on the first three columns?

Hi @sowix42873

Can you please share a code demo where the issue can be replicated?

Hi @eh_0124

Is this issue already solved?