Open egyptguy opened 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.
This issue has been linked to a new work item: W-11819631
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
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)