You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Select the SuiteCloud tool where you encountered the issue
SuiteCloud Extension for VSCode
Version of the SuiteCloud Tool
1.6.2
Operating system
Windows 10 Pro
Node Version / VSCode Version
v18.15.0
JAVA Version
java 17.0.5+9-LTS-191
Bug description
When uploading a file or working with folder names, the casing of the file/directories is determined by the deploy.xml file. This behavior impacts both the filenames and the folder names.
Bug Details:
Affected Area: SDF Deployments Symptoms: When uploading files or folders, the case (capitalization) is not preserved as it appears in the file system. Instead, the case is dictated by the settings in the deploy.xml file. Impact: This can lead to inconsistencies between the original file/folder names and the uploaded versions, potentially causing confusion, misalignment with naming conventions, or even errors in case-sensitive systems.
Steps To Reproduce
Create a New SuiteCloud Project: Start by initiating a new SuiteCloud project within your development environment.
2.Create a New SuiteScript File: Create a new SuiteScript file (it can be of any type) and name it test.js.
3.Update deploy.xml: Open the deploy.xml file and update it to deploy the file as tEsT.js. Make sure the casing is exactly as shown.
4.Deploy the File: Deploy the file to the target environment, following the standard deployment process.
5.Verify the Filename on NetSuite: Navigate to the location where the file was deployed on NetSuite. You will observe that the file is named tEsT.js, reflecting the case specified in the deploy.xml, rather than the original test.js.
Actual Output
The file will be named tEsT.js on NetSuite, reflecting the exact casing specified in the deploy.xml file, rather than the original filename test.js.
Expected Output
The file should be named test.js on NetSuite, consistent with the original filename and independent of the casing specified in the deploy.xml file. The deployment process should preserve the original filename in the src folder rather than adopting variations in casing from other sources.
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Select the SuiteCloud tool where you encountered the issue
SuiteCloud Extension for VSCode
Version of the SuiteCloud Tool
1.6.2
Operating system
Windows 10 Pro
Node Version / VSCode Version
v18.15.0
JAVA Version
java 17.0.5+9-LTS-191
Bug description
When uploading a file or working with folder names, the casing of the file/directories is determined by the deploy.xml file. This behavior impacts both the filenames and the folder names.
Bug Details:
Affected Area: SDF Deployments
Symptoms: When uploading files or folders, the case (capitalization) is not preserved as it appears in the file system. Instead, the case is dictated by the settings in the deploy.xml file.
Impact: This can lead to inconsistencies between the original file/folder names and the uploaded versions, potentially causing confusion, misalignment with naming conventions, or even errors in case-sensitive systems.
Steps To Reproduce
2.Create a New SuiteScript File: Create a new SuiteScript file (it can be of any type) and name it test.js.
3.Update deploy.xml: Open the deploy.xml file and update it to deploy the file as tEsT.js. Make sure the casing is exactly as shown.
4.Deploy the File: Deploy the file to the target environment, following the standard deployment process.
5.Verify the Filename on NetSuite: Navigate to the location where the file was deployed on NetSuite. You will observe that the file is named tEsT.js, reflecting the case specified in the deploy.xml, rather than the original test.js.
Actual Output
The file will be named tEsT.js on NetSuite, reflecting the exact casing specified in the deploy.xml file, rather than the original filename test.js.
Expected Output
The file should be named test.js on NetSuite, consistent with the original filename and independent of the casing specified in the deploy.xml file. The deployment process should preserve the original filename in the src folder rather than adopting variations in casing from other sources.
Anything else?
No response
The text was updated successfully, but these errors were encountered: