Comments
-
I guess that answers it. I'll take your advice and submit it. Thanks.
-
Just tried and getting the same results regardless of the user.
-
No, I haven't but, the users have the exact same role
-
Thanks Jae, I will check out the Slack group. BTW, I've used your You Tube before, it's been very helpful.
-
Hi ,thanks for your response. Yes, I've read the documentation you mentioned and didn't see anything I am missing. Yes, I have variable in the select, order and where clauses. Still haven't figured it out.....
-
Thanks for the reply, yes I did google it but did not find anything useful. We are using a Teradata ODBC driver. After some more testing we found that there was a column we had transforming a time [Interval Day to Second(6)] that was causing the error. We reconfigured that field to calculate what we needed to differently…
-
Here you go. In the historical dataset, I changed the name of the column 'userType' to 'Type' to match the activity log.
-
My service rep was able to give me a one time download of the historical data that I could combine with the Domostats with a magic ETL.
-
Thanks for the tip. Given the complexity of the data (multiple locations, times) I was trying to avoid doing the calculation ahead of time in SQL. But if that's what I need to so be it. Thanks.
