Comments
-
This may be occuring if you have your Company Time Zone Settings set to your local time. If this is the case, then when you begin using native SQL commands, it treats the time within those commands at UTC time. If you are West of the Central Time Zone then you are at least -7 hours from UTC, so in your example the system…
-
That seems really weird. I reproduced a few of your time stamps in a data set and then copied your code and it seems to have returned exactly what you were originally looking for. So this would seem to suggest that there aren't any errors in the way you have written the formulas.
-
UPDATE: It appears that you have to use Oracle-specific SQL language in this connector whenever writing queries. My LIMIT example was rejected because, as I have since discovered, it is not a command that functions in Oracle. Knowing that we need to stick with Oracle language, this query should work for the original…
-
I get the sense that only certain SQL commands are allowed in the Query section when creating a data set from SuiteAnalytics Connect. For example, I tried running this query: SELECT TRANDATE, TRANID FROM TRANSACTIONS LIMIT 100 and recieved the same error message for the multiple DATE_ADD functions I tried. Perhaps someone…
-
I have found myself continually coming back to timezone issues, particularly when trying to reconcile our Ecommerce sales which happen at all hours of the day. After reading your second comment, it seems that a good solution regarding data sets going forward would be to create a second date column that casts the original…
