La fonction de suggestion automatique permet d'affiner rapidement votre recherche en suggérant des correspondances possibles au fur et à mesure de la frappe.
I would like to have the ability to create multi-language property names for internal use.
My company database is entirely in English and my Dev, Product, Data and other more technical users prefer to use HubSpot in English as well.
However, Sales, Customer Success, Collection, and Customer Experience teams prefer to use HubSpot in Portuguese (our country's main language).
HubSpot default properties usually are translated from English to Portuguese, but we use a lot of custom properties because of our business needs and in these properties, we can't auto-translate based on our employee's HubSpot language. This generates a little friction because technical users want our CRM property naming like our database (English) and operational users want our CRM property naming in our country's language.
If a could manually insert the default property name (English) and the translated one (Portuguese) this problem would be solved.
This would be a great feature to have as we have multiple users in various countries. Surprised that it will translate everything else but custom properties. Definitely a disadvantage not to have that
After Hubspot being used in more roles than just marketing automation the ability to provide multi-language capable APIs and build services around it is becoming more important every day. Now we need to copy the descriptions and labels for other languages than English outside of Hubspot and maintain also it there.
I hope that there would eventually be some progress on this.
👋 Hello! I'm Rachel from the HubSpot Product team. Sharing an update - we have a beta in its early stages called Translate custom CRM data. In the current stage of the beta, you can create translations for custom properties, excluding custom pipeline and custom pipeline stage translations. During the beta, the ability to translate other custom data such as custom pipeline and pipeline stages will be added.
This is an Enterprise feature. To learn more details, or to join the beta, please contact your Customer Success Manager so they can request beta access on your behalf.
Hey @FelipeFelix and @rwebb1 just built this guide that could solve your problem! You shouldn't follow it until the end since it then sends the property and build a note. But the first 2 steps simply send a property to DeepL (free account) and translate the property - you should change the custom code that requests the DeepL API to translate everything in english to translate to portuguese.
@rwebb1 where would you guys like feedback for the beta? In our HubSpot Sandbox the Lifecycle Phase got translate to wierd german translations. For example: Lead is translated to "Blei" which is german for the metal lead 😉
Hi all! There should be a CSAT survey in-app for beta users where you can leave feedback. Another way to provide feedback is to communicate to your CSM, who can pass feedback to my team diectly. If you are in the beta and have a pressing question or issue, please reach out to the Support team, that is the fastest way to get issues resolved.
Pipeline stage properties translations (including lifecycle stage) are not yet included in the beta. Additionally, this beta will only impact pipeline stages that can be edited (it will not impact any translations of default pipeline stages provided by HubSpot that cannot be customized).
Hi everyone - a quick update - Enterprise customers can now opt into the beta: Translate custom CRM data directly via Product Updates (no need to request via a Customer Success Manager).
@KFAISY I'm having the same issue. Could you resolve yours already?
If I re-export the file again, it just gives me the same csv as the initial one. After adding the translations in the translation column once more and re-importing the new file I get the same error.
Thanks for the feedback. I haven’t however worked with Notepad in my entire life and it seems not be able to display the csv as a spreadsheet. No idea how to edit the file this way, i.e. add the translations without having to type in the labels manually/copy them individual - which would be insane. 😂
Any chance this feature can be expanded to also show translations of custom properties on the front-end for clients/leads. Specifically with the Meetings Tool.
When using custom properties as part of the "Form" questions to schedule a meeting, they always show up in the created language, while default HubSpot properties are automatically translated to the person's browser language, leaving us with some properties in one language and others in another.
@JK_0322 Yes, I understand that it's crazy to add all the translations. I created a python program to fetch translations from DeepL and integrate them into my file. Alternatively, you could input your translations into Excel and develop a program to remove the extra commas.
The beta is a great start! But I don't see this working in a production environment yet, not without having to build some severe customization to ensure the .csv format is properly retained before it goes back into HubSpot. Right now, I can't seem to load it into an Excel spreadsheet so that the translation interface is at least somewhat passable, without messing up the .csv formatting. It replaces the comma with a ; on my machine, and it removes the "s around content. This is an Excel issue, not a HubSpot issue, but with the current state, we are forced to solve for it.
I'm not expecting a full TMS-like functionality here, but a better way to interface with the translation would be nice 🙂
Hi everyone - another quick update - it is now possible to import .XLSX (Excel) files when using the beta Translate custom CRM data. The goal of this change is to reduce the likelihood of errors when importing (e.g. encoding issues).
Also, this feature now supports custom properties including custom pipeline and pipeline stages, as well as custom object labels.
@rwebb1 would be amazing if product updates could be properly tested before setting it live
Because no one can tell me it is expected behavior to: 1. copy translated values of properties to other association objetcs (if the translated value is not even saved anywhere as a label/internal name) 2. that it translates raw data value in the settings tool and everywhere where you can create properties/change pipeline/pipeline stages etc. this is such a mess you change your language to the custom translated one then you change one thing in any pipeline (doesnt matter if Deal/Object/Ticket/etc.) and then every value gets translated to the existing language at stays this way making the original langugae where these objects/pipelines etc were created obsolete
Pls test stuff before shipping a broken product...
Pour ajouter un commentaire ici, vous devez être inscrit. Si vous êtes déjà inscrit, connectez-vous. Dans le cas contraire, inscrivez-vous puis connectez-vous.
