Search the Community
Showing results for tags 'sql request importer'.
Found 3 results
-
Can we requests an enhancement to be able to import multiple connections on a request as part of the SQL Request Importer. We would envisage this as an additional sub query process much like the historic updates/comments. We would want to be able to pass both Co Worker id's and for Contacts, the Contact ID or Contact email address. Cheers Martyn -
@Steve G @Victor Can I clarify which value related to the Logging and Closure category is to be entered into the 'CategoryMapping' and 'ResolutionCategoryMapping' sections. In the example json files it mentions ID for the former and Code latter, but neither have an actual example value. }, "CategoryMapping": { "External Category": "Service Manager Category ID" }, "ResolutionCategoryMapping": { "External Resolution Profile Code": "Service Manager Resolution Profile Code" }, At the moment I have tried the code as copied from the admin screen with the - delimiter and also the key value from the same screen but to no avail. Cheers Martyn
-
I am currently undertaking test migrations using the SQL Request Importer (v1.3.1), and I am trying to carry over a much information into the Historic Updates that the tool allows. Would it be possible to get some clarification on the below:- h_updatedby and h_updategroup, are these just literal values or are there lookups applied to them such as the User lookup and Team Mapping? h_actiontype and h_actionsource I am presuming these are textual literal values which we can pass in any text from the source system? h_timespent is passed in as an integer in the unit of minutes? Cheers Martyn