-
1. Re: I have a dangerous question:
Ashutosh DeshpandeJul 9, 2019 8:48 AM (in response to Phillip Brockhaus)
1 of 1 people found this helpfulThe question itself is not "dangerous", but you are right ... the results can be "dangerous", if you do that directly in database. It may work in some cases where there are not many references to the field, and also in most cases the references are stored by server as field ID, rather than field name. However, this is still not recommended.
I understand the need to update a lot of things in bulk. I suggest you write an AR API program to get forms/fields in bulk, check existing names and if it matches __c, you can rename with the API program itself. If you are familiar with AR APIs, it will be fairly quick and without any errors - basically producing the same effect as dev studio, which uses exactly the same APIs.
Hope this helps.
-
2. Re: I have a dangerous question:
LJ LongWingJul 9, 2019 9:16 AM (in response to Phillip Brockhaus)
4 of 4 people found this helpful -
3. Re: I have a dangerous question:
Phillip Brockhaus Jul 9, 2019 10:58 AM (in response to Phillip Brockhaus)Thanks Both of you.
I think that is EXACTLY what I was looking for LJ. We have a lot of custom SQL, so for now I'll exclude data bearing fields, but I think this will make my life a lot easier.
-
4. Re: I have a dangerous question:
Phillip Brockhaus Jul 9, 2019 11:22 AM (in response to LJ LongWing)I'm already done with all the fields that do not require investigation. Thanks again.