ProRoadmap Support

ProRoadmap requires exactly three fields: Item Name, Start Date, and End Date. All three must be bound before the roadmap renders. Check that Start Date and End Date columns are set to the Date data type in your Power BI model — not Text or DateTime. Right-click the column in the Fields pane and set Data type → Date.

The Status Rules card only appears when the Status data role is bound. Once bound, open the Status Rules card and enter the exact status values from your data in the Rule value fields — matching is case-sensitive. For example, if your data has On Track but you typed on track, the rule will not match.

Swimlanes require two conditions to be met simultaneously: a Pro license must be active, and the Team / Area data role must be bound. If either is missing, the Swimlanes card is hidden. Verify your license status in Power BI Service and ensure Team / Area has a field bound to it.

Hierarchy requires both Item ID and Parent ID to be bound. Item ID must be a unique identifier for each row. Parent ID values in child rows must exactly match the Item ID of their parent — check for case differences, leading/trailing spaces, or mismatched data types between the two columns.

Check three things: (1) The items may be filtered out by a page-level slicer or report filter. (2) The Free tier renders a maximum of 50 items — items beyond that limit are silently dropped. Upgrade to Pro or reduce the data scope. (3) Items with Start Date after End Date are normalized automatically, but if both dates are null or invalid, the row is excluded.

Milestones require either (a) Start Date equals End Date, or (b) the Item Type field is bound and the row's value is milestone or release with equal dates. Also confirm that Show milestones is toggled on in the Milestones & Releases format card. If both conditions are met and milestones still do not appear, check whether a date slicer is excluding those specific dates.

Two settings must be active: the Goal / OKR data role must have a field bound to it, and Show Goal / OKR must be toggled on in the Name Column format card. The subtitle only appears on regular item rows — theme rows and swimlane header rows do not show goal subtitles.

Category Appearance groups are generated dynamically from the unique values currently in the Team / Area field. If your data has changed or a filter excludes some team values, those groups will not appear. The groups are case-sensitive — Growth and growth would appear as two separate groups.

Cross-filtering works most reliably when Item ID is bound — this lets ProRoadmap build a precise Power BI selection ID for each row. Without Item ID, selection falls back to row-index-based logic which may not match after data refreshes. Also confirm that the field you are filtering on is from the same data model table as the target visual.

License checks run asynchronously after the first render — there may be a brief moment where the visual shows Free behavior before the check completes. If the watermark persists after reloading the report, verify that your AppSource subscription is assigned to your Power BI user account and that you are testing in Power BI Service (not Desktop). Some embedded and Sovereign Cloud environments do not support the Power BI licensing API. Contact support@vectras-software.com if the issue continues.