Comments
-
No, the files come from the same source. it does appear to be random, the source people do not seem to have control over which gets sent, or at least they do NOT know how to control it. There are NOT New York and Chicago files, it is just one file sent weekly. This column heading has been switching back and forth ...
-
It is not at row level. In this instance, we are using the DataSet via email connector to load the data. This data is generated external to the company. Sometimes, within the file, the date column name is named "Source Date (America / New York)" Sometimes, within the file, the date column name is named "Source Date…
-
Thank you, i appreciate your efforts! To clarify, the data comes through with either `Source Date (America / New York)` OR `Source Date (America / Chicago)` as the column header, not a mix of both ...
-
Thank you for the reply! I did try your suggestion and received this error message: Invalid Formula : A column in this calculation did not exist. To clarify, the data comes through with either `Source Date (America / New York)` OR `Source Date (America / Chicago)` as the column header, not a mix of both ... Thanks again!
-
that's an interesting suggestion, thank you. i find it more so as we have realized that the owner of a Dataset via email does NOT get notified when the email update does NOT execute for any reason. That is, whereas the dataflow owner can get an email notification when the dataflow fails to update, this is NOT available for…
-
Thank you for the reply, an interesting work around ... but i was looking to avoid creating new dataflows, moving the card, etc. The dataset and the card are fine, i just want to change the way the data is being updated from a file upload to a dataset via email ....
