Does anyone know of a way to prevent HubSpot from changing
a custom field (string) that is entered in all CAPS to lowercase on a report? Thanks…
(i.e. in the field (deal property) Q4 FY22 => displays on the report => q4 fy22)
Hi @DZoladz1,
Thank you for reaching out to us!
This is working as designed albeit at a possible inconvenience for you and other customers. Essentially, this behavior is due to how our systems currently display single line text fields in reports, with them being not case sensitive. The reason being, the API endpoints we use to generate reports returns the internal key (in this case the lower case property fields) rather than the actual labels.
Our team is aware of this confusion from customers and is actively trying to see how we might be able to adjust this behavior in the future, but don’t currently have any timeline for this.
Best,
@JenWeiss
How is this an “Accepted Solution”? You’re taking data entered into a specific field with specific capitalization and returning it all as lower case in your report, then shrugging and saying, “We’re not going to fix this”.
This really can make dashboard reporting non-functional in some cases when everything pushes out as all lowercase. Specifically, we have a report on a ticket dashboard that is intended to show the latest technician notes on units. We use this report to see a snapshot of activity on these particular open tickets. Often the report is exported for regular progress review meetings with leadership. When everything is in lowercase, it can erode the meaning of the notes entirely.
For example. In a ticket note, a rep may enter:
- “On 8/8/2024 For Jack - this PI unit needs exclusion version X2xR”
but in the dashboard report (and exported XLS report) it would show as:
- “on 8/8/2024 for jack - this pi unit needs exclusion version x2xr”
This is especially challenging when we have internal reporting language that is case-sensitive.
In this example:
- Jack and jack can have separate meanings (person or thing) and
- version X2xR would not be the same as version x2xr (as x2xr would not even exist because the version is case-sensitive).
Is there any way to correct this output?
Hello @DZoladz1,
So one of my team members did a check and found it is working fine in the Reports. Please refer to the following screenshot:
If you can share any specific scenario where and how you are doing this, then I can have a better understanding of the issue as it is working fine for now.
Regards,
+1 to this the removal of capitalization can cause confusion - this is specific to the custom reports vs. using single object.
Adding to this that the text shown in reports is only changed to lowercase when one of the fields has an aggregation (Sum, Average, Min, Max, etc) as when I remove the Sum from the fields of my report it allows text to display with proper capitalization.
Getting this corrected would be very helpful, otherwise there is little benefit to using the report feature vs exporting my sales deal view to an excel file, which as it is I have to export it anyway just to correct the capitalization.
Agreed, this should really be addressed.
Adding a +1 to this! Understand it is working as designed but when these reports are used for management reporting, it is important for us to present them as professionally as possible with proper capitalization
+1
Properties such as deal name should not be converted into lowercases when used as dimension in table reports.