New columns on standard objects #7816
Replies: 9 comments 1 reply
-
Same comment as: #2977 |
Beta Was this translation helpful? Give feedback.
-
We have introduced all the tooling required to handle this one. |
Beta Was this translation helpful? Give feedback.
-
I'll try to work on, please assign me, sir🙇 |
Beta Was this translation helpful? Give feedback.
-
I can work on this as well @Bonapara @FelixMalfait |
Beta Was this translation helpful? Give feedback.
-
Thanks a lot @pacyL2K19 I removed the "good first issue" tag as I think we should probably tackle all field updates at the same time (they are several related issues). |
Beta Was this translation helpful? Give feedback.
-
@FelixMalfait should we close this ticket? |
Beta Was this translation helpful? Give feedback.
-
@charlesBochet I'd like to bring it back when we consider data enrichment. It's not that useful I agree but there are a few things that I would re-use / based on analysis I did when looking at various data enrichment providers. I closed most related issues |
Beta Was this translation helpful? Give feedback.
-
company
industry
see old issue: #3048
employeesRange
annualRevenue
Step 1: rename annualRecurringRevenue to annualRevenue
Step 2: disable this field by default for newly created workspace
Step 3: create a new field, enabled by default on all new workspaces, called annualRevenueRange, of type enum, with values:
$0-$1M
$1M-$10M
$10M-$50M
$50M-$100M
$100M-$250M
$250M-$500M
$500M-$1B
$1B-$10B
$10B+
description
A brief summary/description of the company.
Short text (typically a paragraph).
Enabled by default but not visible on default view.
founded
year
funding
Need to add 3 fields, disabled by default:
related companies
many-to-many
person
Birth date
Birth year
Gender
male/female
previous experiences
many-to-many with people
Language
Array of values coming from an enum.
Disabled by default.
Take values from:
https://docs.peopledatalabs.com/docs/language-names
Beta Was this translation helpful? Give feedback.
All reactions