ETM example of creating an object if it doesn't exist Does anyone have an example ETM datamapper that checks the existance of an object (could be an Item, Section, Department, Cost Center, etc.), and if it’s not found, to have it created?In the process of importing my Contact Users through ETM, we are providing the values for Section, Department, Building, Cost Center, Job Title, etc. The issue I am running in to is that there are sometimes values in the CSV that we are importing for something, we’ll use Section, that doesn’t exist in Assyst. What I am currently doing is exporting the list of existing Sections via the DMW, then comparing it to the distinct values in our CSV import, then manually adding any that are missing in Assyst. What I would rather do is create a datamapper that first goes through the import CSV, just looking at the Section column, and checking to see if it exists in Assyst yet. If so, skip, if not, create it. That way, I can get any missing Sections, Buildings, etc. added to Assyst BEFORE I do the user import, so th
