Data exported is not the same as data imported

[mmagnuson]

Hi,

This is a rather strange question but hopefully someone has an answer or thought.

I've been exporting data to a specific file location multiple times a day, overwrite the data and export it to Salesforce. Throughout the year there have been multiple edits to values, columns etc. and the export has always shown the changes.

There was an issue with logic in the query where new calculations were needed for two weeks in the year that I edited yesterday. For example, for the week of 5/24 instead of the Sum of Column 1 being 8 it needs to be 16. When I filter the final data table in SAS it shows as 16, however, when I export the data then re-import it into a new SAS query the value shows as 8.  

Are there any thoughts/reasons why the value changes from the final data table vs the export?

[Shmuel]

Either you exported the input sas dataset of your run or

you have exported it in a different name then the one you just imported or

exported it to a different path.

[Kurt_Bremser]

Please post your SAS dataset in a data step with datalines, and the code you used to export and import the data.

[PaigeMiller]

@mmagnuson: 

There's really no way to answer this unless you show us your code and a portion of the data.

[TomKari]

Given the logic you're presenting, I can't think of any explanation other than that there is an error somewhere in your chain of code.

Troubleshoot each step. Some specific suggestions:

Make sure you're actually creating a new file on the export, and not leaving the old file in place.

A related thought is that a lot of people (myself included) don't like overwriting an output file as part of this kind of process, since you lose all ability to troubleshoot. I suggest either writing each new file to a new filename, or rename your old file before you write a new one.

Good luck, and let us know what happens.

    Tom

[mmagnuson · Accepted solution]

Hi everyone, 

Thanks so much for chiming in. I went through some of the different columns to see where the disconnect was and it was due to the data needing to be formatted. The final data table showed 1.25 but it was being exported/imported as 1 which was throwing the differences off.  I made a data change on the last query builder to ensure that it exporting/imported the same way and now it does.

Thanks again!