cwalliser Member

No solutions I'm aware of yet. Maybe creating a custom connector. But I'd rather have a standard tool to work with. 

My bad. I found a structure difference in one of the files. When I removed that file from the folder, the update worked. A lovely thing...

I tried this approach to load 3 csv files with different names in the same folder. The preview test failed with an error message below. I notice only Q1 & Q2 files show in the log. Is there a file size limit? Some other factor I'm missing? I don't see any structure differences in any of the files. [08.28.17 03:45:48 PM]…

I think there were some missing fields (even though I couldn't see them). The export showed the column names correctly, but a couple of the columns were showing blank values on records I recall previously having values. We ended up building a new dataset with workbench and connected that to the related data flows. Things…

That's the problem, there is no beast mode to do this yet. I've been told other users in our company that there is a "fiscal calendar" function available in Domo, but I haven't figured out how it works yet. The earlier post referring to uploading a fiscal calendar data set, then doing ETL to link that to you reporting…

I see an MS SQL connector, but it appears to be for cloud instances, not on-premise. How do you configure this connector to talk to an on-premise SQL DB? Meanwhile, I discovered that Domo Workbench allows me to connect to the on-premise SQL via odbc. And allows me to write the SQL query directly.

Thanks for the update. The good news is that Domo keeps growing. It will come in time ?

I think I forgot to state in my original post that we use are doing a distinct count of records per order id. Is there a way too use this logic for distinct count?

Thank you ckatzman, that is what I was looking for. I was looking at the % symbol as a percent function, not a variable. More coffee...

creating the DSN as a 32 bit system dsn worked. thanks