suitecloud object:import bugs

[kangqiwang]

Select the SuiteCloud tool where you encountered the issue

SuiteCloud CLI

Version of the SuiteCloud Tool

3.0.0

Operating system

Windwos

Node Version / VSCode Version

23.10.0

JAVA Version

17.0.13+10-LTS-268

Bug description

I use suitecloud object:import -i importing object successfully

? Do you want to import all object types? Yes
? Do you want to enter a script ID to filter your list? Yes
? Enter the full or partial script ID. customlist2463
? Select the objects you want to import customlist:customlist2463
? Select the folder where you want to import the objects. /Objects
? All the selected objects in the project will be overwritten with the objects from the account. Do you want to continue? Yes
The following objects have been imported:
    - customlist:customlist2463
Non-interactive execution:
suitecloud object:import --type ALL --destinationfolder "/Objects" --scriptid customlist2463

but when i use recommend Non-interactive execution:

suitecloud object:import --type ALL --destinationfolder "/Objects" --scriptid customlist2463

return error

$ suitecloud object:import --type ALL --destinationfolder "/Objects" --scriptid customlist2463
The imported objects will overwrite the project objects
The following objects failed with reason "Objects must be placed under the Objects folder or any of its subfolders.":
    - customlist2463
    - 
    - ```



### Steps To Reproduce

1. when run suitecloud object:import -i ,it works fine
2. try recommend Non-interactive execution fails

### Actual Output

_No response_

### Expected Output

_No response_

### Anything else?

_No response_

[Montsant19]

Hello, @kangqiwang, thank you for reporting the bug. After investigating, we have been unable to reproduce the error on our end.

However, we did notice that the error is related to a Java-specific issue, where the destination folder parameter is not starting with "/Objects". This suggests that the issue might be related to the way the folder path is being passed. One potential cause could be the presence of invisible characters in the folder path. We would recommend checking the destination folder parameter for any invisible characters, such as whitespace or special characters, that might be causing the issue.

[kangqiwang]

Hi @Montsant19, thanks for your message! I double-checked the issues—could they be related to the Windows system or the Bash terminal I'm using?

[Montsant19]

Hi, @kangqiwang. Yes, it could be. Powershell works better.