Great minds think alike

Last week, there was a significant change in all our exports. Specifically, any fields containing 'ID' in their names had the 'ID' portion removed. For instance, 'Contact ID' became 'Contact', 'Record ID' became 'Record', and 'Line Item ID' became 'Line Item'. This alteration has created chaos in our field mapping for other applications. Consequently, we'll need to reconstruct all our scripts. When I inquired about this with Support, this was their response. I'm not sure why HubSpot would suddenly decide to rename my fields upon export but I'm hoping this can be reverted back to save me asking Operations to have to rebuild everything.  I'm currently renaming the header rows in .xls when I export my reports every night so errors don't occur and every department gets their data in the morning. Hi Kim,   Thank you for your patience here, I did some digging and testing within my own personal portal for these properties when exporting reports. I created a sample report and exported them from my portal and my export has also dropped the "ID" out of the headers on the csv.   After doing some research internally, I was able to confirm that there has been a change made and this update is across the board on reports in hubspot not just isolated to your account. I can confirm the export is working as desired with the headers not including the "ID".   While I know this may not be the answer you were looking for as you mentioned this change impacts other integrations my best recommendation would be to submit a feature request for this here in our ideas forum.   The Ideas forum is the best way to let our product team know about features that our users would like to see implemented in the portal. As you may know, this forum is frequently monitored by our product team and is an additional platform we can raise changes and/or new features we want to see within HubSpot.   Please let me know if this resolves your roadblock or if I have misunderstood your goal ! Best, Nyasia   ...read more

I'm using Hubspot CRM for sales for my real estate business. One of the biggest challenges that I'm running into is with new imports. The leads in my import list do not have emails, which defaults the records from matching the records in HubSpot.    It would be great if the common denominator between records could be changed from emails to another property or properties such as address, city, state, zip/postal code. Giving the user the flexibility to select which properties they want to match to existing records in Hubspot to prevent duplicate records would be fantastic ...read more

Currently, there isn't a way for us to see the user status "deactivated" or "invite pending" etc when we export the user list from HubSpot because this column is not added to the report.    Since the deactivated user list will get longer over time, it becomes very cumbersome in trying to manage data of users who are no longer with the company. Hence please consider including the "user status" column in the Export User Report. ...read more

When using the "API Request (Beta)" action in Zapier to connect to Hubspot, it runs into an error when trying to import contacts (POST https://api.hubapi.com/crm/v3/imports).   "Failed to create a http request in HubSpot Raw request failed. Problem executing your request: This app hasn't been granted all required scopes to make this call. Read more about required scopes here: https://developers.hubspot.com/scopes. errors: All of the following scopes are required."   Use case: updating large numbers of Hubspot contacts (1000s) regularly based on data from external systems. ...read more

hey, my job would be slightly more efficient if we could run an import of same-object associations in the same import with multiple object types.    also ps the select objects (single vs multiple) section is a little confusing to reps. It should specify object types.    reps otherwise are thinking am I importing one single object vs one type.  ...read more

It would be beneficial for users to be able to select the date format when exporting object data. For example, when exporting contacts, the "Create Date" property is exported as YYYY-MM-DD HH:MM. However, having the option to select DD-MM-YYYY HH:MM add value. This would also apply to other data exports from HubSpot. ...read more

People try to import old address books and contact information including emails that have already hardbounced from our system. This is reverting the record information to the old email address that was listed as secondary for record history or re-establishing a new contact profile with an address that the importer assumes is current or contactable.   Instead of updating/creating these records, it would be great if the import created an error message instead. ...read more

It would be very helpful to be able to import postal mail activities through the import tool. Currently the only options are manually on each record or through the api.   We work with financial services companies and they send a lot of direct mail through various banking platform providers. The mail sent through those platforms cannot be sent through HubSpot. They also don't always need to import direct mail from all platforms. So, when they do need to know which of their customers has been sent direct mail they often have to use over-complicated methods to get a one-time import into the CRM. ...read more

Vender debe ser apto de comunicar una idea que despierte el interes de quienes escuchan  ...read more