New columns on standard objects

[FelixMalfait]

company

industry

see old issue: #3048

employeesRange

• 1-10
• 11-50
• 51-250
• 251-1K
• 1K-5K
• 5K-10K
• 10K-50K
• 50K-100K
• 100K+

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:

• last_funding_date latest_funding_stage (d/m/y)
• total_funding_raised (currency field)
• latest_funding_stage (values)

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

[charlesBochet]

Same comment as: #2977

[charlesBochet]

We have introduced all the tooling required to handle this one.
Ready to be picked

[16dango]

I'll try to work on, please assign me, sir🙇

[FelixMalfait]

Thanks!

[pacyL2K19]

I can work on this as well @Bonapara @FelixMalfait

[FelixMalfait]

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).

[charlesBochet]

@FelixMalfait should we close this ticket?

[FelixMalfait]

@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