Anyone knows if it is possible to keep custom field value sourcing / filtering with SDF, it tells me the object can't have ACCOUNT SPECIFIC values.

they’re account specific, so there is no way of keeping those values. you can still push with ACCOUNT SPECIFIC values, but it will allow clearing and pushing them on the deployment end if you bypass the warning with

--accountspecificvalues WARNING

The problem I see with this is that those filters exists across my accounts(most of them native), it should fail at deployment time if they don’t exist but not stop me from having them on my SDF project. Imagine a custom record with 20 custom fields and 10 of them having sourcing filters. That means that after deployment somebody needs to manually update 10 fields.

Sure, I think it is possible to use sourcing and filtering with SDF, but object can not have account specific values. So after deployment, manual update should be necessary.

Then filtering is not possible or not reliably… Example: • Custom Field -> List/Record Transaction • Filter -> Type = Sales Order • Subsidiary = X If that fails, it makes SDF for object filters useless in my opinion.

I think SDF does not support deployment of “Account-Specific Values” (ASVs) like filters, sourcing configurations, and form display settings, I can still deploy by using the flag:

suitecloud project:deploy --accountspecificvalues

But this option only allows SDF to clear or overwrite those fields during deployment so manual reconfigure is necessary after deployment.

Thank you… This is still useless, it should fail if those account specific values are not found during deployment but not before… is not that hard, it is that simple, but of course easy for oracle to not allow account specific values and force manual updates…

Sure, I am also interested in this, but not found the best solution yet. If there is any good result, please share with me. 🙂

Yeah, not ideal, but you could pull them from deployment if you aren’t updating your objects. I setup a pipeline build which only pulls in objects with changes to be merged. There is no way around having to return to update your account specific values when deployed, but you can avoid deploying the objects if no changes are necessary by keeping them out of the deploy.xml file. I haven’t updated this in awhile, but you can get an idea with this project on github: https://github.com/devnetkc/NetSuite-CustomModules-Template/tree/main/.ci/scripts

Thank you... The only way to handle this that I can think of is Playwright, I will be playing with it when I have a chance and I will let you guys know.

Hey @Ryan Valizan or anyone here, Do you know if we have something to suppress the account specific values issues in Suitecloud IDE plugin for VS code? just like you pointed out --accountspecificvalues <argument> in case of cli It take so much of time to replace those values, compare both SB and PROD list. It would be better if I can make changes for those values in PROD directly, specifically for Workflows.

I’m unaware of any way to do this.