forcedotcom / devops-center-feedback

61 stars 2 forks source link

Deactivating a flow in managed package creates a change that can't be committed #212

Open egyptguy opened 1 year ago

egyptguy commented 1 year ago

Describe the bug I deactivated a managed package Flow, and source tracking created a change that has been pulled into DevOps Center. However, there is no way to commit the change to a Work Item - even if just to get it out of the list. The failed commit attempt produces an error message: "Retrieving metadata failed". When you click "Error Details" it says "Entity of type 'Flow' named 'Dynamic_Flow_Progress_Sample' cannot be found".

To Reproduce

  1. In a dev sandbox, deactivate a flow installed by a managed package.
  2. In DevOps Center, create a new Work Item.
  3. Click "Pull changes" button. The Flow will appear in the list and Operation = CHANGE.
  4. Select the change, provide a Comment, and click the "Commit Changes" button.
  5. Commit fails with the above error message. ...

Expected behavior Activation/deactivation of managed package Flows shouldn't appear as source tracked changes in DevOps Center.

Screenshots n/a

Additional context The managed package Flow I attempted to add to a dummy Work Item was from my Dynamic Flow Progress package (Salesforce Labs AppExchange package)

andresrivas-sf commented 1 year ago

Hi @egyptguy,

I am sorry to hear that you have experienced difficulties using DevOps Center.

Giving you some context, to get that list of changes, DevOps Center queries the Development org’s SourceMember object directly with a Tooling API SOQL query.

With that operation, DevOps Center gets the meta-metadata about the changes and knows what type of file changed, what type of change was it (ADD/UPDATE), when, who did it, etc.

Activation/Deactivation of managed package Flows counts as a change for the Tooling API, that’s why you will see the Flow in the list.

As a workaround, you can put that file into your .forceignore file rules in the feature branch if you don’t want it to be displayed in the list.

git2gus[bot] commented 1 year ago

This issue has been linked to a new work item: W-11819631