calc field defined as: extract(‘HH’, {created_date})
i can see that out of 17,000 records, about 30 of them yield results that are greater than 23. This should not be possible. It concerns me that many are wrong but I can’t tell which others are incorrect with a quick glance.
Picture one shows the weird anomalies. Picture two shows the majority of my data looking correct.
Hi @davidqwi,
I wonder if there’s something going on with your actual ‘created_date’ field for those rows, would you be able to add in ‘created_date’ to your table visual and share new screenshots so that we can see how the created date field may be differing between the correct values and the anomalies?
Hello @davidqwi
Are you able to follow up on @Brett 's question or were you able to solve this problem? If we do not hear from you in two business days this topic will be archived.
Hi Brett, I have the created_date field shown in both of those screenshots already. Do you mean for me to present them in a different way? I apologize, but I do not know exactly what you mean when you say to proivde the created_date field as I have two fields present for both screenshots: {created_date}, and my calculated field, “TEST_extractHH_created_date”
I figured it out. I overlooked something and it was not a bug or corrupted data at all. I didn’t realize there were duplicate records for certain tickets and I was taking the sum of the extract() of the timestamp and that’s why it was >24. You can close this now. Thanks for the input all.
2 Likes
Hey @davidqwi
I’m glad this got solved, thank you for sharing your solution!