Changes

However, the soap example worked with a frontend form (which wasn't explained much and so I looked ) leading me to investigate more into what was requiredby the soap service. When I found the form in "examples", it did not work as an application entry point (because even though it defined ('sugarEntry', true); there was also an IF that pre-empted that definition)Not because other code was being loaded before the form. I did not immediately seeing see this cause for the example failure, so I put the example form outside the application directory and then successfully used the form to insert a single lead This is illustrated at http://www.sugarcrm.com/wiki/index.php?title=Creating_a_lead_capture_form_for_your_websiteSeeing that the example worked, but did not capture all the details provided in the data exercise, I knew I should look at the existing functionality of modules/Lead dealing with Import (dataMaps), the database abstraction layer (SugarBeans and/VarDefs) or the database directly to get a clear clearer picture of what I needed to label everything.

Looking at the full application import routines and the four-step forms for importing leads, it seemed was obvious that there was a lot of machinery that I didn't need or want to get involved with to simply import records. For instance, why deal with all I would not want to (re-)write the form and UI handling when I simply needed to insert records into a database. This made me reconsider using the SOAP example to write a scriptdo the job. In essence, it would only need to read the exercise data and create full records for the 50 provided leads.