[BUG] TEST: Potential Bug — Cannot move items to folders of same workspace (upstream #74)

[ayeshurun]

📋 Copied from microsoft/fabric-cli#74 for AI triage testing.
Expected triage outcome: Potential Bug

---

Bug Description

Workaround of copying and remove is not good, because I want to preserve the item id

fabric-cli version

1.2.0

Python version

Python 3.12.10

Operating System

Windows

CLI Mode

Interactive mode

Authentication Method

Interactive browser login

Steps to Reproduce

Create a Fabric Workspace
Create a folder
Create some items in the root folder
Type command: fab mv WSName.Workspace/ItemName.ItemType WSName.Workspace/FolderName.Folder

Expected Behavior

Item gets moved to the workspace. Use the Fabric API: https://learn.microsoft.com/en-us/rest/api/fabric/core/items/bulk-move-items?tabs=HTTP

Actual Behavior

Not supported error

Additional Context

No response

Possible Solution

No response

[github-actions]

🅰️ Approach A (Action) — prompt-only, no codebase access

AI Assessment: Potential Bug

The issue describes an attempt to move items from the workspace root into a folder using fab mv, which results in a "Not supported" error. According to the command reference, the mv command accepts both item and folder paths and is intended for moving entities within the Fabric hierarchy. The expectation aligns with documented REST API support for item moves via the bulk-move endpoint. The error suggests either incomplete implementation or restriction in the CLI that is not documented.

The workaround (copy and remove) is unsuitable because it does not preserve item IDs, which is a valid concern given item-level tracking in Fabric. No indication is given that the operation should be unsupported for items in workspace roots, and the usage is consistent with the CLI's hierarchical path requirements (see hierarchy docs).

This issue may affect data integrity and usability if moving items is silently unsupported in cases where the REST API offers corresponding functionality.

Next Steps
🔔 Escalated to team — This issue requires team review and has been flagged for attention.

---

💡 If this issue requires the team's attention and was not escalated, you can tag @microsoft/fabric-cli-dev to notify the team.

---

🏷️ Label Decisions (testing mode — not applied)

Decision	Value
AI assessment	ai:bug-triage:potential bug
Would add help wanted	❌
Would add ai:needs team attention	✅
Would request author feedback	❌
Would remove needs triage	❌
Would auto-close	❌
Would notify team	✅

[github-actions]

🅱️ Approach B (Code Agent) — code-aware triage agent that reads the actual source code

AI Assessment: Potential Bug

Analysis

The report describes an inability to move items between folders within the same workspace using the mv command. The expected behavior is to leverage the Fabric API /core/items/bulk-move-items endpoint per the REST documentation. The CLI responds with a "not supported" error, forcing the user to copy and delete, which results in new item IDs rather than preserving the original.

Based on the codebase, cp/mv operations for items invoke cp_single_item in fab_fs_cp_item.py. There is logic for copying but raising a "not supported" error on move when not a Lakehouse or when check_command_support(Command.FS_CP) is False. The Fabric API endpoint referenced does support bulk move of items, and the reporter's scenario matches supported capabilities in the REST API and the CLI resource hierarchy.

Severity

Elevated: This affects basic item management, potentially resulting in data loss of item IDs, metadata, lineage, and references if copy-delete is used as a workaround. The actual operation is supported by the backend API and should be fully implemented in the CLI. This is a core user expectation.

Reproducibility

The issue is clear and reproducible given the commands and context. No additional information is required.

Next Steps

🔔 Escalated to team — This issue requires team review and has been flagged for attention.

---

💡 If this issue requires the team's attention and was not escalated, you can tag @microsoft/fabric-cli-dev to notify the team.

---

🏷️ Label Decisions (testing mode — not applied)

Decision	Value
AI assessment	Potential Bug
Would add help wanted	❌
Would add ai:needs team attention	✅
Would request author feedback	❌
Would remove needs triage	❌
Would auto-close	❌
Would notify team	✅

[github-actions]

🅰️ Approach A (Action) — prompt-only, no codebase access

AI Assessment: Potential Bug

The report indicates that the fab mv command returns a "not supported" error when attempting to move items between locations within a workspace. According to the CLI documentation and command reference, fab mv should allow moving items (including folders and supported item types) within the workspace hierarchy. The user correctly references the Fabric REST API's bulk-move endpoint, which is intended for such operations.

The error response suggests that either the CLI implementation does not support item moves at the workspace level, or the move operation is not correctly mapped to the Fabric API. There could also be a limitation or missing handling for certain item types or root-level moves. The fact that the workaround (copy/remove) is unsatisfactory due to item identity preservation further indicates a gap in expected functionality.

Moving items while preserving their IDs is critical for maintaining data integrity and references. This impacts usability and interoperability with external systems referencing item IDs. The lack of support for this operation via the CLI, despite its presence in the API, warrants further investigation.

Next Steps
🔔 Escalated to team — This issue requires team review and has been flagged for attention.

---

💡 If this issue requires the team's attention and was not escalated, you can tag @microsoft/fabric-cli-dev to notify the team.

---

🏷️ Label Decisions (testing mode — not applied)

Decision	Value
AI assessment	ai:bug-triage:potential bug
Would add help wanted	❌
Would add ai:needs team attention	✅
Would request author feedback	❌
Would remove needs triage	❌
Would auto-close	❌
Would notify team	✅

[github-actions]

🅰️ Approach A (Action) — prompt-only, no codebase access

AI Assessment: Potential Bug

The report describes use of the fab mv command to move an item between a workspace root and a folder, which is expected to be supported according to the Fabric REST API's bulk-move endpoint. The CLI returns a "Not supported" error, indicating either a gap in CLI functionality or incomplete backend support despite the public API documentation.

Current CLI documentation does not list known limitations for mv involving item types or workspace hierarchy moves. Expected behavior is that item IDs are preserved; a workaround via copy and remove would break this, confirming the request for moving, not duplicating.

This deviation from documented API and CLI capabilities warrants further investigation. If mv is intentionally limited, the documentation should clarify this. Otherwise, this could indicate a missing or incomplete feature.

Next Steps
🔔 Escalated to team — This issue requires team review and has been flagged for attention.

---

💡 If this issue requires the team's attention and was not escalated, you can tag @microsoft/fabric-cli-dev to notify the team.

---

🏷️ Label Decisions (testing mode — not applied)

Decision	Value
AI assessment	ai:bug-triage:potential bug
Would add help wanted	❌
Would add ai:needs team attention	✅
Would request author feedback	❌
Would remove needs triage	❌
Would auto-close	❌
Would notify team	✅

[github-actions]

🅱️ Approach B (Code Agent) — code-aware triage agent that reads the actual source code

AI Assessment: Potential Bug

The report indicates that attempting to move an item to a folder within the same workspace fails with a "Not supported" error, despite the bulk-move-items API being available. In the implementation (fab_fs_cp_item.py), the cp_single_item function only permits move/copy operations if the item type supports the command or is a Lakehouse, otherwise raising an error. Items like reports and datasets do not support this operation currently, even though the REST API includes a bulk-move endpoint.

The reporter’s use-case—preserving item IDs and metadata during a move within the workspace—is reasonable and aligns with the API’s capability. The current CLI behavior diverges from expected functionality and documented API support. The workaround (copy then delete) is not appropriate for most scenarios, especially where item ID continuity matters.

This issue should be further investigated for alignment between CLI functionality and Fabric API capabilities, particularly for the mv command. If the CLI intentionally restricts this operation, justification should be documented. Otherwise, support for intra-workspace moves should be implemented.

Next Steps

🔔 Escalated to team — This issue requires team review and has been flagged for attention.

---

💡 If this issue requires the team's attention and was not escalated, you can tag @microsoft/fabric-cli-dev to notify the team.

---

🏷️ Label Decisions (testing mode — not applied)

Decision	Value
AI assessment	Potential Bug
Would add help wanted	❌
Would add ai:needs team attention	✅
Would request author feedback	❌
Would remove needs triage	❌
Would auto-close	❌
Would notify team	✅