finops-toolkit icon indicating copy to clipboard operation
finops-toolkit copied to clipboard
verified publisher icon microsoft

We cannot apply operator < to types DateTime and Text

Open mithilmehta121287 opened this issue 1 year ago • 5 comments

We already extracted the data using FinOps but Date is coming as yyyy-MM-ddTHH:mm:ssZ Format which is not recognized by Power BI Report, and Power BI is throwing error "We cannot apply operator < to types DateTime and Text" FinOps_Issue

mithilmehta121287 avatar Aug 22 '24 13:08 mithilmehta121287

@mithilmehta121287 Can you share your storage URL without the storage account name? I have a feeling this is about the file path rather than the date format but that's just a guess.

flanakin avatar Aug 23 '24 02:08 flanakin

@flanakin, please check attached snapshot for this.

Storage URL: https://storage_name.dfs.core.windows.net/ingestion

image

mithilmehta121287 avatar Aug 23 '24 14:08 mithilmehta121287

@mithilmehta121287 Can you share what your ingestion folder path looks like for the parquet files? I'm thinking there's an issue there. If not, we should setup some time to go over this together on a call.

#needs-info

flanakin avatar Aug 27 '24 07:08 flanakin

@flanakin, please check below ingestion path for Parquet file. Please provide me your availability to go over with details.

image

mithilmehta121287 avatar Aug 27 '24 12:08 mithilmehta121287

@mithilmehta121287, thanks for the extra details. This all looks perfect. I'm not sure what the issue could be. Can you email ftk-support@ms so we can setup some time to chat in person? I also just responded to a message from Ifeoma, who I believe you're working with. She might be in a better spot to help us coordinate a little quicker.

One other thought: Can you share the values you have in RangeStart and RangeEnd? I'm not sure that would be an issue, but checking just in case, since it is a date value that's getting parsed.

flanakin avatar Aug 28 '24 07:08 flanakin

@flanakin Is this still reproducible? I don't remember anyone reporting this exact error message.

arthurclares avatar Feb 24 '25 23:02 arthurclares

@arthurclares I think it is. I can work with you to test it. We need someone who isn't in the US to test it from what I've seen. We have at least one other issue for this as well.

flanakin avatar Feb 25 '25 10:02 flanakin

@mithilmehta121287 I just realized we added a fix for this in 0.8. Can you please try the 0.8 reports and let us know if you're experiencing any issues? We'll keep this issue open for a few weeks to give you time to confirm.

flanakin avatar Mar 09 '25 18:03 flanakin

Closing this since we haven't heard back. Please create a new issue if you run into any new issues.

flanakin avatar Mar 31 '25 06:03 flanakin