Vista has a reasonable data import mechanism when one row of import data equates to one Vista record. But the standard routines will not import data which does not fall into the standard model. This is a common occurrence when importing Command Alkon concrete data. It has multiple ticket elements in each imported data row.<\/p>\n\n\n\n
With a custom stored procedure, and proper data capture, this type of import can be accommodated in Vista’s import. This is how we did it.<\/p>\n\n\n\n
We created a user field to capture the entire string of data. This was attached to each ticket during the normal import process. Upon completion of the import, our custom process then when through extracting the additional records, added each one to the import tables, along with the appropriate validations. And finally, blanking out the custom field so it would not be retained in the database.<\/p>\n\n\n\n
While this process underwent a bit of troubleshooting to ensure the implementation went well, it is daily in use, importing multiple concrete tickets with each imported data row.<\/p>\n\n\n\n