Has anyone noticed bugs with the SDF file upload? ...
# sdf
j
Has anyone noticed bugs with the SDF file upload? Both myself and members of my team use SDF to update our sandbox account as we work. We've both noticed that, sometimes, the file upload completes successfully, the file record appears to be updated in the system, but the script is using an old version of the code. We think this might be some sort of "caching" issue (maybe not with SDF, but with NetSuite). Issue occurs 0% of the time when User uploads the file manually via UI
πŸ‘ 1
I use the node SDF CLI and my colleague uses the official webstorm plugin
e
This has been reported quite often around here since 2020.2
j
I'm using 2020.1 and my account is not yet upgraded to 2020.2
e
I'm only saying that it has been observed since the 2020.2 upgrade, not that it only impacts 2020.2 accounts
j
Understood, thank you! I'm not always on this channel. Do you happen to know if NS has it on their radar and/or a plan to fix?
e
I haven't seen any update in a while
j
@Ali Syed (NS DevTools QA) ?
a
@Jon Ostap Yes we have started investigating it. As you said we suspect it's not a problem with SDF, but we are looking at all possible causes. Thanks for bringing this up.
j
Thank you for the quick update, Ali!
d
I can vouch for some of the above as well ^ We have a custom vscode extension that uploads/updates files via
SuiteTalk
and have seen the same issue occurring intermittently, so it doesn't seem to be exclusively isolated to SDF/CLI tool
πŸ‘ 1
c
Last week it was uploading to root directories last week for people using it here.
t
I have found that if you go into the file in the file cabinet, edit it and take an empty line away press save it, forces the new script to be executed.
a
@Jon Ostap @Tim Pilgrim Are you still getting this unexpected behavior? Is this with file upload or deploy?
j
@Ali Syed (NS DevTools QA) I haven't noticed the issue recently (this week). For me, because I use the CLI, I perform an actual deploy each time I want to upload a file
t
@Ali Syed (NS DevTools QA) I haven't seen the issue in the last few days.... I was using file upload. it only appeared to be happening on 1 account for me.
r
Just happened to me. Uploaded via Eclipse plugin. Even after refreshing the transaction I was not getting the logs I just added to a script. I check to view the script file and the script was updated normally. Yet somehow it was still executing the old version. Then I edited the script in the script deployment, copy-paste, save, and after refreshing the transaction all was good. Also works if you click on edit and save the script file via the script deployment, that does the trick to update that cache or whatever it it is. Any idea about the status of this issue?
βœ”οΈ 2
b
We have the same issue
βœ”οΈ 2
r
Still happening to me. Did anyone open a support case? I normally do a lot of interactive development with NetSuite, but this is kind of ruining the experience 🀨
βœ”οΈ 1
a
Yes there is an open issue. And the relevant team is investigating it. It's an intermittent issue but its being worked on.
βœ”οΈ 2
r
Thanks for the reply.
j
One of my colleagues reported that, when he experienced this issue, the script was properly executing for others. (He could tell by the presence of logs in their names) Might a workaround be to create a separate Integration User specifically for SDF deployments? (Licenses permitting)
πŸ‘Ž 1
(not a workaround)
m
Does anyone have a defect number so that my company can get added to the case and get updates on fix?
πŸ‘ 2
b
Well I observe the same issue while not using SDF and simply uploading a file. Old code (SuiteLet) gets executed while new code definitely has been uploaded and could be confirmed by opening the file from the file cabinet. And for no reason it just works again. Took about an half hour. Wasted time
πŸ‘ 2
a
@michoel @Budy Sutjijati I reported this bug or a very similar one with some details a few weeks ago, the problem is when uploading the file NetSuite side is not being trigger to re-evaluate the script xml which I think holds the script definition, entry points etc...(my educated guess).
πŸ‘ 1
b
I just stumbled upon it again. I then edited the script via the file cabinet and saved it and that work-around worked as was pointed out by @Tim Pilgrim. Thanks
c
Happening to us as well
Saw it was listed as a U4... seems like it should be way higher up the list if you can't upload changes and rely it on it. Workaround or not. How do you even miss this not working its the 1 main function lol
πŸ‘ 1
b
Yes, so for the coming month or so we must manually upload the scripts. So don’t use an IDE or whatever, just use the NS File Editor instead think about it
πŸ‘ 1
r
Yeah, I feel the same, that is quite urgent since you might think you have updated production and the work is done, but hey, not true.
πŸ‘ 1
b
I have just updated my ongoing NetSuite support case about this and also my disagreement with the urgency level of U4.
πŸ‘ 1
d
This is killing us. Chasing our tails when we don't see fixes we implement.
r
I reported this a last week. so annoying and its a U4
Copy code
Case # 3970663 Update: "Defect 602138: script changes uploaded to NS file cabinet not showing when running the script"
e
^ I was doing some work today, deploying with SDF into a Sandbox account. On my first deployment, I observed this bug. However, after that, all subsequent changes seemed to be reflected immediately. I never had to resort to any other form of deploying.
r
I have to OPEN the file in the UI hit F5 and then save to get the changes in
e
After that first deployment "failed", I went in to the file cabinet and just did a quick edit/save of a couple relevant Files and Folders (though certainly not all of them that I changed). I don't know if that helped flush out the cache or what
r
EDIT save works for me as well
e
I only had to do that the one time
after that, I deployed about a dozen more times and all were recognized immediately
I was deploying several custom modules and a Suitelet with a Client Script attached - changes to all of them were reflected right away. I don't know why it was any different
r
I'm using Chris Recees plugin but need to "refresh/save" the suitelet everytime
e
Ah yes the problem is definitely prevalent in SuiteTalk, which that plugin relies on
I was using SDF, but the problem has definitely been evident there in the past as well
c
I've just been uploading manually is it working now? Guess I could try and not be lazy πŸ˜„
r
hello, has anyone reproduced this via the UI, that is, uploading the File via the File Cabinet's add file and not using IDE or CLI?
@Budy Sutjijati, I see that you reproduced this without using IDE nor SDF, but just by uploading the file in File Cabinet. is that correct? Did you do this via the File Cabinet's "Add File" button replacing the existing one, or did you reproduce this via clicking Edit file and manually editing the file from the UI?
b
m
FYI finally heard back from support about getting added to the defect, and apparently now it's U3
c
#progress
r
@michoel, did you heard back from support on how is it going? I am still experiencing this issue in some accounts...
j
After 2020.1 release I configured the new SDF CLI and had 0 issues until today.... just when I thought this method was reliable again, I now have to go back to copying and pasting code directly in the browser πŸ˜”
e
To be fair, this issue affects more than just SDF deployments.
That said, I haven't seen it manifest in any of the (relatively few) accounts that I work in recently
s
for the record, I've never copy/pasted to upload suitescript in the browser. Better to upload the file to the file cabinet through the UI if you're using UI
m
@Roc127 no not a word from support since, although the ticket says I'll be updated daily. It was ok for a couple days and also started playing up again on friday for me.
πŸ‘ 1
c
Support emailed me to say that their engineers had deployed a fix. It's too soon to say for sure, since our experience has been intermittent, but so far, my team has not noticed this issue in the past day with either the SDF nor the VS Code extension we use which relies on a RESTlet. We'll keep an eye on it for sure πŸ‘€
πŸ‘ 1
r
Thanks for the update! I noticed issues last week. This week not yet, but haven't done much either. Hopefully is all good and reliable now.
w
This issue just started for me yesterday...
What I find odd is that the preview link on the script record pulls the current script file, BUT that is NOT what is being run when the script fires.
πŸ‘ 1
d
ARG! Just burned my morning trying to figure out an issue ... only to find out my changes were NOT being run! This is easily the worst bug I've ever encountered in NetSuite. The hours wasted are piling up!
s
[thinking out loud] how is I haven't seen this yet myself, across quite a few different clients?
j
I think the only thing we can do is file support cases to communicate this is a widespread issue causing a lot of grief. My case # is 4008171 if anyone would like to reference it in their own case
c
NS: "But there's a workaround..."
Oh, your car broke? I guess you could just walk
w
The workaround is not working for me today - Edit the script file in the file cabinet and delete a blank line... Also tried in the script record itself.
NVM, it was my code... It sucks when you can't just rely on the tools to do their job reliably... It just throws another factor into debugging.
e
I'm seeing this issue this today on two accounts.
j
I received an email one hour ago that engineers have applied a fix for Defect 602138 (this defect we're discussion). Anyone continuing to have issues?
m
Nope, still happening for me
r
I believe I have experienced it today, but I did not further check, tomorrow I should be able to tell. But is indeed a very annoying bug.
r
Happened today to me in a SB account.
m
I have a plugin script and even after doing edit save in the UI, the changes were not reflected. Woke up this morning and now I see my changes work. Do we have to wait overnight now for changes to register?? Has anyone else encountered this with plugin scripts? Are there any know workarounds here?
Note that I’ve actually got a suitelet that calls a plugin implementation that uses a library. The code that I’ve updated is in the library and the change just isn’t being reflected even after edit / save in the UI.
j
@matty, it must not be a coincidence that I started having issues with SDF Deployments this morning for the first time since the fix for defect 602138 was applied to my account on 11/10
m
What’s so strange, is that I upload the code and initially it doesn’t work. Then I go back a few hours later and it works.
βœ… 1
Seems like I’m getting good performance now.
βœ… 1
r