Skip to main content

Historical fields explained

  • May 31, 2023
  • 10 replies
  • 729 views

With historical fields, it's possible to create custom fields with effective date of any type to match their exact needs. This allows to track historical data of the fields, use these fields in filters and conditions, create a comprehensive changes report and so on (e.g. cost center, driving license, performance grade, work visa, etc).

It’s possible to support conversion of a simple field to a field with effective date, but not the opposite. Once a field becomes historical, it can't be changed back.

Historical fields can be used for category fields, but are not supported for tables.

It's also not possible for now to import historical fields.

10 replies

Hey @Ana Russo, we changed a field to be a historical field and now that field doesn’t show up in the column picker for a ‘changes report’ where it was previously visible. 

EDIT: I’ve just seen in a help center article that historical fields aren’t support in Changes report - will they be able to at some point?


Lindsay Sinenberg
Bobber

@Louise Connolly We have an open feature request with our Product Team for this limitation. So I went ahead and added your company to it. At the moment, there is no provided timeframe 😔


  • January 9, 2024

Hey @Lindsay Sinenberg, just wanted to see if there had been any update on the feature? If not, could you add me/my company to the feature request as well? 🙂


Lindsay Sinenberg
Bobber

Hi @Dom Prieto! There aren’t any updates as of now on the request. But definitely check in with your CSM who will be able to provide updates if Product makes any changes 😊


Hi @Lindsay Sinenberg can you please add my company to this? 

We require a historical table that we can capture cost centre information, cross charging codes etc that should not face out to the business. It would be used exclusively by Finance and our company changes alot and fast, so we need to be able to capture and provide in an audit, the data that supports. Many Thanks! 


Lindsay Sinenberg
Bobber

Hi @Jamie Macneilage! No updates regarding the historical fields. However, based on the information you provided for your use case, you could create a custom category with a custom table to store this data. Each row in the table would then have its own effective date and you can access a designated report for just this table. You can also provide visibility just for the Finance team.


Any updates on this request? How do you work with historical fields?


Lindsay Sinenberg
Bobber

Hi @Elena Milusheva! What request are you inquiring about? The limitation that historical fields aren’t supported in the Changes report?

If yes: there hasn’t been an update as of yet for this. But I went ahead and added your company to the open ticket with the product team 😊


Hello, is it still the case that historical data cannot be imported into a historical field? The workaround of using a custom category with a custom table isn’t working either, as those fields can’t be used in standard reports nor show the current value (not the entire history).

 


Netta Brodsky
Bobber

Hi ​@Patricia Barrantes - Thanks for your message! 🙏🏻

Unfortunately, that’s still the case - it’s currently not possible to import data into historical fields. I understand how limiting that can be, especially when the custom table workaround doesn’t fully meet reporting needs.

I’ve added your feedback to the open request with our Product team so they’re aware of the impact. If there are any updates in the future, we’ll be sure to share them!