Pega 25.1.3 - @CurrentDateTime() and @DateTimeDifference() Not Returning Results in Test Data

We have identified a behavior difference after upgrading to Pega Infinity 25.1.3.

In Pega 24.1.2, the following functions return the expected result when executed through Test Data:

@CurrentDateTime()

@DateTimeDifference(“20260806T130758.819 GMT”, @CurrentDateTime(), “D”)

However, in Pega 25.1.3, the same functions do not return any result when evaluated using the Test Data option. No output is displayed, making it difficult to validate the expression.

  1. Is this a known issue or behavior change in Pega 25.1.3?.
  2. Has the evaluation of date/time functions within the Test Data utility changed in this version?
  3. Are there any patches, configuration changes, or alternative methods recommended for validating these functions?

This works in 25.1.3. We’re using this in our application and it works fine. Please find the input you shared and Output in 25.1.3.

Input: @DateTimeDifference(“20260806T130758.819 GMT”, @CurrentDateTime(), “D”).

Output: 1.0

Please ensure the double quotes is correct

For the same input we are not getting result through test data

Below is my actual expression and when i am trying to see the result through test data not getting result in Pega 25.1.3

(.pxPages(AttachFile).ECMArchivalDatetime,(),D)>(“Funding”, “FundingFilePurgeDuration”)

(“20260806T130758.819 GMT”, (), “D”) This expression is also not giving the result.

Even @CurrentDateTime () not giving any result.

But if i give input like below am getting result as True or False

(“20260706T130758.819 GMT”,“20260810T130758.819 GMT”,D)>(“Funding”, “FundingFilePurgeDuration”)

Please note that in runtime this expression is evaluating as expected and only its not giving result through test data, Also it is giving results as expected in Pega24.1.2 version with my actual expression.

Could you pleaes confirm if this works fine for you?

@DateTimeDifference(“20260806T130758.819 GMT”, @CurrentDateTime(), “D”)

If this works, then you can you can add the necessary logic to enhance it better

Are there any updates on this topic? We are facing exactly the same issue.