https://netsuiteprofessionals.com logo
Join Slack
Powered by
once again SDF proves to be utterly braindead when...
# sdf
s
once again SDF proves to be utterly braindead when it comes to working out order-of-deployment and/or circular dependencies upon deploy.
☝️ 1
🤯 1
a
@Alvin Kiho Kim (NS SDF PM) This issue keeps coming from several users.
☝️ 1
w
My case a few weeks back with similar issues came to a dead end yesterday. Couldn't be replicated by support, the project had too many dependencies. https://netsuiteprofessionals.slack.com/archives/C42JX79UZ/p1616064888061600?thread_ts=1616009026.030700&channel=C42JX79UZ&message_ts=1616064888.061600
s
I find myself frequently needing to manually control the order of lines in 
deploy.xml
and SDF just can't handle circular dependencies
one case I just ran into is a search that depends on a custom record. That custom record in turn relied on that search for a sublist. (circular dependency)
👍 1
I really wish SDF could recognize that the dependencies would have been satisfied if it created both those objects then checked for issues, or something like that. If each object.xml file is the smallest granularity SDF can process then that may need to be improved?
it's especially frustrating since 
--dryrun
shows all green as if we're good to go
when doing the actual deploy, I had to change (by hand) probably 10 things between deployment order and circular dependencies
👍 1
so much for SDF '_automation_'
😆 1
though I admit it's still better than bundles and better than doing it manually. But I feel like if I get an 'all green' with 
--dryrun
I should also get all green when doing actual deployment.
c
It's a nightmare. Can't use the "Copy to account" feature on 95% of the customisations we want to copy from sandbox to production because it can't actually detect the circular dependencies & just times out with an internal error after a while. Reported it as a defect 18 months ago & it got switched to an enhancement. Terrible
🤯 1
I've got a big project that is going to take me an entire working day to manually deploy because of this. Not pleased
👍 1
s
I find myself manually downloading xml files in dependency order, and sometimes pushing files to PROD so SDF doesn’t freak out.
@CD and @stalbert Also, with workflows.. a cautionary tale.. I 
spent more time failing
 to make it work, than it ultimately took me to 
record a screen share
 of every state, action, and transition of the WF in SB1, and 
manually re-create it
 in SB2. 
I highly doubt this is what they had in mind when they set out to build SDF.
w
@suitedev. Pro-tip. Login to both accounts and have each account on separate monitors. 😂
s
@Watz good idea.. I'll try that next time!
@Watz either way, neither option gets us closer to SDF utopia... :/
w
Yeah, the god-tip is to fix SDF.
Open in Slack
PreviousNext
Powered by