Skip to main content
New Idea

Default/system fields able to be either not visible or renamed

abeck0625
tmorgan
romihache
+6
  • abeck0625
    abeck0625
  • gschardan
  • tmorgan
    tmorgan
  • romihache
    romihache
  • jkolle
  • RoxConroy
    RoxConroy
  • alizee
    alizee
  • Harika Singadi
  • stevepost
    stevepost
  • Lulu_Zhang
    Lulu_Zhang
  • vartan.kourshounian
    vartan.kourshounian

manda.edmonds

It would be fantastic if users could either a) make fields inaccessible or b) rename fields to indicate they will not be used.

 

Specific example:

Billing address is a default field at the company level.  In our organization, we are unable to use this (since GS cannot support pulling this field in from Salesforce’s default item).  As a result, I had to build each field (i.e., street address, city, state, etc).  

 

In the current state, I cannot realistically use this field, which leaves me 2 options:

  1. Have an empty field required to be visible for users who might be building out reports or
  2. Create a rule to update this field after concatenating a whole slew of fields together just to populate a field that ultimately is not needed (and eat up valuable rule running time).

 

Thanks!

0 replies

Be the first to reply!

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings