Questionable default field priorities
1. Why don't have people address fields by default: Zip Code, Street
2. Why do they have a Twitter / Linkedin field by default?
What is this non-sensical priorization? Are people using this in real-world szenarios?
13 Replies
Are you talking about defaulty seeded excample data ?
What is this non-sensical priorization? Are people using this in real-world szenarios?Yes
I removed the dafault data and attempted to run an import. I had to cancel the import because I cannot properly assign address data to "People" because the fields are not setup. But in every single people dialogue screen space is wasted on Social Media Nonsense.
Pardon my frustration. I am 6h into this setup and very unimpressed.
What kind of import ? mail synching or csv import ?
That's alright
You will indeed need some prior metadata model configuration, if the default object and fields ( called standard ) are not fitting your needs
The address field, which is a default field on company and people should fit your need
It doesn't make any sense to me to not provide people with an address field.
How do you treat any freelancer when they are working under his/her own name? Are you setting a person up as a company?
csv import.
While trying to setup a the data model for People "Address" is not a valid field name even though I cannot use a predefined address field.
Address is a default field on people
Please review your import configuration
To map your entries to address field
There is no matching field when I look for address in the import though
@geeky.gent did you create a Address type field by any chance? I checked and People records have City field which is Text type, not Address
I didn't. I just tried to do so because I was told that it had an address field.
I believe Address is not available as a field name indeed because it used to conflict with Address field type in our graphql schema some time ago. I think this limitation does not make sense anymore. @geeky.gent your feedback on people missing address as a standard field is interesting
could you open an issue on Github regarding these two aspects
Regarding Linkedin / X links, the idea is too also demo the capabilities of the CRM, you can disable it in your Settings indeed
Thank you for your feedback. I would like to, once again, apologize for my salty tone, yesterday: I was quite frustrated with the vanilla state in which Twenty presented itself after I spent the better part of two days of getting it to work behind our reverse proxy. The fact that I have to restructure all of our costumer data to make it fit into Twenty, even after I modify the model is probably going to be a red-flag. I respect that you cannot build a product for everyone, or we end up with an SAP like mess; it just feels very disconnected from anything that I have experienced over the past 15 years and I'm pretty certain it simply isn't the right solution for the company. I don't think I will have the time to provide detailed Github issues. Here are my 2 cents:
- Have Twenty initialized with a(n optional?) so called "Demo" Instance that users can use to play around in, but initialize every new "Company" instance barebone without hipster fields like X and Linkedin. It really caused a bunch of raised eyebrows among colleagues when we discovered there were social media fields but no address fields
- The forced split between people and companies feels weird: I will give it another go tomorrow. Maybe it is just the naming convention that made me use it wrong: We have a bunch of freelance contractors which I added as people, but I couldn't properly address a member of "people" the same way that I would address a company. Addressfield, etc. Maybe it would help to rename Companies to Costumers and People to Positions to avoid the problem that I ran into. I assume that would have been the correct way to use it?
- It is problematic that I have to change the ownership of the folder for Twenty to be able to upload files and images. There are 23 other docker containers on the server and Twenty is the only one misbehaving
Hello there,
Unless I'm mistaken customer data restructuration is done through the import funnel wizard form, which is then natively supported
The forced split between people and companies feels weird: I will give it another go tomorrow. Maybe it is just the naming convention that made me use it wrong: We have a bunch of freelance contractors which I added as people, but I couldn't properly address a member of "people" the same way that I would address a company. Addressfield, etc. Maybe it would help to rename Companies to Costumers and People to Positions to avoid the problem that I ran into. I assume that would have been the correct way to use it?You can rename standard objects labels
Have Twenty initialized with a(n optional?) so called "Demo" Instance that users can use to play around in, but initialize every new "Company" instance barebone without hipster fields like X and Linkedin. It really caused a bunch of raised eyebrows among colleagues when we discovered there were social media fields but no address fieldsDefault standard metadata configuration might not fit your exact need. Adding more and more thing to the default standard metadata definition is very subjective to everyone's need. Also we're about to introduce Twenty configuration as code by the end of Q3 where
demo won't make much sense anymore. Meaning that you could search for community maintained or official twenty configuration as code to be added as an extension to your current one
It is problematic that I have to change the ownership of the folder for Twenty to be able to upload files and images. There are 23 other docker containers on the server and Twenty is the only one misbehavingPlease feel free to raise a GitHub issue and we will implement a fix
Yes, but people and companies are in the same database / list / csv of ours. They will have to be manually separated. Twenty also does not allow us to use the customer IDs that were generated by our system as customer IDs in twenty. The message I receive is, that the IDs are invalid and those items will be skipped on import. There are lots of workaround. I also pulled a new container version today and now the system isn't running anymore. When I check the container log it is either stuck migrating databases between versions or telling me that I should do it... I'm done here. This experiment has failed and is over. Thank you for your time.
Hey, unless I'm mistaken only valid V4 uuid are accepted as payload which format do you use ?
Sorry to hear you couldn't find your fit through self hosting twenty
Thanks though for the roe