Amanda Rosser Posted September 25 Share Posted September 25 My company has a nightly DDS job that pulls all of our data since the previous pull. We made the choice to move away from the API due to the lack of visibility regarding deletes. DDS comes with it's own list of issues, but I have been able to find a workaround for most. When a custom field configuration is modified the column completely changes location on the DDS file. This causes my ETL to fail as the flat file config no longer matches. I have tried to edit, modify, and save the DDS job in order for the order of the columns to correct themselves but that did not work. As of now, I have to either modify the package in my ETL to accept the new configuration or I have to manually for the column in the file. If I modify my ETL I either need to create branching logic to accept multiple configurations or I have to update the config and lose the ability to easily reprocess the files form before then unapproved change. Does anyone have any ideas on a workaround? Or even better a way to get this to stop happening? As the DDS job UI gives the user the ability to sort the selected fields my assumption is that the expected behavior is for the DDS configuration to dictate the file configuration. Link to comment Share on other sites More sharing options...
Members Sterio, Louis Posted September 26 Members Share Posted September 26 Amanda, I am not aware of any work arounds to this however I made the DDS product manager aware of this issue. Link to comment Share on other sites More sharing options...
Recommended Posts