Beruflich Dokumente
Kultur Dokumente
Application Architect
New Editable Grid control
This new control uses an internal or external SData feed as its data source and provides the
following functionality
Allows inline editing of column data.
Provides ability to look up child data and add new records to the grid.
Security may be implemented using the Applied Security property.
A number of different column types are available: Checkbox, Currency, Edit, Editable
Field, Link, Lookup, and Numeric.
Predefined grid toolbar buttons are available to save data changes, delete records from
the grid, or undo unsaved grid changes.
For more information, refer to the Application Architect Help topic, Editable Grid Control.
Sage Software
Page 1
Sage Software
Page 2
Blank Merge Accounts/Contact Screen when Merging and error when the
check for Duplicates function is used
From step 12 in the Applying Service Pack 4 Documentation:
Delete the MergeConfiguration.xml and the PotentialMatchConfiguration.xml files.
Note: If you customized the files, record your customizations before deleting them. New
configurations have been added to the MergeConfiguration and PotentialMatchConfiguration files.
You must delete and recreate the files to see the updates. These files are rebuilt when you
convert a lead in the Web Client. After you recreate these files you can add your customizations
(step 69 in the service pack 4 documentation).
To delete
1. In the Application Architect, open the Virtual File System Explorer.
2. In the tree view, expand Configuration and expand Global.
3. If necessary, save the MergeConfiguration.xml and the
PotentialMatchConfiguration.xml files to another location or record any customizations
to the files.
4. Delete the files.
Desktop Manager
Install
It is possible to install the Desktop Manager to a different directory than the default. The
command line to perform that install is:
SlxDesktopIntegrationSetup.exe /s /v"/qn INSTALLDIR=\"C:\Program Files\<installationfolder>\""
Sage Software
Page 3
Note: Y = True
N = False
1 = True
0 = False
SDataUserName = the Sage SalesLogix user, for example, Dan from the Eval database.
You must use the SalesLogix user, not the SalesLogix Admin user, so that the History
item is created as the SalesLogix user. Otherwise Sage SalesLogix security for the user
will be bypassed giving the user full access.
Windows Authentication
Desktop Manager can now use Windows Authentication introduced for the SData portal. For
more information on configuring Windows Authentication, please review the Administrator Help
topic, Enabling Windows Authentication Access for Web Client Users.
Tray Notifications
When Desktop Manager is running and a SendSLX or a Record to History is performed, users
may see notifications appear in the system tray depending on their options. To turn this off, open
the Desktop Manager and clear the Display Tray Notifications check box.
Sage Software
Page 4
Logging
You can enable Desktop Manager logging to assist with troubleshooting.
To enable logging
1. Open the Desktop Manager and click the View Log button.
2. Check Enable Logging, and then press OK.
Following are examples of information written to the log.
Scenario 1:
Sending E-mail in Outlook and selected SendSLX. The contact cannot be found in Sage
SalesLogix (there is no contact in the system with a matching E-mail address).
[Info] 6/10/2011 07:39:19:502 Processing "testing to see if this logs to desktop manager log"
[Info] 6/10/2011 07:39:19:502 Build list of addresses to process
[Info] 6/10/2011 07:39:20:658 Processing 1 addresses:
[Info] 6/10/2011 07:39:20:658 John.Smith@testaccount.com
[Info] 6/10/2011 07:39:20:658 Building HTTP request
[Info] 6/10/2011 07:39:20:658 Looking for contacts
[Info] 6/10/2011 07:39:20:658 Searching for SalesLogix Contacts
[Info] 6/10/2011 07:39:20:971 Looking for leads
[Info] 6/10/2011 07:39:20:986 Searching for SalesLogix Leads
[Info] 6/10/2011 07:39:21:111 Found 0 contacts/leads
[Info] 6/10/2011 07:39:21:111 Building list of unresolved addresses
[Info] 6/10/2011 07:39:21:127 Found 1 unresolved contacts/leads:
System.Collections.Generic.List`1[System.String]
[Info] 6/10/2011 07:39:21:127 Displaying unresolved contacts/leads
When the user selects OK (if prompting is enabled), the rest is written to the log.
[Info] 6/10/2011 07:42:55:118 Successfully processed "testing to see if this logs to desktop
manager log"
[Info] 6/10/2011 07:42:55:165 Successfully processed file, deleting C:\Documents and
Settings\jsmith\Application Data\SalesLogix\Outlook\TempMailDir\MSG\S-testing to see if this
logs to d.MSG
[Info] 6/10/2011 07:42:55:165 Successfully processed file 'C:\Documents and
Settings\jsmith\Application Data\SalesLogix\Outlook\TempMailDir\EML\S-testing to see if this logs
to d.EML'
Scenario 2:
There are two contacts with the same E-mail address:
[Info]
[Info]
[Info]
[Info]
[Info]
[Info]
[Info]
[Info]
6/10/2011 07:44:54:145 Processing "Two contacts exist with same E-mail address"
6/10/2011 07:44:54:145 Build list of addresses to process
6/10/2011 07:44:54:145 Processing 1 addresses:
6/10/2011 07:44:54:145 John.Smith@testaccount.com
6/10/2011 07:44:54:145 Building HTTP request
6/10/2011 07:44:54:145 Looking for contacts
6/10/2011 07:44:54:192 Searching for SalesLogix Contacts
6/10/2011 07:44:54:410 Found contact Adams, Georgia
Sage Software
Page 5
[Info]
[Info]
[Info]
[Info]
[Info]
[Info]
6/10/2011 07:48:05:559 Processing "Two contacts exist with same E-mail address"
6/10/2011 07:48:05:575 Build list of addresses to process
6/10/2011 07:48:06:731 Processing 1 addresses:
6/10/2011 07:48:06:731 john.smith@testaccount.com,
6/10/2011 07:48:06:731 Building HTTP request
6/10/2011 07:48:06:731 Looking for contacts
Sage Software
Page 6
Prompt for Duplicate Contacts: If there is more than one contact or lead in the Sage
SalesLogix database that has the same E-mail address, the user receives a prompt for
which contact or lead to select.
Prompt for Contacts: Prompts the user to select which contact or lead to associate the
history item to.
Prompt for Unresolved Contacts: If Sage SalesLogix cannot locate a contact or lead with
that E-mail address, the user receives a prompt that it cannot find the entry in the
database.
Display History Details before saving: The Complete E-mail dialog box opens so the user
can change history notes and then schedule a follow up activity.
What if I do a Drag and Drop and not a SendSLX or Record to History? The option to prompt the
user to Log to History on a Drag and Drop is actually controlled through the User Options in the
Sage SalesLogix Web Client. With Sage SalesLogix 7.5.4, the prompts for when a Contact or
Lead is not located or when a duplicate is found have been removed. This is because those
options are being controlled through Desktop Manager. The user option in the Web Client for Log
to History strictly deals in the scenario where the user is performing a Drag and Drop of the Email into Sage SalesLogix.
Sage Software
Page 7
Export to Excel
Drag and Drop Library Files (Administrator only)
If you have users who will not be performing SendSLX or Record to History, simply remove the
DesktopManager.exe from the Startup so it does not load for those users. However, Desktop
Manager must be configured and active for users who will be performing SendSLX or Record to
History.
Disabling the option for SendSLX and Record to History after Desktop
Integration has been installed and configured/used
1. Exit the Desktop Manager from the system tray.
2. Unregister the slmn.dll. For example, for Windows 2003:
regsvr32 C:\Documents and Settings\user\Local Settings\Application Data\Sage\slmn.dll u
3. Delete any pending e-mails to be recorded to History. For example, for Windows 2003:
C:\Documents and Settings\user\Application Data\SalesLogix\Outlook\TempMailDir\EML (and if exists,
\MSG) folders
4. Remove DesktopManager.exe from the Startup folder for each user logging into the system. For
example, for Windows 2003:
\Documents and Settings\user\Start Menu\Programs\Startup)
Installation Paths for Desktop Manager:
Window XP: C:\Documents and Settings\%user%\Local Settings\Application Data\Sage
Windows 2003: C:\Documents and Settings\%user%\Local Settings\Application Data\Sage
Windows 7: C:\Users\%user.domain%\appdata\local\Sage
Changing the option to Save attachments with e-mail (MSG format) to Save
attachments as individual files
Note: The Desktop Manager will need to be closed and re-opened for the changes to take effect.
1. Log into the Administrator
2. Select Tools > Options > Outlook and change from Save attachments with e-mail
(MSG format) to Save attachments as individual files.
3. Close the browser.
4. Exit the Desktop Manager.
5. Click Start > All programs > Startup > Desktop Manager.
6. Create an E-mail in Outlook and add an attachment.
7. Click on SendSLX.
8. Log into the Web Client and find the contact to whom the E-mail was sent.
9. Check the Attachment tab and notice that the attachment has been saved.
This will cause the attachments to be saved as individual files on the Attachments tab
and the E-mail will save to the History tab with the body of the E-mail in the Notes field.
Sage Software
Page 8
Intellisync
History Filter
Intellisync synchronizes History table information as well as Contacts and Activities. With Sage
SalesLogix 7.5.4, an Intellisync History filter has been added within the web.config file in the
Intellisync Portal. This will allow the administrator to determine if the History table information will
synchronize or not, and if so, how much of it will.
To customize the history filter
1. Open the web.config file in the Intellisync portal that has been deployed on the Web
server.
2. Locate the following and modify as necessary:
<intellisyncConfiguration maxMonthIteration="13" maxDayIteration="31"
maxWeekIteration="53" maxYearIteration="5" invalidStringList=""
invalidReplaceCharacter="!" syncHistory=true prevHistoryDays=30 />
syncHistory This determines if any history should be synced at all. Turning off will
negate the prevHistoryDays setting. Default=true.
3. Repeat steps 1-2 for each Intellisync portal that has been deployed.
Sage Software
Page 9
Installation
The command line to install Intellisync silently is: <path>\IntellisyncSetup.exe /s
For example: c:\test\intellisyncsetup.exe /s
After Intellisync is installed, the following files and folders should exist:
Location
\Documents and Settings\[windows user profile]\Application
Data\Sage\Configurations
\Program Files\SalesLogix\Intellisync
File/Folder Name
Intellisync XML
Intellisync XML.cfg
Iloptcfg.cfg
IS4Web.ini
IS4WebUI.ini
PTTrace.log
1033 many files inside here
Action Engine
Connectors
DATA
Desktop Setup
Help
3rd_party_copyright_license.txt
Attendees.dll
ConfigurationUpgrade.dll
ConfigurationUpgrade.dtd
ConfigurationUpgrade.xml
Conn_install.cfg
ConnectorRequestHandler.dll
CXLServer.dll
Eula.rtf
Iloptcfg.cfg
IlSdk.fil
IlsyncEx.dll
IlTif32.dll
Ilx32.dll
IS4Web.exe
IS4WebRuntimeData.dll
Mimepp_core.dll
PtAttach.dll
PtSSLog.dll
PushSyncCallback.dll
ReadMe.txt
SyncConfirmation.dll
SyncConflict.dll
System.dtd
UserLocMgr.dll
Zlib1.dll
After login and configuration, the following files and folders should exist:
Location
\Documents and Settings\[windows user profile]\Application
Data\Sage\Configurations\
Sage Software
File/Folder Name
Con_Intellisync XML_username
Con_Intellisync
XML_username.cfg
Page 10
When you synchronize the first time, these files get generated:
\Documents and Settings\[Windows User Profile]\Application
Data\PushSyncData
PushSync.dat
PushSyncLog.log
Oracle
Chunksize
In row and out of row lobs
A lob can either be stored along the row to which it belongs (called in row storage) or in the
lobsegment (called out of row storage). The maximum size for in row lobs is 3964 bytes.
Chunk size
A lob's chunk size determines the granularity of allocation for out of row lobs.
The Implementation Guide says that when using Oracle databases, the chunksize should be set
to 3000. If you get anomalous results, try setting it to 8000.
To set
1. In the Sage SalesLogix Connection Manager, edit the Oracle database connection.
2. Click the All tab and double-click Extended Properties.
3. In the Property Value box, type chunksize=8000, and click OK.
Provider
Installing History Provider Extension
1. Browse to the SDK Examples folder on the install media.
2. Copy the contents of the ProviderExtensions folder to the server.
3. Edit "test.udl" with Microsoft OLEDB Core Services application selecting the Sage
SalesLogix Server, SalesLogix database name, the SalesLogix User Name and the
SalesLogix Password. Check "Allow Saving Password".
Note: test.udl may be read-only when copied from the install media. Verify that the readonly attribute of the file is cleared.
Sage Software
Page 11
SpeedSearch
Speedsearch Service logging
To turn on informational logging for the SpeedSearch Service, add the following registry key:
HKEY_LOCAL_MACHINE\Software\SalesLogix\SpeedSearch\Service
Add String value: Debug
The logging information, which is recorded to the Windows Event Viewer, can assist in
troubleshooting issues related to building the SpeedSearch Indexes. Once logging is enabled, run
the index(es) again. The information will also include the SQL statements it builds up to retrieve
the index data.
Web Client
Promote to Dashboard for non-admin users
A non-admin user intending to use the Promote to Dashboard option from an entity must create
a dashboard page to promote to.
When a user selects Promote to Dashboard, a popup appears with the text Display this group
list on the following dashboard page. Only the pages (tabs) that the user has permission to write
to are displayed. Because the default pages, My Dashboard and Sales, are owned by the
administrator, a non-admin user does not have write permissions to them.
In the Opportunity or Sales Order Product data grid, after selecting a new Price Level
from the drop down combo box, focus must be removed from the Price Level field in
order for the new Price to display in the data grid
In the Opportunity or Sales Order Product data grid, the Adj Price (User) is not editable
because both the Adj Price (Base) and Adj Price (User) are bound to the same property.
In order to edit the Adj Price (User) field, the Product record must be edited from the data
grid and the field is edited from within the Edit Product form.
When multi-currency is enabled, the Adj Price column labels do not display the (User) or
(Base) designation. This is due to both fields being bound to the same property (FR 180962). In the data grid, the left Adj Price column is (Base) and the right Adj Price column
is (User).Likewise in the Edit Product form. The top Adj Price field is (User) and the
bottom is (Base)
Sage Software
Page 12
Group Lookups
If the lookup result group is filtered, performing a group lookup may not return the correct results.
When performing a group lookup, make sure the lookup result group is not filtered.
Windows Authentication
Passwords and Windows Authentication
A user attempting to log in to the Sage SalesLogix Web Client receives Your password has
expired. Please change it. However, Windows Authentication is being used for logins.
To resolve this error, the administrator should set the expiration days to 0 in the Sage
SalesLogix Administrator under Tools> Options> Passwords> Days until password expires. If a
value other than 0 has been set, it will override Windows Authentication once it passes that
value.
Sage Software
Page 13
Open Administrator.
In DB Manager, add a SLXBoolean (CHAR(1)) field.
In Application Architect, Update the entity with the new field.
Build the portal.
Add the field to the appropriate form. Ensure you make it a Checkbox control.
Build and deploy the portal.
Open the Web Client, open the form, check the box, click Save, and you receive the
following error: String or binary data would be truncated
Update statement generated:
UPDATE DEFECT SET MODIFYDATE = [DBTYPE_DBTIMESTAMP,20100805
16:40:12.000], ISEFFICIENCYIMPROVEMENT = [DBTYPE_STR,"True"]
WHERE DEFECTID = [DBTYPE_STR,"fYV3MA001MYO"]
To Fix
Sage Software
Page 14
Web Admin
Field Level Security Profile
The default security profile for a new user (except webviewer User) will be Team Owner Profile
and WebViewer user is Read Only Default.
A user appears in their calendar list. Do NOT remove a user from their own Calendar
since this will remove the users access to their own calendar.
If a user does not appear in the calendar list, the user whose profile you are editing has
no access to that user's calendar
If a user appears in the list, they can view the selected user's calendar (when Add, Edit,
Delete and Sync are not selected, the user has read-only access)
The Administrator user appears in a user's calendar list and cannot be removed
Sage Software
Page 15
Users Lookup
Use usercode for lookups using user types. The user types don't appear to have a mapping
between the type codes: W, N etc. and the types names: Administrator, Network, etc.
User Type
Usercode
Network User
Remote User
Concurrent User
Template
Add-on User
Retired User
Setting the Ticket Status pick list attribute to "Allow Multiple Selections" will display the
pick list item as an ID in the Ticket status field.
Setting the Return Type pick list attribute to "Allow Multiple Selections" and selecting all
the pick list items for that field, an error displays when saved. This field is not currently
configured to hold multiple selections. Feature Request 1-75269 has been logged for this
request.
Setting the Opportunity Close Probability pick list attribute to "Allow Multiple Selections"
causes this field to not display the selected pick list item.
Setting the Source (Ticket) pick list attribute "Allow Multiple Selections" causes the field
to display blank when multiple items are selected.
Setting the Defect Priority pick list attribute to "Allow Multiple Selections" causes an error
when multiple items are selected for this field.
Setting the Defect Urgency pick list attribute to "Allow Multiple Selections" causes the
Defect Urgency field to display as an ID.
Setting the Defect Status pick list attribute to "Allow Multiple Selections" causes the
Defect Status field to display as an ID.
Admin
Password Options (Administrator)
If "Password must contain numbers and letters" is checked in Password Options, make sure the
default password contains numbers and letters otherwise an error message (Passwords must be
alphanumeric!) is displayed when creating new users in the Web Client.
Integrity Checker
If you add or import users in the Administrator, complete the following steps to ensure the users
function correctly on the Web. Users added in the Web Client do not require these tasks.
1. Create or import the users.
2. Run the following Integrity Checker User tests: Child owner id not in owner,
Parent Owner Id not in Owner, and User Calendar, CalUserId, records not in User
Security
Sage Software
Page 16
Dashboards
Creating a custom tab
The out-of-the-box tab is owned by Administrator, and therefore cannot be edited. In order to
customize the tab, you can copy it and create a new tab.
To create a personal tab
Right-click the default tab and select Copy Tab, name the tab and click OK.
The charts in the new tab can now be customized.
Column Chart
The Goal parameter sets a value on the Y axis to draw a horizontal green line in the graph. The
following table gives an example of the data format required.
Valid Data
20000000
20000000
Sage Software
Goal Data
Invalid Data
20M
20,000,000
Page 17
Display Tips
Use the following techniques to maximize the full functionality of displaying and reviewing charts:
Create custom groups for displaying chart data (they will be available in the group pick list)
Turn off the name display in the Edit Chart Options. Graphs can become illegible when
several items have a similar value. The data can be viewed by hovering over the chart
objects.
Optimize the chart display by setting the Column Width in the Tab Edit Options.
Desktop Manager
If you send an e-mail to contacts or leads with duplicate e-mail addresses using the Desktop
Manager SendSLX button and the Prompt for Duplicate setting is not selected, then each of the
contact or lead will receive an entry in the history table for the email.
Note: Prior functionality was that when sending emails to Contacts/Leads with duplicate email
addresses and the Prompt for Duplicates deselected only the Contact/Lead with the most
history would receive an entry in the history table.
Sage Software
Page 18
Mail Merge
Macro Security Error When Mail Merge Performed with Vista and Office
2007 Word
Receive the following error when doing any type of Mail Merge using Vista and Office 2007 word.
"The function you are attempting to run contains macros or content that requires macro language
support. When this software was installed, you (or your administrator) chose not to install support
for macros or controls"
Ensure the following:
The site has been added to the "Trusted" sites.
"Protection Mode" is turned off
"Initialize and script ActiveX controls not marked as safe for scripting" is set to Enable or
Prompt.
Go to Internet Options>Security>Trusted Sites> and click the Custom level button. Select
Initialize and script ActiveX controls not marked as safe for scripting and set to Enable
or Prompt.
If the above does not correct the issue do the following:
1. Do one of the following:
Vista - click Start> Control Pane> Classic View> Programs and Features
Microsoft Office 2007 - Change >Add or Remove Features> Continue and expand
Office Shared Features
2. Set Visual Basic for Applications to Run from My Computer.
3. Click Continue and follow the prompts.
When performing a Mail Merge in Citrix, the image comes across as a red
cross
Using folder redirection in an active directory such as roaming profiles will cause some
SalesLogix paths to be redirected to the wrong location. Using an UNC path (such as
\\Servername\...) can create this problem.
Sage Software
Page 19
MailMergeAttachmentsTempPath
MailMergeCachePath
MailMergeDataPath
MailMergeDebugPath
MailMergeFaxTempPath
MailMergeLogPath
MailMergeTempPath
Note: The %user% variable is not used by path manager. In order to use path manager
to define the paths used by Mail Merge you should set the location from step 1.
Example:
MailMergeAttachmentsTempPath = M:\SomeLocation\MailMerge\Temp\Attachments
MailMergeCachePath = M:\SomeLocation\MailMerge\Cache
MailMergeDataPath = M:\SomeLocation\MailMerge\Data
MailMergeDebugPath = M:\SomeLocation\MailMerge\Debug
MailMergeFaxTempPath = M:\SomeLocation\MailMerge\Temp\Fax
MailMergeLogPath = M:\SomeLocation\MailMerge\Log
MailMergeTempPath = M:\SomeLocation\MailMerge\Temp
4. If the Web Client running on Citrix, you must also add:
WebClientAttachmentsPath
WebClientLibraryPath
Example:
WebClientAttachmentsPath = M:\SomeLocation\WebClient\Attachments
WebClientLibraryPath = M:\SomeLocation\WebClient\Library
Note: User specific data will be added in a subfolder of each of these locations using the
user's USERID value (e.g. M:\SomeLocation\MailMerge\Temp\ADMIN).
5. Once the correct paths have been set, the modified keys must be made active. To
activate the key remove the <> symbols from the path. Active keys are now used by
every user login on this server.
Sage Software
Page 20
Provider
Connection Manager Settings
A Sage SalesLogix connection can be created programmatically without using the Sage
SalesLogix Connection Manager. Since this connection is not created in the UI, the
SYSTEMINFO table in the database must be updated manually. When creating a connection
manually, there is no check to ensure what you are passing is valid.
The connection file is stored in %AllUsers%\Application Data\SalesLogix\SlxOleDBConfig.dat.
But it is encrypted and cannot be modified directly.
You will want to access it through COM, which there are two examples: one for VBScript and
another with C#.
Build the interop dll as interop.SlxOleDBConfig.dll.
They both show the main calls you would need to make to build your connection.
VBScript:
'=============================================
Sub Create_Connection()
Dim oConnMgr
Dim svConnStr
'On Error Resume Next
Set oConnMgr = CreateObject("SlxOleDBConfig.DBConfigMgr")
svConnStr = GetConnString("SalesLogix_Test", "sysdba", "masterkey",
GetMachineName() & "\SQLEXPRESS")
'oConnMgr.DeleteAlias "SalesLogix_Server", svConnStr
oConnMgr.AddAlias "SalesLogix_Test", svConnStr
oConnMgr.SetConnMgrInfo "SalesLogix_Test", 51101, GetMachineName()
oConnMgr.SetRWPass svConnStr, ""
oConnMgr.SetROPass svConnStr, ""
Set oConnMgr = Nothing
End Sub
'=============================================
'=============================================
Function GetConnString(aDB, AID, aPW, aSRV)
GetConnString = "Provider=SQLNCLI.1;Password=" & aPW & _
";Persist Security Info=True;User ID=" & aID & _
";Initial Catalog=" & aDB & _
";Data Source=" & aSrv
Sage Software
Page 21
End Function
'=============================================
C#:
private static void ConfigureSLXConnection(string SQLServer)
{
try
{
interop.SlxOleDBConfig.DBConfigMgr configMgr = new
interop.SlxOleDBConfig.DBConfigMgr();
string svConnStr = GetConnectionString("SalesLogix", "sysdba", "masterkey",
SQLServer);
try
{
configMgr.DeleteAlias("SalesLogix");
}
catch { }
configMgr.AddAlias("SalesLogix", svConnStr);
configMgr.SetConnMgrInfo("SalesLogix", 51101, ipInternal);
configMgr.SetRWPass(svConnStr, "");
configMgr.SetROPass(svConnStr, "");
}
catch { }
}
private static string GetConnectionString(string dataBase, string userId, string password,
string server)
{
StringBuilder sb = new StringBuilder();
sb.Append("Provider=SQLNCLI.1");
sb.Append(";");
sb.Append("Password=");
sb.Append(password);
sb.Append(";");
sb.Append("Persist SecurityInfo=True");
sb.Append(";");
sb.Append("User ID=");
sb.Append(userId);
sb.Append(";");
sb.Append("Initial Catalog=");
sb.Append(dataBase);
sb.Append(";");
sb.Append("Data Source=");
sb.Append(server);
return sb.ToString();
}
}
Sage Software
Page 22
For a 32-bit machine, double-click the file in the file manager and run
C:\Windows\system32\rundll32.exe "C:\Program Files\Common Files\System\OLE
DB\oledb32.dll",OpenDSLFile <SalesLogix install folder>\test.udl
3. With the blank UDL open, open the Data Link Manager.
4. Create a new database connection and make sure you select the SalesLogix OLE DB
Provider on the Provider tab.
5. Test and save the UDL file.
6. Move the UDL file to all computers that require a connection to Sage SalesLogix. By
default, the file should be stored in C:.
Sync
FTP SYNC
Changing Sync to run using debug mode:
Run Regedit and navigate to the following location:
32 bit OS:
HKEY_LOCAL_MACHINE\SOFTWARE\SalesLogix\Synchronization
64 bit OS:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SalesLogix\Synchronization\
Create a new String Value in that location called: DebugFTP
The value will be empty. As long as the key exists it will be running in debug mode.
This will enable FTP debug messages to the SyncServer\SyncClient Console or output file.
HKEY_LOCAL_MACHINE
SOFTWARE
SalesLogix
Synchronization
DebugFTP
HTTP SYNC
To create an HTTP site on Windows 2008
1. On the HTTP Server, create a folder where you want the Sage SalesLogix Web site you
create to point. For example, SLXHTTPSync.
2. In the folder you created in the Step 1, create the following three sub folders. Set folder
permissions to Read, Write, and Modify.
o Infiles
o Outfiles
Sage Software
Page 23
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
o FailedTrans
Open Internet Information Services (IIS) Manager.
o Create or use an existing Sage SalesLogix application pool.
o Ensure the identity of the application pool is set to log on with a user that has
Read, Write, and Modify permissions to the HTTP sync folders you created in
Step 2.
o For 64-bit operating systems, enable 32-bit applications.
In the Connections tree view, expand your HTTP Server, and then expand Sites.
Right-click the Sites folder, and then click Add Web Site.
o In the Site name box, type a name for the Web site. For example, SalesLogix
HTTPSync.
o In the Physical path box, browse to the folder you created in Step 1. DO NOT
point to the network logging path.
o Click Connect as, verify Application user (pass-through authentication) is
selected, and click OK.
o Click Test Settings to verify the connection.
o In the Type box, ensure http is selected.
o In the IP address box, select All Unassigned.
o In the Port box, change the port number to port 1024 or higher. Record the port
number you are using. If necessary, port 80 can be used.
o Leave the Host name box blank.
o Click OK.
In the Connections tree view, select your Sage SalesLogix HTTP Web site.
In the Features View under IIS, double-click Authentication.
In the Authentication list, select Anonymous Authentication, and in the Actions pane
click Disable.
Enable Windows Authentication.
o In the Authentication list, select Windows Authentication, and in the Actions
pane click Enable.
o In the Actions pane, click Advanced Settings.
o In the Extended Protection drop-down, select Off or Accept (either option
works), and then click OK.
o In the Actions pane, click the Providers link.
o In the Enabled Providers list, select NTLM and move it to the top of the list.
o Click OK.
In the Features View under IIS, double-click MIME Types.
o In the Actions pane, click Add.
o In the File name extension box, type SLXT.
o In the MIME type box, type text/plain.
o Click OK.
In the Features View under IIS, double-click Directory Browsing.
In the Actions pane, click Enable.
Enable and configure WebDAV (Web-based Distributed Authoring and Versioning).
o In the Features View under IIS, double-click WebDAV Authoring Rules. If
WebDAV Authoring Rules is unavailable, download the WebDAV Extensions for
IIS from Microsoft.
Sage Software
Page 24
Sage Software
Page 25
Sage Software
Page 26
SData
IIS 7.5 in Server 2008 r2
You should test the $system/adapters URL for functionality. A 404 error could be caused by an
authentication issue. Make sure you enable Anonymous Authentication and ASP.NET
Impersonation for the SData portal.
Unicode
Creating Unicode fields in Oracle with Sage SalesLogix
When using an Oracle database, Sage SalesLogix creates new Unicode fields as a varwchar field
type. This field type uses the NLS_CHARACTERSET not the NLS_NCHAR_CHARACTERSET.
Oracle databases need to be created with NLS_CHARACTERSET set to AL32UTF8
This query can be used to determine what character set is being used.
SELECT value$ FROM sys.props$ WHERE name = 'NLS_CHARACTERSET' ;
Sage Software
Page 27
Admin
Filters
If there are filter tabs in the Administrator that display without titles or do not seem to be
functioning correctly, then the tabs can be removed by editing the registry. The registry
entry contains the user filter tabs for the Administrator Users view.
To remove blank filter tabs:
There will be several numbered folders under the following registry location
HKEY_CURRENT_USER\Software\SalesLogix\Administrator\UserFilters\.
Each of these numbered folders is associated to a filter tab.
To determine which one is which, use the FilterName key of each entry
Outlook 2007
To allow the Administrator to send reports through e-mail, you must install the
Collaboration Data Objects (CDO).
Beginning in Exchange Server 2007 and Outlook 2007, CDO 1.2.1 will no longer be
provided as a part of the product installation. As a result, there is functionality missing
that many applications depend on. CDO 1.2.1 is a package providing access to Outlookcompatible objects through a COM-based API.
Download the CDO file from here:
http://www.microsoft.com/downloads/details.aspx?FamilyId=2714320D-C9974DE1-986F-24F081725D36&displaylang=en
Sage Software
Page 28
Synchronization
Conflict Resolution After changing the conflict resolution rules in the Administrator, you must do one
of the following for the new conflict resolution rules to be applicable.
o Close the sync server and then reopen it.
o If using the SyncService, stop the server and start again.
How does conflict resolution handle the following scenario:
o Workstation A issues SQL update statement for field x
o Workstation B issues SQL update statement for field x
Does the sync process determine which statement is applied to the database
based on time or transaction ID?
Sage Software
Page 29
Sage Software
Page 30
Web Host
Field Level Security
Sage SalesLogix SP2 contains a new feature related to Field Level Security (FLS) and Web
Entity inserts. The change pertains to with whether or not new entity inserts will incorporate
Field Level Security.
o False = means that no FLS will be incorporated (this is the default setting)
o True = FLS will be used during the insert.
The web.config file contains the following text:
o When set to true, ApplyFieldLevelSecurityOnInsert tells field-level security to use the
security configuration when inserting an entity. If this value is set to false, the user
may set entity properties, regardless of how field-level security is configured for the
user. The default is false.
Attachments
When attaching files to accounts, contacts, etc, you may find you are unable to attach
any file over 4MB in size (4,096KB). By default, ASP.NET limits the max size of a request
to 4MB. This is specified in the machine.config and can be overridden in the web.config.
o To increase the size of the upload this will have to be changed manually in the
web.config. Change the maxRequestLength parameter of the <httpRuntime>
section in the Web.config file. (you will need to reset IIS or the Personal Web
Server in order to see the change in the Web Client)
Note: When the maxRequestLength attribute is set in the Machine.config file and
then a request is posted (for example, a file upload) that exceeds the value of
maxRequestLength, a custom error page cannot be displayed. Instead, Microsoft
Internet Explorer will display a "Cannot find server or DNS" error message.
If you want to change this setting for programs on the computer and not just this
ASP.NET application, you must modify the Machine.config file.
By default, the <httpRuntime> element is set to the following parameters in the
Machine.config file:
<httpRuntime executionTimeout="90" maxRequestLength="4096"
useFullyQualifiedRedirectUrl="false" minFreeThreads="8"
minLocalRequestFreeThreads="4" appRequestQueueLimit="100" />
The Machine.config file is located in the \System
Root\Microsoft.NET\Framework\Version Number\Config folder.
Sage Software
Page 31
Database Schema
There are two new fields within 7.5.2
ACTIVITY:ATTACHMENTCOUNT
HISTORY:ATTACHMENTCOUNT
These are new fields to represent if the Activity or History has an attachment.
Crash Dump
How to get a Crash Dump
On the web server, please do the following:
1. Install the Debugging Tools for Windows
(http://www.microsoft.com/whdc/devtools/debugging/default.mspx) and make a note of
the install path. You will need to refer to this later if you change it from the default.
2. Navigate to the SlxClient website. Ensure that a w3wp.exe process exists.
3. Open up a command prompt.
4. Run the following command (modify paths where appropriate): -->cscript "C:\Program
Files\Debugging Tools for Windows (x86)\adplus.vbs" -crash -iis -NoDumpOnFirst -o
c:\Temp
5. In most cases, an ADPlus message box will pop-up providing a warning about the
_NT_SYMBOL_PATH. You can ignore this warning and click OK.
6. You will now get a message box that ADPlus is now running in CRASH mode. Please
note the path (which exists in the folder you specified for adplus.vbs) as you will need to
refer to this later once a crash occurs.
7. You should see a couple new console windows in the task bar. Do not close these.
8. When you notice that a crash has occurred, navigate to the folder mentioned in step #6,
and look for a file with a dmp extension. If one exists, you may now close the other
ADplus windows, zip up the entire folder containing the dmp file and save it.
Memory Dump
How to get a memory dump from a SalesLogix Web Server:
1. Install the Debug Diagnostic Tool.
http://www.microsoft.com/downloads/d...displaylang=en
2. Launch DebugDiag v1.1 from the Start Menu.
3. Cancel out of the Rule Wizard.
4. Go to the Processes Tab.
5. Right-click on the correct process and choose: Create Full Userdump.
The full userdump should be fine in this case as getting the mini userdump with all the options
would require using WinDbg.
1. To generate a crash dump automatically upon a failure:
2. Run DebugDiag.
3. In the "Select Rule Type" dialog, which will be shown when you start the application,
choose "Crash", and then "Next".
Sage Software
Page 32
Process Orchestration
In order to monitor DBEventing in real time, close the DBEventing service in the "Manage
Computer" console and instead start the DBEventing application using the following
command: c:\Program Files\SalesLogix\DBEventingService.exe /Console
SData
SData is case sensitive - note the Contact property "LastName" in the following request:
http://localhost:3333/sdata/slx/dynamic/-/contacts?where=LastName eq 'Smith' returns
list of Smiths.
If the property were spelled "lastName", the request would fail:
http://localhost:3333/sdata/slx/dynamic/-/contacts?where=lastName eq 'Smith' returns an
error.
Sage Software
Page 33
Oracle
To find the version of Oracle
Start SQL Plus from the Oracle tools, and enter the username, password and the hoststring. (If
they are available to you). The command line program is sqlplus.
Normally, SQL plus reports the version it is running, but if it does not, type the following command
into SQL plus.
select * from v$version
where banner like 'Oracle%';
SQL Express
When running on Windows 7 and Windows 2008 R2, you must install SQL 2008 SP1 to be able
to attach a database. This can be done via Windows Update. SQL Express 2008 is not
compatible with Windows 7 or Windows 2008 R2 Server until Service Pack 1 for SQL Express
2008 is installed.
With any OS, on machines running SQL Express 2008 that need to attach a remote database
(Remote Client, Remote Office, Disconnected Web Client), SQL 2005 Backwards Compatibility
must be installed. Currently Sage only installs SQL 2005 Backwards Compatibility with the
Sage Software
Page 34
Web Client
Active Mail
Active Mail cannot run in protected mode (where applicable). This needs to be
unchecked in the IE options under the security tab.
When Active Mail is configured in the Web Client it must be run as a trusted component
(Active Mail includes both Mail Merge and Send SLX components). This is a requirement
because of the locations it must read from and the .SLM files that it must delete on the
user's computer. It is also required for mail merge because of the OLE automation
involved. In order to make Active Mail trusted the Sage SalesLogix Web site must be
added to the trusted locations and the following trusted security settings must be set:
Default trusted settings plus the following:
Initialize and script ActiveX controls not marked as safe for scripting (Enable)
o Script ActiveX controls marked safe for scripting (Enable)
SLMN.dll
The SLMN.DLL (SLMN) implements an Outlook add-on known as the SalesLogix Mail Notification
add-on. When a user clicks Send SLX or Record to History in Outlook this add-on generates a
special Outlook Message file with the file extension .SLM. The .SLM file is created in the
SalesLogix Outlook Temporary Mail Directory. The default location of this client-side directory is
as follows:
Windows XP and Windows 2003
C:\Documents and Settings\%UserProfile%\Application Data\SalesLogix\Outlook\TempMailDir
Sage Software
Page 35
SlxEmailNotifier.dll
The SLXEmailNotifier.dll (SLEN) implements an ActiveX control whose sole responsibility is to
process Send SLX and Record to History activity generated by the user within Outlook. It does
this by monitoring the TempMailDir location. When it finds one or more .SLM files it starts
processing them. It first identifies the Contact or Lead, with user interaction if required, and then
creates the associated database records (HISTORY, ATTACHMENT, and if applicable,
TICKETACTIVTY).
If the Outlook Message has attachments, the user is prompted to ask if he or she would like to
save those attachments as separate attachment files in the ATTACHMENT table. Beginning in
SLX version 7.5.0, the .MSG file itself is inserted as an associated attachment on the Web, apart
from the general attachment processing aforementioned (the .MSG file is always uploaded and
associated with the Contact or Lead. Note: 7.5.3 will introduce an option for this). Since there will
always be an attachment uploaded by SLEN, it is necessary for the Web server to have access to
the attachment path as defined in ADMIN.EXE.
Note: When Active Mail is configured in the Web Client it must be run as a trusted component
(Active Mail includes both Mail Merge and Send SLX components). This is a requirement
because of the locations it must read from and the .SLM files that it must delete on the user's
computer. It is also required for mail merge because of the OLE automation involved. In order to
make Active Mail trusted the Sage SalesLogix Web site must be added to the trusted locations
and the following trusted security settings must be set:
Default trusted settings plus:
o Initialize and script ActiveX controls not marked as safe for scripting (Enable)
o Script ActiveX controls marked safe for scripting (Enable)
<add key="CacheActivityRemindersResultTimeout"
By adding this line in the SalesLogix.xml config the refresh rate will change to 1 minute. Changing
this setting might impact performance.
Sage Software
Page 36
Sage Software
Value
Current Date
Regular Order
Sales Order
USD
1
None
Page 37
The data used for the remaining pre-populated fields are described in the following table:
Pre-populated field
Last History Record
None Just logged in
Standard Defaults
(No Accounts,
Contacts, Opportunities
or Sales Orders have
been accessed)
Contact
Standard Defaults +
Account
Account associated with the contact from the
last history record
Account Manager
Account manager of the Account
Bill/Ship Contact
Contact from the last history record
Bill/Ship Address
The primary address for the contact
Account
Standard Defaults +
Account
Account from the last history record
Account Manager
Account manager of the Account
Bill/Ship Contact
Primary contact
Bill/Ship Address
The primary address for the contact
Opportunity
Standard Defaults
+
Account
Account Manager
Bill/Ship Contact
Bill/Ship Address
Notes:
1. For Opportunities there is a difference between New Sales Order from the top drop
down menu and Add Sales Order from the Common Tasks in the Opportunities
detail view. Add Sales Order includes the Products associated with the opportunity.
2. Account, Billing and Shipping Address fields must be completed before products can
be added or the Sales Order saved (a red asterisk appears adjacent to a field that
requires data).
Sage Software
Page 38
LAN Client
Storing Attachments as a .MSG file
When using the "Save attachments with e-mail message (MSG format) feature, if there
is a Web Client on the same machine as the LAN Client, ensure that the Web Client is
shut down. If the Web Client is active, the attachments will store as individual
attachments on the attachments tab. The .ocx file will override the setting in the
administrator.
Activity Reminder
In the LAN Client, when you close the Activity Reminder by using the "X" the behavior is
the same as snoozing the activities. The alarms are reset (Snoozed).
An alarm and an activity are treated separately. If you dismiss an alarm the activity
remains until it is completed or deleted. The alarm will no longer be active on the activity.
Importing Leads
When importing new lead records from a file where one or more of the records contain
extended characters (for example, , , ,) the characters may not correctly display in the
Preview section of the Lead Import Wizard. In this case, proceeding with the import will
import corrupted characters into your database. To prevent this, resave the import file and
explicitly define an encoding type as UTF-8, Unicode, or ANSI. You can then re-select the file
in Step 1 of the Lead Import Wizard and continue with the import. The characters will display
properly in the preview pane and will correctly import into your database.
Products
Sage Software
Page 39
Administrator
Documents
After changing the Attachments path in the Administrator (Systems > Offices > Sync Options
tab), documents may still be sent to the old path. The original setting appears to be cashed in
the Sage SalesLogix System. To correct this, after using the Administrator to change the
path, restart the Sage SalesLogix system service for every Sage SalesLogix Client connected
to the system.
Application Architect
Quick Forms
It is now possible to cut, copy, and paste controls within a form and between forms.
The following new Quick Form controls have been added :
o
Panel
Use for a single group of controls
MultiTab :
Use where multiple groups of controls occupy the same form space. Choose the visible
group by either clicking tabs or via code. See the Application Architect online Help topic
Setting the Active Tab and Captions on a MultiTab Control for more information.
SparkLine
Enable display of a small, high resolution graphic. The graphics available are Bar Chart,
Bullet Chart, Column, Discrete, Impulse, Pie Chart, and Smooth.
Sage Software
ComboBox
Page 40
Data Grid
Radio Group
SparkLine
Timeline Visualization
The new Lookup Control Setup Wizard guides you thorough setting up the desired
Lookup control properties.
Mashup Debugging
Provides the ability to run all or part of a mashup from the Application Architect.
Web Reporting
The default application pool for Web Reporting should be SLX Web Reporting.
Provider
Tracing Events
The Sage SalesLogix Provider can be set to trace events. The key is
HKEY_CURRENT_USER, "SOFTWARE\\SalesLogix\\SLXOLEDB", "debuglevel". It should
be set to a non-zero value such as -1.
Sage Software
Page 41
To trace communication between SLXServer and SLXSystem, add logging to the SLXServer.
You need to add the HKEY_LOCAL_MACHINE, "SOFTWARE\\SalesLogix",
"EventsLogging" Registry setting and set the DWORD value to 1.
You may need to stop and restart the service.
You can view the output with an application that lets you monitor debug output, such as
DebugView which can be downloaded using the link below.
o
http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx
Synchronization Client
To help prevent problems during the sync process, ensure that your anti-virus software is
configured to exclude active scanning of the WGLOGS directory. You may also exclude the
following directories (optional):
o
Infiles
Outfiles
Sage Software
Page 42
Writecache
Be a Domain user.
Have full rights to the path, if the path is on the local machine.
AlwaysUse=True\False
Login=sa
Pwd=encrypted password
Forced Distribution
If a library document has already been added, and then later the Force distribution option is
checked, this will not force that library item out to remotes.
To force this library item out to all remotes again, change the revision date and ensure that
"Forced distribution of this file" is checked.
The library item should now sync out to all remote users/offices again.
Sage Software
Page 43
LoggingServer
To alter the number of transactions that are written into each WGLog file, add the following
registry entry to the registry of the LoggingServer:
1. Open Regedit and expand HKEY_LOCAL_MACHINE\Software\SalesLogix.
2. Create a new DWORD key named: WGLogTrans. The value of the key can then be
entered. A value of 10 or greater should be entered here (10 being the default value
hard-coded into Sage SalesLogix).
The LoggingServer uses this key to determine the number of transactions to write into each
WGLog file. The default value is 10. Setting this value too high may cause performance
degradation. This is only required within the registry of the machine running the
LoggingServer.
Web Groups
The (pr) in group name stands for Private.
In Query Builder | Layout tabs, there is a property that can be set to create a link to an entity.
The user will have to create the entity page in order for the link to work.Otherwise, the user
receives a message notifying that it cannot find the page:
Example of error message: Creating a link for an Address field:
Server Error in '/SlxClient' Application.
-------------------------------------------------------------------------------The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have
been removed, had its name changed, or is temporarily unavailable. Please review the following
URL and make sure that it is spelled correctly.
Requested URL: /slxclient/ADDRESS.aspx
Sage Software
Page 44
In this example, since there is no Address.aspx page. The user will have to create an
Address.aspx page for this link to work appropriately.
Outlook Integration
To prevent being prompted for graphics below a certain size or specific files, you can edit the
registry:
1. On the Sales Client machine, open the registry:
HKEY_CURRENT_USER\Software\SalesLogix\Outlook
2. Select the MinImageSizeToIgnore registry and edit the size (in bytes) of the images
(JPG, JPEG, BMP, and GIF) to be ignored.
Graphics files with a size below this value will be ignored and a user will be prompted
only if there are other files.
3. Select the IgnoreFileNames registry and create a list of files to ignore, separated by a
";". You may use "*" and "?" wildcards.
The files matching the criteria will be ignored. Example: "*.jpg;jungle.gif". This applies
to all files, not just images.
HKEY_CURRENT_USER
\Software
\SalesLogix
Sage Software
Page 45
Recurring Events
Outlook
Sage SalesLogix
Task
<->
Timeless
<->
Appointment
<->
Timeless Event<-
ToDo
Timeless Activity
Activity
Event
Sage SalesLogix does not support Recurring Events. To fix a previous issue caused by
fanning (creating multiple single occurrences for a recurring event), Sage SalesLogix now
maps Recurring Events FROM Outlook to Timeless Activities in Sage SalesLogix.
If an Event is created in Sage SalesLogix and synced to Outlook all should be fine. If that
Event is changed in Outlook to recurring, the additional occurrences will NOT sync to Sage
SalesLogix (unsupported). Only the single instance will display in Sage SalesLogix.
If a user has a Recurring Event (for example 52 weekly recurring events) which has fanned to
Sage SalesLogix, up to 52 Sage SalesLogix occurrences may exist. When the new engine
runs and attempts to sync Outlook and Sage SalesLogix, the Recurring Event will create a
New Recurring timeless activity in Sage SalesLogix. The single event occurrences will create
duplicate entries on the Outlook side.
A recurring value can now be customized in the Intellisync Web Portal. The following values
will be used when No End Date is selected in Outlook. As Sage SalesLogix does not have
the concept of no end date, these values will be used for Number of occurrences in Sage
SalesLogix (which will sync back to Outlook). The default values are set to the previous
defaults for SLX 7.2.2 and earlier:
o
Daily:
31
Weekly:
52
Monthly:
12
Yearly:
Modify the shortcut created on the desktop to point to the new folder (where the
installation is located). Redistribute the shortcut as necessary.
Modify the UNC paths within the configuration file to point to the new folder (where
the installation is located).
Sage Software
Page 46
Administrator
Logs
To log to a file:
o
Add the following to the command line: /SV=<logfile> /c where <logfile> has the
form vLogPath + '\' + vLogName + '.log'
This will cause the SyncServer to run in Auto mode (meaning no popup messages
and closing when finished).
User Filters
The following registry entry contains the user filter tabs for the Sage SalesLogix Administrator
Users view. If there are tabs that show up without titles, or do not seem to be functioning
correctly, then the tabs can be removed simply by editing the registry.
o HKEY_CURRENT_USER\Software\SalesLogix\Administrator\UserFilters
o There will be several numbered folders under the registry location. Each of these
numbered folders is associated to a filter tab. Use the FilterName key for each entry
to determine which folder is associated to the tab.
Web Host
Performance
In order to cache and improve performance, the following would be best practice for the
following subdirectories in each Portal deployed.
o
CSS folder
Images Folder
Jscript Folder
1.
2.
3.
4.
Application Architect
Application Architect Quick Forms
The 'New Form Wizard' now displays business rules that return IList<type> as the return
value.
Sage Software
Page 47
Deployment Explorer
You may have a permissions issue if you attempt to deploy a portal to a different server.
You must have local Administrator permissions, or be part of the local Administrators group,
to create a Web site or application.
You can create a Web site or application in a non-domain scenario if you have a user on both
machines that are administrators with the same password.
Mail Merge
Compression
Sage Software
Page 48
Provider
Connection Manager using SQL 2008 Native Client
When using the connection manager with the SQL 2008 Native Client, you must edit the
advanced properties of the connection and manually set the Persist Security Info to "True". Then
return to the Connection tab and ensure that the Blank Password checkbox is not checked and
that the Allow Saving Password checkbox remains checked.
SLX Profiler
In order for the SLX Profiler to function correctly in Vista or Windows 2008, the application
being profiled and the SLX Profiler should both be run as admin. (achieved by right-clicking
on the application and selecting 'Run as Admin')
Process Orchestration
Configure additional debug-logging for the Process Host
Sage SalesLogix uses log4net by Apache. Exceptions, errors and startup events are logged
to the Application Event Log as Sage SalesLogix Process Host. Changes to logging can be
made by altering the log4net.config file in the root directory of the process host Web site. A
restart of the Web site will be required. Additional debugging configuration specific to the
Sage Software
Page 49
Sage Software
Page 50
Application Architect
Sage Software
Page 51
This action item provides a way for developers to define a business rule that returns a
Boolean value and takes some action, depending on the result.
The OnFail and OnSuccess properties of this item can be any other action items.
Business Rule:
This action item is a way to invoke a business rule method that does not return a value.
The OnCompleteActionItem is any other action item that should be run when this
completes.
Sage Software
Page 52
There are two ways to make a particular tab visible when a Web page first loads.
1. On the querystring add &activetab=mySmartPartID
o If the form is already mapped to the middle pane, it will stay there.
o If the form is in the main tab area, it will stay there, but it will be open.
o If the form is under the MoreTabs tab, the MoreTabs tab (and the form) will be
open.
o The form will open only when linking from the particular link.
Example:
An Account form has a datagrid of Contact information.
If you want to link to a Contact portal page with the ContactTickets tab active,
add a link column type (QFLinkCol) to the datagrid.
For example:
Add a link column type (QFLinkCol) to the datagrid
DataField : LastName
TextFormatString : {0}
DestinationBindFields : Id
DestinationFormatString :
~/Contact.aspx?entityId={0}&activetab=ContactTickets
2. Open the portal page containing the entity.
3. In Template Information, click Configure to open the template properties.
4. In the Misc list, set the OverrideActiveTab property to the name (ID) of the smart
part.
5. Every time the page loads, the indicated tab will be open.
Web controls:
GroupNavigator control:
This is used to place a navigation control on a form
The record count indicates the number of records in the current group, and the arrows
allow navigation through the group (first, last, next, previous records).
To see how this is used, open the Contact Details form and press the ellipsis button for
the Toolbar property. The GroupNavigator control is added under the Toolbar Editor.
Datagrid control :
In-grid editing is not supported in this release; however, you can add an edit
column type (QFEditCol) that allows you to open a dialog for data editing.
Sage Software
Page 53
Owner control:
This would typically be bound to the Owner property.
The lookup in the Web Client allows selection by user/ team/ system.
User control:
This would typically be bound to the AccountManager property.
The lookup in the Web Client allows selection by various user groups (all valid
login users/ network users/ remote users/ concurrent users/ web users/ admin
user).
The following features are available in the Template Information group box. You can:
change the default number of visible tabs
choose to include the middle pane
choose to include the More Tabs tab
override the active tab when the page loads
enable viewstate
You can enable viewstate for the smart parts added to a page.
Security
Creating a Remote Database:
A Remote path must be provided in the Create Database Options dialog box. For
example, D:\SLXRemoteDB\NewDBs. The Administrator creates the remote database in
this location. The designated folder must exist on the Microsoft SQL Server or MSDE
instance machine and the folder must be shared.
Sage Software
Page 54
Sage Software
Page 55
Synchronization
To script the process of attaching a remote database:
These are the command line parameters.
\ADMIN = Admin Mode (Default is false);
/DB = Path and name of the file to attach (Default is '')
/N = Database Name to use when attaching (default is 'slxRemote')
/A = Attach database (Default is False)
/D = Detach database (Default is False);
\All Users\Application Data\SalesLogix\AttachRemoteSettings.ini is also used;
[Admin]
InstanceName= MSDE instance name
DBName=remote database name
AlwaysUse=True\False
Login=sa
Pwd=encrypted password
Running AttachRemote creates the file.
HTTP Sync
When setting up HTTP sync, ensure that WebDAV (Web-based Distributed Authoring and
Versioning) is enabled in IIS.
If using self signed SSL certificates, each workstation and server accessing the HTTPS site
will require that the self signed certificate is installed locally within Internet Explorer in the
Trusted Root Certificates. This allows the Sync Server(s)/Client(s) to access the HTTPS Web
site without prompting to accept or reject the certificate. Since the Sync process does not
have the ability to deal with this prompt automatically, it will fail to connect unless the SSL
certificate is installed.
Sage Software
Page 56
Synchronization Client
To help prevent problems during the sync process, ensure that your anti-virus software is
configured to exclude active scanning of the WGLOGS directory. You may also exclude the
following directories (optional):
Infiles
Outfiles
Writecache
Synchronization Service
When setting up the Synchronization service, the service user must:
Be a Domain user.
Log on as Service permission.
Have full rights to the path, if the path is on the local machine.
Citrix
Registry Settings for Citrix Environments
The following are the settings for Citrix Environments, These are registry entries under
HKEY_LOCAL_MACHINE\Software\SalesLogix\Sales Client
ToolbarRefresh :
Default (if the registry item does not exist - defaults to 900ms).
This is the default refresh rate for the toolbars. Some users choose 10 seconds or more
to reduce the perceived CPU usage on the system (10000 decimal). This will affect the
rate at which certain toolbar buttons get updated -like the Save button or Copy/Paste.
DontCacheGroups (added to 6.2 SP and above)
Default = F (False implies you will cache groups which will positively affect group
performance. If memory is the concern (as it was in versions prior to Virtual Server Side
Cursors), you can change this setting to T (saves memory but negatively affects
performance).
Sage Software
Page 57
LEADSOURCE
LITERATURE
ACCOUNT
CAMPAIGN
CONTRACT
CONTRACTINCIDENT
OPPORTUNITY
OPPORTUNITY_PRODUCT
PRODUCT
PRODUCTPROGRAM
QUOTA
To drop the constraints or unique indexes in SQL Server 2000, you may use Query Analyzer
/ Object Browser or a script to alter the table. On SQL Server 2005 it can be done through the
Management Studio or with a script.
To drop constraints on Oracle you will need to use a script to alter the table. Most indexes
may be removed through the Manager Console or a drop index script.
Sage Software
Page 58
Oracle 10gR2
On some platforms, it is not possible to import views from a .dmp file using the recommended
permissions for the SLX sysdba user when the server is Oracle 10g Release 2. The additional
permission has been added to the CreateOracleUser.sql script for those who need it.
Administrator
Feature Security (previously Menu Security)
Two new items in 7.0 are Disabled by default for new users:
o
To disable these items for existing users in an upgraded database, use the following
statements for each user you want to change.
o
When modifying Main view tabs in the users profile or Tools/Options/Client Plugins, it is
important to note that only the Main view tab in focus will be altered during the update.
The Main View tab Reset function will only reset the tab that is visible.
When accessing the Query Builder within the Web Client there may be a delay after the
Database schema has been altered to allow for the DBSchema blob to rebuild. Subsequent
attempts to access Query Builder will take less time until the database schema is altered
again.
Sage Software
Page 59
Architect
NavBar and Toolbar Updates
NavBars and Toolbars now support XP icons (transparency, etc.), in addition to bitmaps.
The extra step in Admin.exe to activate NavBars and Toolbars, after they are released in
Architect, has been removed. NavBars and Toolbars can now be released like other plugins.
o
The NavBar groups supplied by Sage SalesLogix are now separate plugins so they may be
released by role.
The ButtonStyle option for a toolbar may be set to Glyph Only, Text Only, or Glyph and Text.
The ButtonStyle for NavBar groups is Glyph and Text (regardless of the option chosen when
it is created). This is by design.
Architect/Bundle Switch
To see all messages, warnings, and errors generated and suppressed when merging
bundles, installing bundles, or releasing plugins in the Admin or Architect, create a new
DWord for the HKEY_CURRENT_USER \ Software \ SalesLogix \ Architect key called
ShowErrors. 1=On. 0=Off.
o
NOTE: You will not be able to differentiate between messages, warnings, or errors.
Abort will stop the bundle action. Ignore will move on to the next bundle action.
Architect/Event Logs
Problems and actions that are not completed are now written to the event log as either
messages or errors.
New property: Binary Stream. This allows binding of a BLOB type database field. It
supports BMP, JPG, WMF and ICO formats.
Where MaxSize option is specified, selecting an image over a specific size will
display an error message.
Developers may now set the tab order for the Tab control in the Architect UI without
having to re-create the control.
Sage Software
Page 60
Virtual Server Side Cursors support has been added. A new DataGrid property
UseVSSC enables or disables Virtual Server Side Cursors.
Chart Control
o
A variety of charts are now available including Line, Bar, Horizontal Bar, Area, Point,
FastLine, Horizontal Line, Horizontal Area, Bubble and Volume Pipe.
Group Customizations
It is now possible to create an ad hoc group for any Main view, including Main views of
custom tables.
Application.BasicFunctions.CreateAdhocGroup now has an optional LayoutGroupID
parameter which allows the layout of a group to be created to match the layout of any existing
group.
Customizable Attachments
All attachment views are now active forms.
All attachment tabs may now be customized.
Attachment tabs may now be created for custom tables.
Localization
Integrity Checker. If the Integrity Checker Tasks do not translate properly, perform the
following:
1. Browse to the folder where the Sage SalesLogix Localization Toolkit was installed
and double-click the SalesLogixINTL.ini file.
2. Below [ProgramsToTranslate], type FileX=SLXDBChecker.exe, where X is the
next available number if there are other executables listed. If there are no other
executables listed, start with the number 0.
3. On the toolbar, click Save.
Sage Software
Page 61
The new Copy URL function gives users the ability to use links to HTML-enabled e-mail
messages, Web pages or the command prompt.
The new Copy/Move Contact feature allows users to assign any Open or Completed item
(such as an opportunity) to another contact associated with the same account or to No
Contact.
The new File Attachment item on the Insert menu is context driven and will assign the
attachment to the Main View entity that has focus.
SendSLX and Record to History functionality works for Leads, but the user will not
receive a prompt. If the e-mail includes an attachment, the user will be prompted to
save the attachment.
It is possible to drag and drop an e-mail from Outlook to Sage SalesLogix for Leads.
If a contact and a lead have the same e-mail address, the history record will be
created for the contact, but not the lead.
Mail Client: When using SendSLX or Record to History, if the e-mail includes an attachment,
the attachment can now be saved in Sage SalesLogix.
EmPulse
If EmPulse e-mail campaigns are not going to be used, the Sage SalesLogix EmPulse
Service may be disabled on the server by setting the startup property to Disable and stopping
the service.
Sage Software
Page 62
Intellisync
To modify the Intellisync configuration file location
1. On the machine where the Sage SalesLogix Client is installed, close the Sage
SalesLogix Client.
2. Click Start, and then click Run.
3. Type Regedit, and then click OK.
4. In the Registry Editor, click in the tree view to expand
HKEY_LOCAL_MACHINE.
5. Expand SOFTWARE, right-click on Sage SalesLogix, point to New, and then
click Key.
6. Type PathManager, and then press.ENTER.
7. Leave Registry Editor open, and then open the Sage SalesLogix Client.
8. In Registry Editor, press F5.
9. In the PathManager folder created in steps 5 and 6, right-click the
IntellisyncPath entry, and then click Modify.
10. In the Value data box, remove the <> from the front of the path. If necessary,
type a new location for the configuration file.
Note: if you only remove the <> from the Value, then the files automatically default to
C:\Program Files\SalesLogix\SLXIntellisync
11. Repeat steps 9 and 10 for IntellisyncUserPath entry.
12. Open Windows Explorer and move the username and username.cfg folders from
Program Files\SalesLogix\SlXIntellisync to the location you specified in steps 10
and 11.
Sales Dashboard
To allow users to display the Sales Dashboard without Activities at the top
1. Open the Sage SalesLogix Administrator.
2. From the Users view, double-click the appropriate users name, and then click
the Security tab.
3. Under Feature Security, in the Entity Name box, select Sales Dashboard.
4. In the Detail View and Lookup View boxes, select an item other than Use
default view.
Reporting
General Reporting
If there are tables referenced in the RecordSelectionFormula that do not exist in the report,
the report may display an error when attempting to set this property. The workaround is to
rebuild the Crystal SQL statement by generating a subquery based on the keyfield for the
main table of the report.
Sage Software
Page 63
Web Reporting
The Report Viewer is written in ASP.Net not ActiveX as in the prior versions. Therefore it is
no longer necessary to download the ActiveX Report Viewer.
Setting the registry key for Web Reporting:
o
FileExpirationTime indicates the amount of time after creation when the report will be
tagged for clean up.
Logging = On means that the slxwebreporting.dll will write a text file in C:\Program
Files\SalesLogix\Web Components\slxwebrpt called ReportHistory.log. The log
contains information from the report generation process and may be helpful in
trouble-shooting issues.
Sage Software
Check the virtual directory that contains the SLXWebReporting.dll. This dll is an
ISAPI dll. The settings for the slxwebrpt virtual directory and COM+ app should
Page 64
Turn the Logging Registry key to ON. Use the information in the
ReportHistory.log for further trouble-shooting.
Security
SpeedSearch Service
o
Must start the SpeedSearch Service once as the Local System account or user who has
Administrator rights to the machine, so that an internal COM object can be registered at
startup, before switching to a specific domain user.
Synchronization Service
o
User must have full access to the folder: Documents and Settings\All
Users\Application Data\SalesLogix and all sub folders.
If the Queuefile path or any of the other default paths from above are changed in
the registry, then the user must have full access to the new paths.
Sage Software
Page 65
Folder Permissions
Running as
Folder
Create
SLXLogging
Server
SLXService
[Logging]\WGLogs
Synchronization
Server
SLXService \ Domain
user
[Logging]\WGLogs
[Logging]\Infiles
X
X
[Logging]\Archives
[Logging]\FailedTrans
[Logging]\SharedLogs
[Logging]\Tasks
[Documents]
[Library]
[ServiceFile]
Sage SalesLogix
Administrator
Domain User
[ServiceFile]
Synchronization
Client
Domain User
[Logging]\Infiles
[Logging]\Outfiles
[Logging]\FailedTrans
[Documents]
[Library]
SpeedSearch
Server
SLXService
[SpeedSearch]
SpeedSearch
Client
Domain User
[SpeedSearch]
Sage Software
Rename
SLXService
Domain User
Read
[Logging]\Outfiles
Synchronization
Service
Sage SalesLogix
Network Client
Delete
Page 66
Support Integration
Returns
o
Defects
o
A Notify User of New Defect flag has been added to the User Profile,
Service/Support tab in the Administrator. When set to True, a notification e-mail
is sent to the user or team member(s) when a defect is assigned.
The ability to add a Defect Task has been added to Sage SalesLogix version 7.0.
Defect Tasks track the time spent working on a defect. Defect Tasks are not
connected to Contracts.
The Defect Owner field governs security. If a logged-on user does not have
security access to the defect owner, the defect will not be accessible.
Contracts
o
The start and end dates are active regardless of the Contract type.
In the Contracts and Tickets views, the records are expandable. Users can
double-click on the ticket activity record to open the Ticket Activities Ticket Main
view.
Tickets
To reassign multiple tickets
o
Note: Tickets with an open or incomplete Ticket Activity cannot be reassigned. A list
of all incomplete Ticket Activities will be listed in the Reassign Ticket dialog.
To zoom in on a ticket record
o
Right-click a Ticket record and select Zoom. A window containing the tickets
description and resolution appears.
Synchronization
Attach Remote Utility
Attach Remote utility will now accept a mapped drive or Universal Naming Convention (UNC)
path for the remote database except when the utility is run using administrative privileges.
This is only possible because the first step when attaching the database is to copy the
Sage Software
Page 67
HTTP Sync
If you have Microsoft Internet Explorer 6.x on your Synchronization Server or Synchronization
Client machine, and depending on how your HTTP site is configured, you may need to
enable Windows Authentication in your browser for HTTP Sync to work.
To enable Windows Authentication
1. From your Synchronization Client or Server machine, open Microsoft
Internet Explorer.
2. On the Tools menu, select Internet Options, and then click the Advanced
tab.
3. Under the Security section, select Enable Integrated Windows
Authentication (requires restart).
Synchronization Client
If you do not receive messages to refresh the Sage SalesLogix Client after a synchronization
cycle, ensure that the Messenger service is running on that machine and restart your Sage
SalesLogix Client.
If an unsupported date format is used, and then synchronized, the following errors appear in
the SyncErrors.txt on the receiving Sync engine:
o
If a non-ISO standard date is sent using anything except \ as a delimiter the error
will be: Error applying ParamSQL transaction XXXXXXX : Invalid argument to date
encode and the SQL statement. The data will not be applied.
If a non-ISO standard date is sent using the \ as a delimiter the error will be: Error
applying ParamSQL transaction XXXXXX: nn\n is not a valid integer and the SQL
statement. The data will not be applied.
Note: the characters in the quotes after the transaction ID will be the first four characters
of the data sent.
Synchronization Server
You can leverage the new multithreading feature even on a single processor box. Each
thread can take advantage of the wait cycles from the other threads.
To configure multithreading
1. On the File menu, select Options.
2.
Sage Software
From the number of threads to use for Account Sends list, and then select
the number of threads to use. (You can use between 1 and 4 threads.)
Page 68
Synchronization Service
If the Sage SalesLogix Server stops for any reason, the Synchronization Service will continue
to run, but it will not continue to synchronize. Once the Sage SalesLogix Server has been
successfully restarted, stop and start the Synchronization Service.
After making a change to an existing SyncServices.cfg file, it is necessary to stop and start
the Synchronization Service before the changes take effect, but it is not necessary to run the
Sage SalesLogix Synchronization Service manually.
If the physical location of the SyncService configuration file is to be changed, the following
steps are required for implementation:
Note: Unless the service is stopped, the Synchronization Service will continue to run
from the old location until all steps have been completed.
1. Move or copy the SyncService.cfg file to the new location.
2. In the Sage SalesLogix Administrator, click Systems, and then click the
SyncAutomation Services tab.
3. Right-click in the tab view and select Modify Service File Location to change
the value in the Host database to the new location.
4. Double-click the service name to open the Service Configuration dialog box
and select one of the jobs.
5. In the SyncServer box, select the correct Synchronization Server.
6. Stop and restart the Synchronization Service. The service will be started using
the SyncService.cfg file in the new location.
If the Synchronization Service is installed on a new machine and the existing SyncService.cfg
file will continue to be used from the previous location, you must follow the steps below.
Follow these steps after the new machine is fully configured and running correctly in manual
mode.
To set registry settings
1. In the Sage SalesLogix Administrator, click Systems, and then click the
SyncAutomation Services tab.
2. Double-click on the Service Name to open the Sync Server Profile dialog box.
3. Click the Browse button to select the new Service Machine.
4. Select one of the jobs, click the SyncServer drop-down button, and then select
the correct Synchronization Server.
5. Stop and then start the SyncService on the new machine.
To read the SyncServices.cfg, the format of the job string in the SyncServices.cfg file is:
<Job Name>|<Database>|<SyncServer>|<Enabled>|<Once>|<DOW>|<Start Time>|<End Ti
me>|<Interval>|<ADO connection string info>|<All or changes flag>
The Daily Schedule time values chosen in the Sage SalesLogix Administrator Service
Configuration dialog box are for the same calendar day only. If you set it to run from 4 PM to
4 AM it will not cross midnight. The service will begin running at 4 PM and run until midnight.
If you set the time value in the Sage SalesLogix Administrator Service Configuration dialog
box for just a few minutes in the future (or a few minutes in the past as you can do for agents
and remote tasks), the Synchronization Service schedules the first job for the time you have
chosen on the next day listed.
Sage Software
Page 69
The old Admin password is stored in the Sage SalesLogix Administrator, and it is
encrypted in the SyncServices.cfg file.
The Sage SalesLogix OLE DB Provider stores the old Admin password until you
log off and then log on to the Sage SalesLogix Administrator again. So if you
update the SyncServices.cfg file before you log out of the Sage SalesLogix
Administrator, you are re-creating the file with the old Admin password.
Synchronization Process
To increase performance, SLXLoggingObj2.dll batches log information in the internal
cache. The log cache is flushed to disk either when its size reaches 100KB or after a twosecond time-out.
All transactions begin as a .qts or .que file. These files are located in C:\Documents and
Settings\All Users\Application Data\SalesLogix\Sync\QUEUEFiles. Changes that are part
of a SQL transaction are held in memory until they are committed. If the transactions are
"rolled back," the changes are removed from memory and never written to disk. When the
SlxLoggingObj2.dll is unloaded, all changes still in memory are flushed to disk to prevent
data loss.
Queue files are created even when a Synchronization license is not present. The queue
file name is time_of_creation.qts_servername_portnumber (from here we use .qts for
simplicity).
When the SLXLoggingObj2.dll creates a queue file, it gets the Sage SalesLogix Server
and Port information from the Sage SalesLogix OLE DB Provider. If the Sage SalesLogix
Server is the local machine (for example, a Remote client or an environment where all
Sage SalesLogix applications are installed on the same machine), the queue files are
created with a .que extension. If the Sage SalesLogix Server is not the local machine (for
example, a Network Client), then the queue files are created with a .qts extension.
Queue files that end with a .qts extension need to be sent to the Sage SalesLogix Server
so that the SLXLoggingServer can process them. When the logging object writes a file, it
sends an event to the SlxSystem.exe. The SlxSystem.exe searches the queue files folder
for anything ending in a .qts extension. When it finds the .qts file it extracts the Sage
SalesLogix Server and Port information, connects to the SlxServer.exe and sends the
.qts files to the Server (through TCP/IP). The SlxServer.exe then renames the queue files
to a .que extension and copies them into the Documents and Settings/All
Sage Software
Page 70
If the SERVERPATH field in the SYNCSERVER table does not have a value,
then the queue file was never generated. In the past, the queue files were
created, but were not sent to the Sage SalesLogix Server.
If queue files are processed without error and a Workgroup Log file is created,
then the queue file is deleted.
If the creation of the Workgroup Log fails, an Event log is generated and the
queue file is moved to the"QueueFiles\Failed" folder.
QUEUE Files
Queue Files can be found
in:C:\Documents and Settings\All Users\Application Data\SalesLogix\Sync\Queuefiles on
each Sage SalesLogix machine. However they only exist in this folder for a few seconds,
unless the Logging process stops or the files are in the Failed folder.
What causes queue files to fail?
o
Only corrupt queue files are moved to the Failed folder on the host Sage
SalesLogix Server. This does not include 0KB files which are deleted when
encountered.
Logic has also been put into the clients to delete 0KB queue files if encountered.
If a client creates a corrupt queue file it will be pushed up to Sage SalesLogix
Server where it will fail and be moved to the QueueFiles\Failed folder. Queue
files should not fail on a client machine.
Queue files can fail if the proper permissions do not exist for the Sync Logs folder. Once the
permissions have been fixed, you will have to move the failed queue files back into the main
queue files folder on the Sage SalesLogix Server.
Not enough disk space:
When the first queue file for a database is processed, the available disk space is calculated
on the drive where the Workgroup Log is created. This value is saved as part of the
initialization information for that database. Each time a transaction is written to the Workgroup
Logs, the size of the transaction is subtracted from the available limit. When the available
space reaches a determined limit (default is 50MB), the SLXLoggingServer will recheck the
Sage Software
Page 71
If the SLXLoggingServer stops for any reason, queue files will continue to generate and be
converted to WGLogs as soon as the Provider is restarted.
Workgroup Logs
The following circumstances will close open Workgroup Logs:
o
Note: In all of the above environments, Workgroup Logs automatically close after 10
transactions occur of the following types: Inserts, Updates, Deletes, and ParamSQL
statements.
To change how many transactions occur before Workgroup logs are closed
1. Create the following registry entry by right-clicking on:
HKEY_LOCAL_MACHINE\Software\SalesLogix.
2. On the New menu, select DWord Value.
3. Name the Value WGLogTrans.
4. Modify the value, select Decimal, and then type the number of transactions per
Workgroup Log in the Value Data field (Sage SalesLogix suggests 50 or 100).
You can modify this as you do your testing.
5. Restart the Sage SalesLogix Server service. Workgroup Logs will close when
either the new number of transactions has been met or the elapsed time period
defined in the Close Workgroup Logs Every setting in Admin has passed.
Note: This setting will only apply to transactions that update the database. Other
transaction types, such as What's New records, get streamed into the Workgroup
Logs differently. So when performing functions such as imports, you may see 10
Workgroup Logs containing 50 transactions (based on the registry setting) and 1
containing 300 What's New updates.
Troubleshooting Sync
Where to look for potential problems:
o
Sage Software
SyncErrors.txt
Page 72
EventLog
Event Viewer Check for any pertinent information for the Sage SalesLogix OLE
DB Provider.
Failed Trans Each Sync Transfer Protocol has its own Failed Transaction
folder.
If you attempt to run the Synchronization Server or Synchronization Client and receive the
message You cannot load more than one copy of SyncClient/SyncServer at a time, ending
the Synchronization Client or Synchronization Server in the Task Manager will not fix the
problem. You must either restart the machine, or run Synchronization Client or
Synchronization Server from a command line with a /reset command.
Logging
To enable additional Debug information in the SLXLoggingTrigger, which is responsible for
logging all Whats New and Attachment logs, you can:
o
If the key exists additional debug messages will output to the system event log of that
client machine.
Subscription
The following values may be seen in the USERSUBCRIPTION.DATA:
o
0=
subscription, no
1=
2=
3=
subscription, no access
4=
subscription, delete
5=
subscription, forced
6=
Accounts with a value of 4 will have a delete statement sent to the remote.
Sage Software
Page 73
Templates
Lead Templates: To create a template based on Leads, Contact fields cannot be added (or
must be removed).
Contact Templates: To create a template based on Contacts, Lead fields cannot be added
(or must be removed).
Web Host
The ASPScripts virtual directory, for the Web site, must have the ASP.NET tab set to 2.0.
ASP.Net v2.0 needs to be an allowed Web Service Extension on both the Web server and the
Web Reporting server if they are on Windows 2003 Server operating system.
Sage Software
Page 74