@srinivasan_ab Thanks for reaching out. I entered your issue into our Community chat agent and this is what I got. I have asked @Brett to validate this when back online on Monday – but hopefully in the meantime this will help you get unblocked. 
To address the issue with energy values that reset on vehicle on/off patterns, you can use calculated fields to handle pre-aggregated data without additional aggregation. When working with table visuals where calculations have already been applied at the data level, you should place all fields in the “Value” field well without using the “Group by” field to avoid unwanted aggregation. 1
For your specific case with energy consumption values that reset to zero, you could try using conditional statements similar to these approaches:
-
Create a calculated field that uses CASE or ifelse statements to handle the reset values, similar to how negative adjustments are handled in energy consumption metrics. 1
-
You might consider using countOver with ifelse to identify specific conditions, which has proven effective for other users with similar aggregation challenges. 2
-
Another approach is to use a formula like this to filter out unwanted values:
ifelse({energy_value}=0 OR other_conditions, NULL, {energy_value})
This would help remove noise or numbers affecting your calculation. 3
If you’re still getting only maximum values when you need to capture all reset periods, you might need to modify your approach to track each reset cycle separately, perhaps by creating a time-based partition in your calculation. 4