Converting glidefunction:datediff() Report Function to Platform Analytics
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2025 02:32 PM
Hi all,
I'm in the process of converting reports from the classic Reporting module to Platform Analytics (PA) and have run into issues with function fields that use glidefunction: logic — specifically for calculating durations.
In the Reporting module, I created a report function field (with associated report ranges) using this expression:
glidefunction:datediff(coalesce(closed_at, now()), sys_created_on)
This works well in reporting module reports and renders properly in Platform Analytics list and bar widgets — as long as the duration value is not used by a group-by. This duration function has been created in multiple tables and is used in a large number of reports. Ideally I'd like to minimize the amount of changes needed to convert it to Platform Analytics. I am trying to avoid building a physical field that would then be populated by a nightly job.
My questions are:
- What is the best (ideally with the least amount of rework) way to replicate a glidefunction DATEDIFF duration calculation in Platform Analytics?
- Has anyone built a report in PA using calculated fields or scripted indicators that supports duration grouping and filtering (e.g., by duration buckets)?
Any insights, examples, or guidance is greatly appreciated. Thanks in advance!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-06-2025 12:16 AM
Hi @bhutch
To the best of my knowledge you do not need to manually convert function fields that use glidefunction:
syntax as part of your migration to Platform Analytics. The Migration Center is designed to handle these automatically. However, always validate your migrated reports to ensure all function fields and calculations are working as expected.
Maik