Predecessors and Successors do not work when using SaveOptions for Excel

Aspose.Tasks Product Family
1

Predecessors and Successors do not work when using SaveOptions.
I am using PostTaskDocumentWithFormat API with saveoptions in golang, trying to display Predecessors and Successors but it is not working. here is the sample used.

   type (
	Column = struct {
		Type     string
		Name     string
		Property string
		Width    int
	}
	View = struct {
		Columns []Column
	}
	saveOptions = struct {
		View View
	}
)

so := saveOptions{
	View{
		[]Column{
			{"GanttChartColumn", "ID", "Id", 120},
			{"GanttChartColumn", "Active", "IsActive", 120},
			{"GanttChartColumn", "Name", "Name", 120},
			{"GanttChartColumn", "Duration", "Duration", 120},
			{"GanttChartColumn", "Start", "Start", 120},
			{"GanttChartColumn", "Finish", "Finish", 120},
			{"GanttChartColumn", "Predecessors", "Predecessors", 120},										 
                         {"GanttChartColumn", "Successors", "Successors", 120},
		},
	},
}
opts := &requests.PostTaskDocumentWithFormatOpts{
	Name:        "data1.mpp",
	SaveOptions: so,
	Format: string(models.XLSX_ProjectFileFormat),
	Folder: optional.NewString(remoteBaseDataFolder),
}
data, response, err := tasksApi.PostTaskDocumentWithFormat(ctx, opts)
if err != nil {
	return
}

can you tell me what properties are provided for the GanttChartColumn view and how to display Predecessors and Successors?

2

@said1024 ,
we are analyzing this issue and request you to spare us little time. We will write back here soon to share the feedback.

3

Thanks for your response, hope to have a solution

4

@said1024,
we need do the fix on our side.

The following new ticket was opened in our internal issue tracking system and we will deliver the fix according to the terms mentioned in Free Support Policies.

Issue ID(s): TASKSCLOUD-875

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

5

Is there another solution to export to Excel with the Predecessors and Successors column?

6

@said1024 ,
we didn’t find the workaround for the issue.