We use the enclosed scenario to add/update records to the Service Manager contact table; the input is a text file (sample included) and the scenario either adds a record or update it depending on the existense of the 'Hire' flag at the end of the record.
Our problem is the following: some contacts already exist in the contact record because they had some previous relationship with our company (usually as contractors) and were hired. In that case, their record will come in with the 'Hire' tag but will not be added because they already have a record on the table (they keep using the old id as the 'contact.name').
One way around this will be to check the "title" field, and if it is "contractor" that's will tell me that I need to update this record instead of adding it. Right now I do this check with the "Hire" tag in the mapping script for the "Create Contact" action:
if Mid([Action],1,4) <> "Hire" then
That will send the incoming record to the "UpdateContact" branch of the scenario, but in this case the incoming record has the "Hire" tag, causing the problem that I'm having. In case you're asking, I can't have the source record changed to eliminate the "Hire" tag for this situation because to the source system that produces that data this is a new employee and they have no way of knowing that it correspond to someone who already was in SM contact table.
So how do I update this mapping script to check for the precense of the "Contractor" value on the contact record? Is that the right way to go about this?