forcedotcom / forcedotcom/devops-center-roadmap

Flow API Version Not Respected V49 showing as V54

Open
#145 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
27
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Flow failed to deploy due to Property 'nameSegment' not valid in version 54.0

I recently was blocked from doing a deployment of a flow to production due to an api version discrepancy. The system was reporting that the flow that I was deploying was on version 54 despite the flow specifying it was on version 49. This prevented the xml from being deployed as it contained a 'nameSegment' which is no longer supported in later api versions.

I believe this issue was introduced with the DevOps Center update 6.4 that was released on July 22nd. I believe that the sfdx-project.json file's api version is overriding the value of the flow's xml with the api version contained within it.

(W-14179354, W-15247534: We support the latest API version, by default, unless a different version is specified as the sourceAPIversion in the sfdx-project.json file. If not specified, we support the latest version.)

I was able to work around the issue by updating the api version of the affected flows to a newer api version where the name segment is no longer present to fix the issue.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.