how do you manipulate the xml when sdf won’t deploy due to ACCOUNT_SPECIFIC_VALUE? i’ve noticed that when you add a filter or default values the SDF really has a hard time during deployment, has anyone come up with a workaround?

I'm in the process of moving a subsidiary and all of its customizations off of a OneWorld account into its own stand-alone NetSuite instance and running into this heavily. I've found my only recourse is to either remove the parameters/filters with ACCOUNT_SPECIFIC_VALUE and remember to go back to them after the deploy and re-add manually, or find the correct values in the new account and add them to the XML before deploying. I most often choose the latter. Not sure if there's a better way, but that's been my method so far.

Thanks @Jordan Patterson it is extremely difficult to deal with these values when you have multiple attributes to the field. examples: default values, filters, record is parent, list/record sourcing, hiccups on any of these things and a simple record update via sdf becomes impossible if you have a few fields that have any of these attributes configured. and you can tell that the beta Copy to Account functionality is no better probably using the same engine as SDF

Yup, you're right. It's definitely not easy. Not sure the right answer, tho? is it better that those just be left blank in the new account when deployed to be updated manually later?

seems like that’s the best practice for dealing with the current broken functionality. it can only be moved without any problems if its a bare record with field names and ids but no other attribute besides help/description

apologies as i'm new to SDF - do you mind sharing how exactly you would update the XML for an account-specific value?

do you not have the option to change the check for account specific value from ERROR to WARNING? I found this as a life saver working with multiple devs on the same SDF projects when testing in SB and migrating to prod

@Vince I saw documentation on that but only for Eclipse - it may be available in Webstorm as well but I haven't found it

^yes only in eclipse as I know as well - my colleague could not find it on Webstorm