I did an sdf deployment which updated some setting...
# sdfd
dbaghdanov
07/20/2018, 1:41 AMI did an sdf deployment which updated some settings,
<loglevel>DEBUG</loglevel><loglevel>ERROR</loglevel>m
Mariano Saenz (NS Eng Lead)
07/20/2018, 8:54 PMSDF should not be reordering scripts. Are you reproducing this consistently? Can you check if updating the record in the UI also changes the order?
d
dbaghdanov
07/20/2018, 8:56 PMI haven't had a chance to try different scenarios yet. I seem to remember that if i modify a script deployment in the UI that it did not re-order script execution.
m
Mariano Saenz (NS Eng Lead)
07/20/2018, 8:57 PMYou are right, I would expect neither the UI or SDF to re-order the script. However a bug could have been introduced recently. Let me know what you find if you get a chance to check
d
dbaghdanov
07/20/2018, 8:59 PMI do vaguely remember this same situation happening about a year ago, where I did an SDF deployment and it had also reordered scripts
dbaghdanov
07/20/2018, 8:59 PMso just for disclosure, this is specifically the Sales Order record, and we do have a ridiculous 20 user event scripts running on it
dbaghdanov
07/20/2018, 8:59 PMand it's also appeared to affect client side script ordering
dbaghdanov
07/20/2018, 9:00 PManyway, hopefully I'll have time soon to try a few scenarios
m
Mariano Saenz (NS Eng Lead)
07/20/2018, 9:00 PMhmmm… that’s odd. OK, thanks for the info
Mariano Saenz (NS Eng Lead)
07/20/2018, 9:30 PMOK, we reproduced. We are working on a fix.
d
dbaghdanov
07/20/2018, 9:31 PMoh good i'm not crazy
m
Mariano Saenz (NS Eng Lead)
07/20/2018, 9:31 PMnope 😄
d
dbaghdanov
07/20/2018, 9:34 PMso what does "working on a fix" mean? 2018.2? 2019.1? next week?
m
Mariano Saenz (NS Eng Lead)
07/20/2018, 9:37 PMIt can mean many things - but in this case it will either be 2018.2, or possibly an e-fix for 2018.1 - depends on the issue analysis being done now
d
dbaghdanov
07/20/2018, 9:37 PMok cool, thanks
3 Views