[Excel export] Cannot merge already merged cells

Hi Leo,

Thanks for the update. This issue should be fixed now in the latest sandbox build (2025.3.6647).

Please let me know if the problem persists.

Hi Dan,

Unfortunately, it does not. However, the documented change is for the Scheduler, not the Gantt?

Cheers
Leo

The Gantt chart uses Scheduler internally, so the change applies to it as well.

I’m not able to reproduce the problem with the following config anymore:

dp.scale = 'Week';
dp.cellWidth = 100;
dp.useEventBoxes = 'Never';
dp.cellDuration = 1440;
dp.cellGroupBy = "Month";
dp.cellWidth = 100;
dp.cellWidthSpec = "Fixed";
dp.timeHeaders = [
    {groupBy: "Month", format: "MMMM yyyy"},
    {groupBy: "Week", format: "d"}
];
dp.useEventBoxes = "Always";
dp.days = 300;

Sometimes, the old version of the library gets cached so you can verify that.

If the problem still persists, could you please post a full config that reproduces the problem?

Hi Dan,

unfortunately, the issue persists for me, even when not having any events - so it must be the config. However, the only change to other configs I have (that do export correctly) are the values already provided.

We also add cssClasses and HTML, but I don’t see how that would impact the error:

if (args.header.level === 0) {
	args.header.cssClass = 'header_month';
}

if (args.header.level === 1) {
	args.header.cssClass = 'header_week';
	args.header.html =
		'Week ' +
		(this.week_number_algorithm === 'ISO8601'
			? args.header.start.weekNumberISO()
			: args.header.start.weekNumber());
}

Do you have an idea what other configs might cause this?

The header content doesn’t have any effect on this error. The error was caused by overlapping cells produced by headers that don’t match the grid. But that was fixed already.

Could you please take a look at this demo? It uses your config but it doesn’t produce any error (it used to throw an exception with the last release). Could you try to modify it so that it reproduces the problem?

Hi Dan,

You were right, today’s release fixes the issue. It must have been a NPM caching issue that it persisted for me.
Apologies for the extra work I caused!

Cheers
Leo

Hi Leo,

Great, thanks for the update!