[BUG]: sf project delete source -m "Flow:XYZ` returns insufficient access rights on cross-reference id

オープン
  • 何か問題がありますか？
#3,684 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
65/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
node.js
領域
cli

調査の方向性

Start by locating the implementation and tests for the sf project delete source command, then trace how it handles Flow components and their versions. Reproduce with the provided steps using an unactivated screen flow. Done means the command deletes the flow and all versions without the cross-reference access error.

索引モデルが issue の本文から書いたものです。

説明

area:mdapi investigating validated
Before You Submit
  • I'm using the latest version of Salesforce CLI
  • I've searched the existing issues
  • I've run sf doctor to diagnose common issues
Related Issue

No response

Command

sf project delete source

Org Type

Sandbox

Did this work before?

No, this is a new bug

Last Working Version

No response

Summary

When I'm trying to delete Flow entirely, it always return insufficient access rights on cross-reference id even though I'm an admin and I have all rights to the flow.
I can delete the same flow without any issues from the UI.

sf project delete source -r -m "Flow:FO_Sampling_Flow"

Component Failures [1]
┌───────┬──────────────────┬──────────────────────────────────────────────────┐
│ Type  │ Name             │ Problem                                          │
├───────┼──────────────────┼──────────────────────────────────────────────────┤
│ Error │ FO_Sampling_Flow │ insufficient access rights on cross-reference id │
└───────┴──────────────────┴──────────────────────────────────────────────────┘
Repository to Reproduce

No response

Steps to reproduce
  1. Create screen flow "TestDeleteIssues". It doesn't need to be activated, just saved.
  2. sf project delete source -r -m "Flow:TestDeleteIssues"
  3. Notice error
Expected Result

Flow and all flow versions should be deleted., regardless of activation status.

Actual Result
Component Failures [1]
┌───────┬──────────────────┬──────────────────────────────────────────────────┐
│ Type  │ Name             │ Problem                                          │
├───────┼──────────────────┼──────────────────────────────────────────────────┤
│ Error │ TestDeleteIssues │ insufficient access rights on cross-reference id │
└───────┴──────────────────┴──────────────────────────────────────────────────┘
Error Message
insufficient access rights on cross-reference id
System Information
{
  "architecture": "win32-x64",
  "cliVersion": "@salesforce/cli/2.157.8",
  "nodeVersion": "node-v24.20.0",
  "osVersion": "Windows_NT 10.0.26300",
  "rootPath": "C:\\Users\\piotr\\AppData\\Roaming\\npm\\node_modules\\@salesforce\\cli",
  "shell": "cmd.exe",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 4.0.6 (core)",
    "@oclif/plugin-commands 5.0.6 (core)",
    "@oclif/plugin-help 7.0.6 (core)",
    "@oclif/plugin-not-found 4.0.7 (core)",
    "@oclif/plugin-plugins 7.0.13 (core)",
    "@oclif/plugin-search 2.0.9 (core)",
    "@oclif/plugin-update 5.0.10 (core)",
    "@oclif/plugin-version 3.0.7 (core)",
    "@oclif/plugin-warn-if-update-available 4.0.5 (core)",
    "@oclif/plugin-which 4.0.6 (core)",
    "@salesforce/cli 2.157.8 (core)",
    "agent 2.2.3 (core)",
    "apex 4.4.4 (core)",
    "api 2.0.24 (core)",
    "auth 6.0.0 (core)",
    "code-analyzer 5.16.0 (user)",
    "data 5.1.24 (core)",
    "deploy-retrieve 4.3.2 (core)",
    "info 4.0.22 (core)",
    "lightning-dev 6.2.19 (user)",
    "limits 4.0.6 (core)",
    "marketplace 2.0.23 (core)",
    "org 7.0.10 (core)",
    "packaging 3.0.17 (core)",
    "schema 4.0.16 (core)",
    "settings 3.0.22 (core)",
    "sobject 2.0.20 (core)",
    "telemetry 4.2.4 (core)",
    "templates 57.5.0 (core)",
    "trust 4.0.28 (core)",
    "user 6.0.6 (core)",
    "sfdmu 5.8.0 (user)",
    "sfdx-git-delta 6.45.1 (user)"
  ]
}
Additional Information

No response

Screenshots or Log Files

No response

主要言語
言語のデータがありません
スター
575
フォーク
80
平均マージ
5時間 58分
マージ済み PR（30日）
4

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

forcedotcom/cli のほかの issue

forcedotcom/cli の issue をすべて見る

似ている issue

CLI の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。