13. When you are done with your web server settings, move over to
“CIG CRM module config” tab
14. In email configurations update your SMTP server name, from and to email address.
15. In folders, you can change the default folders where the CIG CRM module stores the form XML files that it retrieves from the CIG Web Service module.
CIG to CRM user mapping
16. You can map your web site/s forms’ users on your CIG web site into one or more CRM users.
17. This allows you to add several “User Alias” that you will be able to use later on when you create CIG ASPX Forms (see: Create custom forms in )
18. To do so follow these instructions:
a. Click on “WebUsersToCRMUsers” ... next to the (Collection) value
b. In the popup that appears you will have 1 user mapping made for you as an example:
c. Set the domain, password and user name to the real CRM user credentials.
d. Set the user alias as the CIG web site’s form user you wish to submit to CRM as that user.
Connection to CIG Web Service module
19. To configure the CIG CRM module to connect to the CIG Web Service module (that does not have to be on the same machine), use the “Web Request Settings” configuration section.
20. You can set up the CIG Web Site URL, the interval (in minutes) for the requests for updates, and the user credentials to run the requests under.
CRM entities configuration
21. Last, you will have to configure Entities mapping between the CRM and your CIG web service forms.
a. Click on the “...” next to the Entities definition
b. In the popup that opened you will have a sample entity binding for “Accounts”
c. First, under “Entity Settings” choose the entity this form definition relates to.
d. Under “Form Settings” set up the “FormName” to a unique form name (we will use it late on in our web site)
e. You can use one entity definition with several ASPX forms, as long as all these forms specify the same “FormName” value.
f. In “Form Fields” you can add mappings from your web form to CRM entity fields.
g. Click on “...” near “Form Fields” to add and edit field bindings:
i. In “Form Field” choose the name of the field in your ASPX form.
ii. In “Entity Field” choose “EntityFIeldName” from the list of fields in current entity
iii. In “FieldType” select the field type.
h. TBD –export to excel
Expose entities to web site
22. Exposing CRM entities to you web site is composed from 2 steps:
a. Adding CRM entity definitions to CIG (see:
b. CRM entities configuration)
c. Creating ASPX forms in CIG web site to handle these entities (see: Create custom forms in )
Create custom forms in your web site/s
23. After you configured CRM entities in CIG CRM configuration you now can create your custom form page (one or more) that you will expose to your users.
24. You will have to keep at hand the following information from the CIG entity configuration screen:
a. The “FormName” you selected in the set up screen
b. The “FormFieldName” and type for each of the “FormFields”
you configured for this entity
25. You can create a web forms in any required web application/site, implemented in any required technology. You just have to make sure these form perform a POST HTTP request to the appropriate address, and include the correct form field names.
The following example demonstrates how to create a web form in ASP.NET:
a. Go to “C:\Program Files\KWizCom\CRM Internet Gateway\WEB”
on CIG web site.
b. Make a copy of “SampleAccountForm.aspx” into a new file (say “EntityXForm.aspx”)
c. Open the new ASPX page for edit using notepad or other text editors.
d. Edit and modify the “FormName” in the following lines (Replace “SampleAccount” with your form name:
<form id="SampleAccount" method="post" action="[URL of CIG web
site]/CreateEntity.aspx?redirecturl=SampleAccountForm.asp x">
And in:
<INPUT id="__formname" type="hidden" name="__formname"
value="SampleAccount">
26. Set up the CRM users this form allows to submit as:
a. Your form can run as one specific CRM user, or you can allow your users to choose between several CRM users to work under.
b. Simply add this HTML to allow your users to choose between
“user1” and “user2”.
<SELECT id="__useralias" name="__useralias">
<OPTION value="" selected></OPTION>
<OPTION value="user1">run as user1</OPTION>
<OPTION value="user2">run as user2</OPTION>
</SELECT>
c. Note: “user1” and “user2” were defined earlier in CIG to CRM user mapping
27. The rest of the HTML is pretty simple and dynamic – you can change everything as long as you keep to the following rules:
d. For every “FormFieldName” you set up – create an input
e. For a text field named “inAcountName” add the following HTML:
<INPUT id="inAcountName" type="text" name="inAcountName">
f. For a choice field named “selIndustryCode”, add the following HTML:
<SELECT id="selContact" name="selContact">
<OPTION value="" selected></OPTION>
<OPTION value="Mike Peterson">Mike Peterson</OPTION>
<OPTION value="Jill Garassy">Jill Garassy</OPTION>
</SELECT>
g. For a yes/no field named “chDoNotPhone” add the following HTML:
<INPUT id="chDoNotPhone" type="checkbox"
name="chDoNotPhone">
Monitoring
Once you finished all configuration – you still need to check that the service do update the CRM with changes in your web site, right?
For every failed job – an email will be sent to the address you specified in the CIG configuration screen like this:
There you will get all details about the errors and a log file (saved on the server) that may help you (and mostly us) to understand the error.
Most common error is no access for the service to CRM.
This can be done when you did not define correct user mapping for some forms, and when the CIG service does not have permissions to update the CRM.
To check the service permissions
1. Open “Services” console in “Administrative Tools”
2. Find “KWizCom CIG” service
3. Right click -> properties on the service
4. Update the user credentials here to a user that has access to CRM 5. Click OK and restart the service.
To check CIG user to CRM user mapping 1. Open the CRM settings form
2. Check Web Users to CRM Users configuration
3. Check user configuration in “Request Data” section: