Does anyone have an approach they are using for se...
# sdf
c
Does anyone have an approach they are using for secret fields and deploying/updating? Whenever we deploy, the secret fields get mangled and we have to re-enter everything. Maybe the best approach is to not include the secret fields in SDF and just make it part of the setup process?
e
Do you mean like Secrets Manager fields?
or encrypted "password" type custom fields?
We use several of the former, but we don't include any of them in SDF
but we're also not distributing a SuiteApp
c
its just a secrets field. Nothing is stored in it initially. If I try to update an account that has it filled out, then its basically overwriting the field and doesn't retain the user value.
Im leaning towards maybe not including them and just having the user set it up so its a non-issue. It takes like 2 min to do it as part of the setup.
d
@creece secrets field? Like password?
c
Setup --> Company --> API Secrets
d
OH. Are you trying to distribute a secret?
I can help with that
1st suggestion is to create your secret in your deployment account (as you cannot deploy your project to the same account that you created the secret in .. much like integration records)
c
I thought we were deploying one but it looks like we are not. For some reason when we deploy our app, its mangling the secret fields so I need to look into this a little more.