Describe the bug
After exporting a solution with pac-cli tools and using pac solution unpack, the attributeimageconfigs files are generated with an incorrect file extension, i.e. .yml instead of .xml.
When packing the solution, this causes the import to fail. If the extension of the affected files is manually changed to .xml and the solution is packed again, the import completes successfully.
To Reproduce
Steps to reproduce the behavior:
- Export a solution using pac-cli
- Unpack the solution using:
pac solution unpack -z $zipFile -f $sourcePath
- Refer to the screenshot below (VS Code)
Expected behavior
The file extension should match the file content, i.e. the files should have .xml as extension.
Screenshots
VS Code indicating the change (add/delete), showing the file content as XML while the file extension is .yml
Desktop (please complete the following information):
- OS: Windows 11 25/H2
- VS Code with Power Platform Tools (auto-update) - version 2.0.145
Additional context
n/a
Describe the bug
After exporting a solution with pac-cli tools and using
pac solution unpack, the attributeimageconfigs files are generated with an incorrect file extension, i.e. .yml instead of .xml.When packing the solution, this causes the import to fail. If the extension of the affected files is manually changed to .xml and the solution is packed again, the import completes successfully.
To Reproduce
Steps to reproduce the behavior:
pac solution unpack -z $zipFile -f $sourcePathExpected behavior
The file extension should match the file content, i.e. the files should have .xml as extension.
Screenshots
VS Code indicating the change (add/delete), showing the file content as XML while the file extension is .yml
Desktop (please complete the following information):
Additional context
n/a