ProGantt Support

Ensure all four required fields are bound: Task ID, Task Name, Start Date, End Date. Check that date columns are typed as Date in Power BI (not Text). If all four are bound and dates are correct, look for data quality issues: Start Date > End Date, or null values in required columns.

ProGantt renders a milestone for any task where Start Date equals End Date. Ensure End Date is strictly after Start Date for non-milestone tasks. Also check whether the Milestone Type field is bound because any non-blank value in that field triggers milestone rendering regardless of dates.

The dependency string must be formatted as [ID][Type] or [ID][Type][+/-][N]d, for example 3FS or 7SS+2d. IDs must match Task ID values exactly, including data type. Multiple dependencies are comma-separated, such as 3FS,7SS+2d.

Verify that the Task Category role is bound in the Build visual tab. The Category Styles section only appears in the Format panel after a category field is bound. If the section is visible but styles have no effect, confirm your data has non-blank Task Category values.

Verify Color by Field is turned on in Format panel -> Tasks and Summaries. Then check Color Rules 1-8. Each active slot needs a Rule Value that exactly matches the value in your data. Leave unused slots blank.

Swimlanes require the Task Category role to be bound. Enable Show Swimlanes in Format panel -> Swimlanes and ensure your data has non-blank Task Category values.

The legend reads colors from Category Styles. Once Task Category is bound, expand the generated category groups under Category Styles and set a distinct Bar Color for each category.

This message appears with partial binding. If all required fields are bound and the message persists, check for data quality issues such as null Task IDs, parsing failures, or date values that Power BI still reads as text.

Verify Parent ID values match Task ID values exactly and use the same data type. If Parent ID is number but Task ID is text, matching fails and tasks appear at root level.

CPM is based on the dependency network you define. Tasks not connected by dependencies form isolated chains and may not be on the overall critical path. Also verify dependency strings reference valid Task IDs.

ProGantt accepts either decimal values (0.0-1.0) or whole numbers (0-100). If values are interpreted incorrectly, check the column type in Power Query and use Whole Number when your source data is 0-100.

For best results, scroll the Gantt to the beginning and use Zoom to Fit before exporting. Very large datasets may require lower zoom to include all tasks in a single export.