Is setting a blank DSS value the same as removing it? How to remove DSS using prpcServiceUtils

Hi we have a prconfig DSS that we want to remove across all of our 80+ on-premises environments. The thing is that we have to use prpcServiceUtils for that. As far as I know, that tool allows to set a DSS but not to remove it. Am I wrong? The other question is if I have a prconfig setting like:

{ 
         "pySetting":"",
         "pyPurpose":"prconfig/{xxx}/default",
         "pyOwner":"Pega-Engine"
}

Would setting a blank value would be equivalent to manually removing a DSS from the platform?

@Paweł Adamczuk

no, setting a DSS to blank is not the same as removing it; the platform still sees the record and it can override defaults. prpcServiceUtils only supports updateDASS (it updates values via JSON) and doesn’t provide a delete operation. A real fix is to delete the Data-Admin-System-Settings instance or automate deletion using prpcUtils/direct DB access if that’s approved in your shop. Pega’s own guides tell you to delete certain DSS after upgrades, so deletion is the supported path, not blanking. Also, many prconfig/… settings are read at startup; plan a node restart to be safe after removal. If you script it, don’t try to “SQL-flip” pySetting only DSS values live in a BLOB and you can get out of sync; use Pega tools or re-save the instance. Bottom line: don’t blank it delete it properly (Dev Studio/prpcUtils), then clear caches or restart where required.

@Sairohith Thank you very much for such a detailed explanation.