Did Netsuite roll out an update last week changing...
# suitescript
e
Did Netsuite roll out an update last week changing the behavior of file name collisions in the File Cabinet? Seems like new files created/moved into a folder results in the existing file matching the same name being wiped out and deleted. Is that possible? Began last Friday, and NS generally pushes out fixes/patches on Fridays.
b
always done that
e
i beg to differ; i believe not, because we had a bundle out for a long time that relied on a failure to move files to a new cabinet location where the name colliding with an existing file… The logic was, 1. move the file to destination location 2. check the file folder to see if the move worked 3. if not, rename, repeat the move this started failing on Fri
b
what did the code look like
e
i opened a case with ns support. sure enough, an e-fix was released on 6/8. Errors first reported on 6/9. pseudocode: Load file; if folder is incorrect, set folder, save Load file again; if folder is still incorrect, change filename (add timestamp) and set folder, save. That was the way it worked. Now, if i try to modify a folder in the UI and save I get an error if there is a filename collision. However, in script, it continues and saves the file, and REMOVES the original.
b
file.create is the one that automatically overwrites
file.load is the one that silently ignores
file.copy is the one that gives you choices
evidently that made this more consistent and made file.load also automatically overwrite
t
hello, i notice the same issue. My file.create with the same file name in the same folder is not always overwriting the file content anymore.