title: What is a good design pattern to implement a dynamic data importer tool?
body: <p>We are planning to build a dynamic data import tool. Basically taking information on one end in a specified format (access, excel, csv) and upload it into an web service.  </p>
  
  <p><strong>The situation is that we do not know the export field names, so the application will need to be able to see the wsdl definition and map to the valid entries in the other end.</strong></p>
  
  <p>In the import section we can define most of the fields, but usually they have a few that are custom.  Which I see no problem with that.  </p>
  
  <p>I just wonder if there is a design pattern that will fit this type of application or help with the development of it.</p>