Skip to main content
Topics#Salesforce DeveloperFrage von Evan Ponter
Evan Ponter (Hostelling International USA) fragte in #Salesforce Developer
29. Sept. 2017, 04:34

Deployment is not using the flow version in the change set

Hello, I have a change set with an active flow definition included. The flow is called "Create Journals" and it is on version 27 from my Development sandbox.

Deployment is not using the flow version in the change set

When attempted to deploy this change set into another sandbox, I recieve a FlowApplication error email that indicates version 19 of that same flow causing an issue - a new required field does not have a value set. The reason I am deploying this new flow version is to set a value in that required field, which is also being introduced in this same change set. Version 19 is the current active version of that flow in the destination sandbox.

"Flow Details

Flow Name: Create_Journals

Type: Autolaunched Flow

Version: 19

Status: Active"

I can't figure out why the apex test classes would be using the latest active version in the sandbox when a newer version is included in the incoming change set, especially when the field being referenced in the error is a new field that is being created through the deployment of this incoming change set
3 Antworten
  1. Rick Upton (CrowdStrike)
    27. Aug. 2018, 19:25
    Evan, I ran into a similar problem. In a sandbox, I added a flow to a change set, made changes to the flow, then uploaded and deployed the flow to another sandbox. After deployment, the destination sandbox's flow was an old version. I fixed this issue by going back to the source sandbox, cloning the change set, removing and then adding back in the flow, and then uploading and deploying the new change set. I got this idea from a post I read sometime ago elsewhere but can't find at the moment.
Antwort schreiben...
0/9000