Steps to Import accounts / contacts through schedule csv from SCP 11001 build
This is applicable only from 11001 builds.
How to do?
# Based on the Globalconfig table entry with category as 'CSVUserImportSchedule', this can be turned ON/OFF. By default this is turned OFF.
Query to enable the feature - update Globalconfig set Paramvalue='true' where Category='CSVUserImportSchedule';
# Mapping of the user's fields with the CSV file can be specified in the 'ScheduledCSVUserImportMapping.xml' file present under $SCP-HOME\conf directory. This is a daily schedule.
# Schedule time has to be set via database. Use the query given below to set the time. Highlighted time can be changed in the query.
update task_input set schedule_time = '2020-09-15 14:23:00.000' where schedule_id in (select schedule_id from schedule where schedule_name ='CSVuserimportschedule');
Note: Once the query is executed in the database,restart the application.
Configurations in ScheduledCSVUserImportMapping.xml
# The fields 'filePath' and 'fileName' are used to locate the needed csv file for the user import. After the import, the csv file will be renamed automatically to avoid unnecessary (or) repeated imports.
# If portal specific files are available, specific the file path as [filePath]\$PORTALID (eg: C:\ManageEngine\SupportCenter\$PORTALID) and place the respective files under, [filePath]\[portalid]\[fileName] (eg: C:\ManageEngine\SupportCenter\601\requesters.csv), where portalid is the id of the portal to import.
In the XML file, you only have to give the variable $PORTALID at the end of the file path as shown below( No need to provide the portal Id in this XML):
In the File name, you have to give the CSV file (ex - Requesters.csv) name that you are going to import
# In the above case, we need to create a folder named 601 manually under SupportCenter directory.
You have to create separate folders for each Portal ID inside the path "C:\Program Files\Manage Engine\SupportCenter Plus" as shown below:
Ex snapshot (1,2,601 are portalID created as folder)
# The portalid can be obtained from result of select * from helpdeskdetails query
# If a single file contains portal data, specify the file path as [filePath] (eg: C:\ManageEngine\SupportCenter) and place the files under, [filePath]\[fileName] (eg: C:\ManageEngine\SupportCenter\requesters.csv).
# DisplayName, LoginName, Password and PortalID is mandatory. If any of these filed is missing the requesters.csv then import will be getting failed. In the below CsvFieldName is your CSV header name of the corresponding values.
# Default available USERFIELDMAPPING are
<USERFIELDMAPPING AppFieldName="displayName" CsvFieldName="displayName"/>
<USERFIELDMAPPING AppFieldName="firstName" CsvFieldName="firstName"/>
<USERFIELDMAPPING AppFieldName="lastName" CsvFieldName="lastName"/>
<USERFIELDMAPPING AppFieldName="emailId" CsvFieldName="emailId"/>
<USERFIELDMAPPING AppFieldName="phone" CsvFieldName="phone"/>
<USERFIELDMAPPING AppFieldName="mobile" CsvFieldName="mobile"/>
<USERFIELDMAPPING AppFieldName="account" CsvFieldName="account"/>
<USERFIELDMAPPING AppFieldName="login" CsvFieldName="login"/>
<USERFIELDMAPPING AppFieldName="password" CsvFieldName="password"/>
<USERFIELDMAPPING AppFieldName="portalId" CsvFieldName="portalId"/>
# In addition to the default available USERFIELDMAPPING, we can add this for
<USERFIELDMAPPING AppFieldName="errormailaddress" CsvFieldName="tech2@sdpmsplinmail.com"/>
This USERFIELDMAPPING is used to send a mail if the import has beed failed.
# We can configure Additional fields as well to import the contacts with additional fields.
<USERFIELDMAPPING AppFieldName="userSingle" CsvFieldName="userSingle"/>
<USERFIELDMAPPING AppFieldName="userMulti" CsvFieldName="userMulti"/>
<USERFIELDMAPPING AppFieldName="userPick" CsvFieldName="userPick"/>
<USERFIELDMAPPING AppFieldName="userNumeric" CsvFieldName="userNumeric"/>
<USERFIELDMAPPING AppFieldName="userDate" CsvFieldName="userDate"/>
CSV format should be as below and Portal ID should be present as shown
New to ADSelfService Plus?
Related Articles
User Import Issue (CSV)
While importing Contact or Support Rep via CSV many customer face issue with importing getting failed The most comman reason is that the CSV file may not have the password for the users getting imported We have set the Display Name and Login Name as ...Custom Script to enable "remove login" option for contacts in SCP 8.1
Use case: To disable login for contacts in bulk from Contacts module. The attached CustomScripts.js can be moved to SupportCenter/custom/scripts directory. Browser cache needs to be cleared for the script to work as expectedWorkaround for Contacts tab not visible for support reps (post 11.0 version)
Post 11.0, the contacts tab will not be shown at the top for support reps. As a workaround follow these steps 1. Goto Admin -> ZOHO Creator apps 2. Click on Add Links -> Provide Link Name as Contacts -> URL as ...query to find the unapproved contacts -> PGSQL
Below is the query to find the unapproved contacts -> PGSQL-> can be used from version 11 SELECT aaauser.User_id AS "User ID", aaauser.first_name "First name", aaauser.last_name "Last name", hd.id "Portal ID", hd.displayname "Portal Name", ...List of contacts logged into the system
Mysql select aas.session_id "SessionID", aal.name "User Name",aau.FIRST_NAME "Contact Name",org.NAME "Account Name", aas.user_host "User Host", aas.application_host "Application Host", longtodate(aas.opentime) "Start Time", longtodate(aas.closetime) ...