Company -> Blog...

September 3rd, 2014 by

Swiftpage has released new updates for Saleslogix v8.1.0, SNC 03 and Web Core Update 03. These updates address reported defects and should be evaluated for application to your environment.

Here are the update High Points:

  • These two updates contain a multitude of changes!
  • No More 8-Ball logos!! Saleslogix 8.1.0 SNC Update 03 includes new icons for the Administrator and Architect and Saleslogix v8.1.0 Web Core Update 03 includes a new icon for the Application Architect. (There are additional steps required to update the icons if you are using a Windows 8 or Server 2012 environment)
  • The Saleslogix Reporting Assistant was introduced in 8.1.0 SNC Update 03 to support reports with dynamic parameters on the Saleslogix Web Client.
  • Saleslogix 8.1.0 SNC Update 03 includes a new Integrity Checker library.
************

SNC Update 03 for Saleslogix v8.1.0

This Saleslogix v8.1.0 SNC Update 03 is cumulative, it contains fixes released in previous updates (SNC 01, 02).

The summary of the new fixes are listed below:

Defect Description
11083340: In the Saleslogix Windows Client, dragging and dropping an email to Ticket Activities displays the Complete E-Mail dialog window twice.
12090172: In a localized environment, in the Administrator, the Visible Columns dialog box does not display extended characters correctly.
12090554: In a localized Saleslogix Windows Client, corrupted strings appear in the Confirm Activity dialog box.
12090931: In a localized Saleslogix Windows Client, in the Defect detail view Tickets tab, some extended characters do not display correctly.
13091236: In a localized Saleslogix Windows Client the Toolbars Editor Arguments dropdown list contains corrupted strings.
13091316: In a localized Saleslogix Windows Client extended characters do not display correctly in the Confirmation dialog box Notes field.
13091909: In a localized environment, Cyrillic characters are not saved correctly when creating SpeedSearch indexes.
13092054: In a Russian localized environment, some labels in the Architect Manage Plugins dialog box do not display correctly.
13092110: When a create user is a Disconnected Web Client user, the host database sends inserts for newly created records back to the user who created the record.
13092278: In a Korean Saleslogix Windows Client, the Calendar Month view labels do not display correctly.
13092634: In a Russian localized Saleslogix Windows Client, the Literature Requests Print Labels drop-down list view contains corrupted text.
13092735: In the Architect, using the Application.BasicFunctions.AddMinutesToDate returns incorrect results over periods longer than 4 days, 15hours, and 20minutes (6680 Mins).
13092854: In a Korean Saleslogix Windows Client, the English character “Y” may not display correctly.
13094272: The activity conflict warning does not display when a conflicting activity is scheduled.
13094366: In a localized Saleslogix Windows Client, extended characters do not display correctly in the Ticket Activities Comments preview pane.
13094456: In a localized Saleslogix Windows Client, when viewing or editing an Event, extended ASCII characters in the Location or Notes boxes do not display correctly.
13094457: In a French localized Saleslogix Windows Client, in the Activities list view Events tab the Type information does not display completely.
13094458: In a localized Saleslogix Windows Client, corrupted characters appear in the Activity Confirmation Message dialog box.
13094460: In a localized Saleslogix Windows Client, the Literature Requests delete Warning displays corrupted characters.
13094461: In a localized Saleslogix Windows Client, if a timeless activity includes extended characters and an event is scheduled for the same time, the Conflicting Activity notification does not display the extended characters correctly.
13094473: In a localized Saleslogix Windows Client, the Mail Merge Specific Group list contains corrupted characters.
13094475: In a localized Saleslogix Windows Client, if a Mail Merge contact or lead name contains extended characters, then the extended characters in the file title are corrupted.
13094496: The Application Architect help topic “Changing Build Output or Search Path Locations” contains the incorrect build Search path.
14094604: In a localized Saleslogix Windows Client, a corrupted string occurs in Toolbars Editor window after saving a Toolbar Button or Hint with extended characters.
14094639: In a localized environment, the SendSLX Contact Not Found message Subject/Regarding field does not display extended characters correctly.
14094694: In Query Builder, adding a date field condition with the operator ‘within the last xxx’ causes the error “Error parsing within parameter”.
14094728: In a localized Saleslogix Web Client environment the “Learn more link” on the log on page opens an untranslated help topic.
14094755: Characters with umlauts do not display correctly in the Conflicting Activity notification.
14094916: The Net Extension Manager Help About does not open the correct dialog box.
14094926: In Query Builder, adding a condition with a ‘greater than’ operator causes a “List index out of bounds” error.
14094994: In a French localized environment the Admin help table of contents link to Contacting Saleslogix is broken.
14095020: The SlxLoggingTrigger.dll should allocate memory from the heap in a thread safe manner.
14095023: In the Architect, resizing a checkbox or editbox will cause the control to collapse to 0 size.
14095024: Users with Windows Authentication configured who use SpeedSearch to search for Internal Tickets or History get the “Search found no matches” message when results should have been found.
14095026: Cyrillic characters do not display correctly in the Administrator Users List column names.
14095027: Cyrillic characters do not display correctly in the Administrator when adding a team to user.
14095028: Cyrillic characters in a user name do not display correctly In the Administrator when copying a profile.
14095029: Cyrillic characters do not display correctly in the Administrator Realign Territory view.
14095030: Cyrillic characters do not display correctly in Administrator, Systems, Office Profile tab.
14095033: Cyrillic characters do not display correctly in the Administrator System Report.
14095034: Cyrillic characters do not display correctly in the Administrator Edit Lookups Layout view.
14095141: When more than two databases are set up to be indexed by one SpeedSearch Server, and most incremental indexes are scheduled to build at the same time, dtSearch will fail.
14095244: In the Query Builder changing the order of conditions causes the error “List index out of bounds”.
14095287: If an e-mail with multiple contacts or leads is created from within the Saleslogix Windows Client, and then sent using the SendSLX button a history record is only created for the first contact or lead.
14095290: In a German localized environment the label on the Outlook Sync Connector Options Logging options is truncated.
14095297: Cyrillic characters in Report names do not display correctly in Architect.
14095315: When new user, who was created from an existing user or template, attempts to log on into the Saleslogix Windows Client, the error “Exception ETimeZoneError: The time zone has not been defined for user…” displays.
14095320: In a Russian localized Saleslogix Windows Client, group names do not display correctly in the Literature Request dialog box.
14095321: In a Russian localized Saleslogix Windows client, the icons are truncated on the Attachments tab.
14095324: When moving activities on the Saleslogix Windows Client Calendar, the error “Exception EOleException: Failed to parse SQL Exception location [0058B31E] (saleslogix.exe) IsBrandingEnabled” displays.
14095370: In a French localized environment, when generating an Opportunity By Account report for the Opportunities Closed-Lost or Closed-Win groups no records are reported.
14095391: In the Saleslogix Windows Client, scheduling an event displays the error “Failed to Parse SQL…IsBrandingEnabled”.
14095395: In a Russian localized Administrator applying a bundle displays corrupted characters.
14095404: When using SendSLX, a history record is not created for any Saleslogix contacts or leads if the e-mail is also sent to an e-mail address that is not in Saleslogix.
14095429: Create an SlxReport.Optimize() method that removes a pre-defined printer, discards saved data, and forces the option to use indexes or server for speed on each report and sub-report. This method will be called when a report is stored in or extracted from the database to improve report performance.
14095453: In a Korean localized Saleslogix Windows Client the Schedule/Edit an Event view contains corrupted text..
14095454: In a Korean localized Saleslogix Windows Client the Calendar Week view event descriptions do not display correctly.
14095476: In a German localized environment the Import Wizard version 8.0 does not support extended characters.
14095516: The application server logs the following SpeedSearch error “GetIndexFolderSize Error: Access violation at address 00405343 in module ‘SLXSearchService.exe'”.
14095609: In the Saleslogix Windows Client, when using the Contact Advanced Lookup to look up a contact by first and last name, and then either refreshing the view or selecting delete from the Edit menu causes the error “List index out of bounds (1)”
14095651: After applying 8.1 SNC Update 02, selecting Letter Using Template from the Write menu causes the error “The Mail merge engine encountered and error and cannot continue. The parameter “” could not be located for the query”.
14095658: In a French localized environment some of the Outlook Saleslogix Connector Options labels are incorrect.
14095659: In a German localized environment some of the Outlook Saleslogix Connector Options labels are incorrect.
14095666: In a Russian localized Saleslogix Windows Client the names of copied groups listed in the Group Manager display incorrectly.
14095674: The Saleslogix Windows Client loads slowly when a group has a lot of conditions.
14095676: The Integrations list contains duplicate entries.
14095687: In a French localized Architect the Query Builder does not display the “é” character correctly.
14095692: After a report is released to Everyone and a user, the associated Report family shows multiple times in Saleslogix Windows Client for the selected user.
14095709: While building a SpeedSearch index, an error in the SlxSearchService can get stuck in a loop repeating the error every half second.
14095711: The SlxSearchTrigger will create multiple entries in the IndexUpdates table for a single Account change. The entries will be for other indexes that have a relationship to account in some way.
14095713: When multiple threads are attempting to write to the spDelFiles.txt file at the same time the following I/O error can occur in SlxSearchService ” Error: IndexThread.Execute Line: 14 Error: I/O error 32″.
14095715: In order to limit the number of Indexes that can be built at one time to 5, SlxSearch should spawn no more than 5 active threads at a time, new threads can start when others finish.
14095717: The SlxSearchService should filter queries to IndexUpdates with the indexName to prevent returning more rows than necessary.
14095719: In a localized Saleslogix Windows Client, the Mail Merge History Options view contains untranslated strings.
14095724: Dragging and dropping the Activities tab from the middle pane causes the tab to disappear.
14095746: The SLXConversionUtility is not creating ActivityAttendee records for activities that are associated with leads.
14095748: Errors that occur in the SLXConversionUtility should be written to a log file instead of displaying an error message that causes the SLXConversionUtility to stop.
14095755: Report names that use accented characters are corrupted.
14095762: In a localized Saleslogix Windows Client the Activity Manager Priority column does not display extended characters.
14095763: In a localized Saleslogix Windows Client NavBar labels may be truncated.
14095785: When replying to an e-mail in Outlook 2013, the edit in place ribbon does not have options for SendSLX, VCards, or Saleslogix Library. The options are only available in an e-mail message if the Pop Out button is clicked.
14095788: Allow administrators to enable or disable each Outlook sync option for contact sync, activities sync or tasks sync separately.
14095809: Template names that contain umlaut characters are corrupted.
14095831: Add dynamic parameter support to the Architect.
14095862: SLXConversionUtility displays an SDataSync error when converting accounts/contacts with apostrophes in the email address.
14095896: When a contact name contains umlauted characters the names are corrupted in the mail merge preview window.
14095910: Activities completed or deleted in the Saleslogix Windows client are not updated, completed, or deleted in Google
14095912: Create a tool to map dynamic parameter information for running reports on the Web Client.
14095920: On an Oracle database moving a contact that has a literature request causes the error “Error calling method btnOkClick”.
14095936: Export to Excel for Assets generates a corrupted Serial Number.
14095937: On a multi-byte database the Rmareceivedproduct Lookup does not return any results.
14095980: Notes that are created in the Saleslogix Mobile client do not display correctly in the Windows client.
14095989: The Import Wizard must support Unicode databases and Unicode data.
14095991: When creating new user from a profile in the Administrator Cyrillic characters are corrupted in the Region and Division fields.
14096005: After creating a contact with Unicode characters, the contact name displays question marks instead of Unicode characters in the Contact detail view title.
14096028: On an Oracle database notes/history records do not sync from host database to a remote office.
14096100: In a German environment, one of the items in the Attendee Role picklist needs to be changed.
14096102: Update the Options Sync option topic to add more information about the “On first sync” option.
14096163: The Activities list view is missing the User Calendars button.
14096206: When Application.BasicFunctions.DoInvoke is used the WhenClosed event fires prior to a Report being displayed or opened.
14096207: When performing an e-mail mail merge to a contact with Unicode characters the characters do not display correctly in the generated e-mail.
14096269: Integrity Checker tests fail against Oracle database.
14096276: In the Architect a report cannot be checked out in if the report name includes Unicode characters.
14096334: In the Saleslogix Web Client, calculated fields are showing question marks instead of Unicode characters.
14096335: The Integrity Checker should check for carriage return line feeds in a user’s title
14096372: In a Saleslogix Web Client detail view users are unable to navigate past the 41st record.
14096387: In a Unicode environment the task bar thumbnail view of the Saleslogix Windows client may corrupt non-Latin characters.
14096392: Replace the Saleslogix icon with a unique icon for Application Architect, Administrator, and Architect.
14096397: The SendSLX Duplicate Contact dialog box does not display Unicode characters correctly.
14096425: Single activities completed in the Saleslogix Windows client result in both a completed activity and the original activity in Google.
14096442: In a localized environment extended characters do not display correctly on the Saleslogix Windows client Account Detail view.
14096443: In a localized environment the Import Wizard ‘Getting Started’ dialog box translated header strings do not display.
14096469: In the Administrator extended characters in the ‘Execute SQL’ Available Remotes list are corrupted.
14096558: In a localized environment, in the Administrator, extended chars are corrupted when applying bundle where action contains extended characters.
14096650: Unable to edit or copy Unicode groups. GroupBuilder does not show an error when an edit fails; it just reloads the group , however an error is shown when copying a Unicode group.

************
Web Core 03 for Saleslogix v8.1.0

Web Core updates are cumulative, so Web Core Update 03 for Saleslogix 8.1.0 contains fixes released in previous updates (Web Core 01, 02).

Prerequisite: Saleslogix v8.1.0 SNC Update 03 is required to have been applied to the environment prior to applying Web Core Update 03 to your system.  Please be sure to read the documentation thoroughly if you plan to apply these updates to your system.

The summary of the new fixes are listed below:

Defect Description
12090528: Creating a campaign target list using a custom Contact or Lead group causes the error “Sys.WebForms.PageRequestManagerServerErrorException: We’re sorry, you’ve encountered an error. If applicable, please try again.”
13091921: In a localized environment, Cyrillic characters do not display correctly in the Query Builder View SQL view.
13092141: When exporting an account the resource code displays.
13092478: In the Query Builder, the ‘Use value as literal’ option changes the ‘Value is’ box to a date field.
13092507: An account that is linked to more than 1 endpoint causes issues when creating new contacts.
13096111: When a group includes an Activity field in the layout that is linked to the entity and that link is clicked the error “The file ‘/SlxClient/ACTIVITY.aspx’ does not exist.” displays.
13092722: When editing an activity using steps in a specific order, the activity window may stop responding.
13093127: The items in a multi-select picklist with more than 12 items are misaligned.
13093797: Dashboard tabs with special characters in the tab name cannot be displayed after sharing.
13094064: In a localized environment the Reports view, Report Manager Tasks pane has untranslated strings.
13094174: Creating a new unscheduled activity where the Leader is not the logged in user sets the Leader to the currently logged in user when saved.
13094343: Add support for reports with dynamic parameters.
13094434: In a localized environment, when adding an attachment, the complete dialog box has untranslated strings.
13094508: In a localized environment, the Reports Schedule and History tabs contain untranslated strings.
14094693: The Currency Code filter should be removed from the Currency Look up.
14094751: In the Application Architect, opening the New page Wizard and using the default values causes an error.
14094759: In a German localized environment, some elements do not translate if a language locale was specified.
14094803: Running a report with a parameter that returns a large number of values causes an “Internal Server Error (500)…” error.
14094804: In a localized environment, the Support Ticket Knowledge Base Summary -Sample report contains an untranslated string.
13094920: The Saleslogix Web Client hangs when accessing entities using Internet Explorer 8 and XP.
14094932: When sending an e-mail to more than one contact using SendSLX, the attachment is only displayed as a hyperlink for one of the contacts.
14095110: The Look up Account Manager dialog box is missing the OK button.
14095112: The Query Builder Assign Condition calls the date control when select “Use Value as a literal”.
14095171: Extend the Detail view Group List to show more information.
14095178: Exporting group to Excel with reserved characters in the group’s display name displays the error “An error occurred requesting job manager: Illegal characters in path.”
14095205: In Report Manager, the DateTimeParameter prompt kind is not working.
14095217: The Saleslogix Web numeric control defaults to zero causing unsaved data messages.
14095243: Including the Return Number in a Ticket Group Layout causes the error “We’re sorry, your request could not be completed”.
14095274: Updating Opportunities from the Opportunities list view displays the error “Unexpected error occurred during the execution of a job ‘Sage.SalesLogix.BusinessRules.Jobs.UpdateEntity.job’.
14095335: In a Portuguese environment, the Tools menu, Options screen fails to load in a Firefox browser.
14095396: After moving a column on the Saleslogix Web client Reports list view, leaving, and then returning to Reports the grid does not display.
14095416: Calls that use “typeof ActiveXObject” to determine if ActiveX client support is available are incompatible with IE 11.
14095455: Numeric control cannot display percentiles as numeric values with three decimal places.
14095474: Group tabs queries should only request necessary properties instead of an entire group’s meta data.
14095482: In a localized environment the Reports list view, Schedules tab, Job Name column label is not translated.
14095493: When serializing SDataPayload the property name should be used instead of the Relationship type ResourceName property.
14095509: When sharing a group in the Web Client the Assign Owner control does not list any users, teams, or departments.
14095541: Redundant query arguments in some linked URLs Causes increased payload sizes.
14095544: Updating multiple leads when a filter is applied displays the error “This job cannot run when filters are applied. Please clear all filters and try again.”
14095551: Selecting a filter in Products list view causes the error “We’re sorry, you’ve encountered an error. If applicable, please try again.
14095555: A custom filter consisting of User Look up type and operator of Contains filters the data but causes a “Can not convert object to String” error.
14095563: Users cannot share or delete their own groups.
14095574: Numeric control cannot display percentiles as numeric values with 3 decimal places. if the strict property is false.
14095580: On the Activities list view Past Due and Alarms tabs the summary view does not load.
14095581: If more than 100 users have calendar access to a user, none of those users are able to edit history records of that user.
14095599: During a Google synchronization some changes are synchronized back and forth several times.
14095605: If the Look up Control Binding Mode is set to “String”, then the retrieved “entity” object is not actually used, which means the system is making an unnecessary query.
14095606: The Role filter on the Users List view does not filter the list.
14095617: The Object of type” Eventlog error ‘System.EventArgs’ cannot be converted to type ‘Sage.Platform.Application.ItemEventArgs’.
14095639: When opening a custom filter in a list view the following error displays, Error 500 – “Could not load type ‘Sage.Entity.Interfaces.ICollection`1’ from assembly ‘Sage.Entity.Interfaces’. HTTP status: Internal Server Error”.
14095646: If an occurrence of a recurring activity is completed, synchronized to Outlook, and then the activity is deleted in Saleslogix, the activity is not deleted in Outlook during the next or any future synchronizations.
14095653: The Saleslogix.Reporting.API.dll should not log assembly binding errors for resources (*.resources).
14095688: The Application Architect should allow dragging and dropping nVelocity templates to a bundle.
14095689: The SData activities endpoint sort order is incorrect.
14095691: The SData $Schema call on the gcrm adapter returns an invalid schema import that includes concatenation of dynamic and common schemas.
14095693: The ActivityBeforeChange trigger in Oracle is not using the variable and always defaults to Activity type.
14095735: Users can modify a name field set to read only via double-click action.
14095751: Removing or deleting a contact from the contact sync group in Saleslogix does not remove the contact in Google.
14095752: Deleting an activity in Saleslogix does not delete the event in Google.
14095753: A group’s FirstRow value should not be allowed to be less than 1.
14095754: If a member of an activity declines (deletes) the activity after it has synchronized to Google the activity is not removed from Google.
14095757: The Report Export Options Excel- Data only option is missing.
14095766: Performing a mail merge to a contact brought into Saleslogix from Outlook causes the error “The Mail Merge Engine encountered an error and cannot continue. The address table query is empty.”
14095767: Using the down arrow to navigate pick lists with a large number of values causes the Web page to move up.
14095777: Export to Excel fails when a group name contains invalid characters.
14095780: SData feed for the activities endpoint is not working correctly for the Saleslogix Mobile and Web clients.
14095810: On an Oracle database, an error is returned when a contact updated in Outlook attempts to synchronize back to Saleslogix.
14095838: In a Windows 7 environment with Internet Explorer 11 and English UK as the default language, the Activities List view displays correctly, but a “404 File or directory not found” displays in a web debugging tool.
14095855: In a Windows 7 environment with Internet Explorer 11 and Es-Es as the default language, the user can log on, but a “404 File or directory not found” displays in a web debugging tool.
14095898: Running an Export to Excel job causes the error “QuartzScheduler_Worker-5] ERROR Quartz.Core.JobRunShell – Job SlxJobService.Sage.SalesLogix.BusinessRules.Jobs.ExportToExcelJob threw an unhandled Exception: Sage.SalesLogix.Client.GroupBuilder.GroupInfoException: There was an error executing a group’s SQL. —> System.OutOfMemoryException”.
14095911: A null reference exception message appears when hosting multiple tenants out of a single database and one of the tenants is deleted.
14095913: Implement Date/Time parameter support for reports.
14095923: When moving a contact, activities and history items are not handle as the selected options indicate.
14095924: When loading reports, some reports cause the error “An InvalidCastException” to display.
14095925: If a group has two columns with the same propertyname filters do not work correctly.
14095963: In a localized environment the Schedule Activity dialog box has two items that do not translate correctly.
14095966: On an Oracle database, the Schedule or Edit an Activity Availability tab causes a 500 error.
14096002: In a German environment there are incorrect translations on the Activities view.
14096004: The SpeedSearch.js file needs localized resource files.
14096018: Using an apostrophe in the Edit Calendar Users look up causes the error “We’re sorry, you’ve encountered an error….HTTP status: Internal Server Error (500).”
14096021: In the Edit Calendar Users lookup window, names that contain an apostrophe display with a “\”.
14096025: On an Oracle database,unable to delete a a lead from the Lead Detail view fails.
14096029: In a Firefox browser, on the Calendar, using the right-click menu to edit an occurrence of recurring activity that does not have a subject causes the date/time, contact, account to be blank.
14096031: Adding users to each other’s teams causes a “Server Request Timed Out” error.
14096090: In a localized environment, when sending a ticket e-mail any extended characters are corrupted in the e-mail message.
14096099: In a German environment the Reports view contains incorrect translations.
14096121: When the Time Zone is set to an option using Daylight Savings timeless activities appear on the Calendar a day late +24 hours.
14096169: Undesirable activity behavior due to Sync trigger changes.
14096170: In a localized environment accessing entities causes the error “The model type: ‘Sage.Platform.Orm.Entities.OrmModel’ was not found.”
14096194: In a localized environment, on the Timeline tabs, “Meeting” is not translated.
14096205: If the trigger description is null it causes an exception in the CrystalReportsJob.
14096215: Running a report with a large number of parameter values causes a Request Size Exception error.
14096232: For localized environments implement new localization .js files.
14096236: Building summary views against entities that have dynamic string properties in Unicode models will throw an exception.
14096323: For localized environments implement new localization resources for OptionsDialog.js.
14096354: Calling CompleteActivity for an invalid activity through the SData Dynamic $service call will throw a NullReferenceException.
14096522: Group layouts should include unique aliases for columns formatted as User, Owner, and PickList Item without requiring the consumer to match the alias naming logic.

We recommend and encourage you to review the update documents to keep abreast of all defects and issues that have been corrected.  Contact Simplesoft Solutions to discuss an upgrade for Saleslogix, and to review any new features or updates with your version of Saleslogix.

If you would like to discuss upgrading your system, or to see a free demonstration, please contact Simplesoft Solutions.

Also, if you would like to learn more tips, or have a CRM topic you would like us to write about, please contact Simplesoft Solutions, Inc.

Remember to check our CALENDAR and register for free training, demo sessions, and the Heartland Saleslogix Users Group Events.

http://www.simplesoft.net/blog/wp-content/uploads/2012/11/SS-Border.png

Dayton/Cincinnati, OHCharleston, WVCharlotte, NC

Comments Off on Saleslogix v8.1.0 Updates Released


 

 

February 25th, 2014 by

The Integrity Checker is a Saleslogix data management tool to help administrators keep their Saleslogix system healthy. This handy utility can help you locate data issues and correct them without being a SQL or database expert.

Integrity Checker is installed with the Administrative Tools for Saleslogix.  The Integrity Checker can be launched two ways from within the Saleslogix Administrator. One way to launch the tool is through toolbar icon in the Administrator (see below) or the second way is by using the menu by accessing Tools | Integrity Checker option.   Both launch points will take you to the same starting point.

Outside of the Administrator, the Integrity Checker can be launched from the executable directly.  See below for the path to the executable.

To run the Integrity Checker:

First step is to login into your server where your Saleslogix Administrator is installed (These steps might vary depending if you are using Saleslogix Cloud, have Saleslogix on premise, or use path variations for Operating System editions).

Note:  The Integrity Checker is not a web-based tool and is NOT launched from the web client.

  • Login to the Administrator as the Admin user
  • Either select Tools | Integrity Checker… from the menu options (or select the toolbar icon)

Or

  • Open Windows Explorer
  • Browse to the Saleslogix folder
  • Double-click the executable to launch the Integrity Checker

C:\Program Files\Saleslogix\SLXDBChecker.exe

  • You will be prompted to login to the application to launch the application.

The basic syntax for running and displaying the results is slightly different for each version of Integrity Checker and Saleslogix.  So, I will provide less “how to” and more strategy for fixing results, once you get them.

Saleslogix has had the integrity tool built in (out-of-the-box) for a very long time. It has continued to improve with each version update, adding improved features and useful tests each time. Overall, it is quite a useful tool for Saleslogix administrators, Saleslogix business partners, and in its efforts to support troubleshooting.

As with any tool or process that can change data in a database, there are a few statements of disclaimer to receive the highest return for your efforts:

1. Ask users to log out to keep changes from impacting them.

2. Perform off hours to keep workers productive during working hours.

3. Back up your Saleslogix database with “Verify” options set.

4. Make sure that processes like the Synchronization Server are not running, if remotes are in use.

These disclaimers are our way of saying to be careful because there is no undo button.

There are two parts to the Integrity Checker.  The first part is the identification of potential issues.  Running the “Tests” will help you identify potential issues with the database.  The second part of the tool is the correction of the test results which are ‘Repair’ options.

Below are some common “questions and answers” related to running the Integrity Checker:

1. Will running tests change the data?  Running Tests does not change records in your database until the Repairs are selected and ran.

2. If I ran the Integrity Checker and I get test results with counts for bad records, how do I clean the records up? Which types of test results should be repaired vs. analyzed?  How often should I run the Integrity Checker?

Basic Integrity Checker Strategy:

I. Look for non-zero results.

Results that come back with 1 or more issues should be reviewed.  Ideally the Integrity Checker should come back with a list and everything has a zero count on the issues.

II. Save the results to a file for review.

Make sure that you include the checkbox to save the results to a file for review.  Note: When you update the options from ‘Test” to ‘Repair’ change, try to make sure that you change the name of the file so that the original file is not overridden.

III. Repair the “no Brainer” items first.

  • When there are results with the Integrity Checker, there are several types of “clean up” actions to consider:  Delete, Set, Clear, Create, Uppercase, Insert Fix, etc.
  • Most of the repairs should be made without much regard to the repair task.  I will repair the following in almost all instances:  Create, Uppercase, Insert, Fix

IV. Ask where you need assistance.

Note: Some Repairs should be reviewed and ran by someone who knows the data or is willing to make a decision about the data.  The test repairs that cause me to pause and review further are:

  • Delete, Set, Clear
  • In the case corrective action is needed to take place instead of deleting records
  • In the case blanking out records which might cause hardship with user and their ability to work.  I try to ask the user about the records first.

Contact us here at Simplesoft if you run into something that you are not sure how to repair.

V. Run the Integrity Checker monthly.

  • The basic recommended timing for running the Integrity Checker is monthly.  My recommendation is for the administrator to have a monthly scheduled task to run the Integrity Checker and then cleanup any unexpected results.
  • Note: For troubleshooting, whenever the need arises, run the Integrity Checker for an Ad Hoc analysis of potential data related issues.

Final Recommendation: Run the Integrity Checker once a month to get the most benefit from the integrity features built into Saleslogix.  It is best to run the Integrity Checker off hours rather than potentially have down time during the user operational hours, but scheduling will largely depend on the administrator’s preference. The most important part is to take the corrective repair actions in keeping your Saleslogix system and data running fully operational.

“You shouldn’t presume that all quotes that are in a magazine or a newspaper are accurate.”–Andrew Card

If you would like to discuss upgrading your system, or to see a free demonstration, please contact Simplesoft Solutions.

Also, if you would like to learn more tips, or have a CRM topic you would like us to write about, please contact Simplesoft Solutions, Inc.

Remember to check our CALENDAR and register for free training, demo sessions, and the Heartland Saleslogix Users Group Events.

http://www.simplesoft.net/blog/wp-content/uploads/2012/11/SS-Border.png

Dayton/Cincinnati, OH | Charleston, WVCharlotte, NC

Comments Off on How to Get the Most Out of Saleslogix Integrity Checker


 

 

February 19th, 2014 by

Have you performed your system checks recently?

As Saleslogix system administrators, you need to mind the system checks and keep the shop tidy.  Two things come to mind right away as higher priority checks.   The only way to know your systems are running correctly for sure is to take the time to review the logs and confirm the results.

Reminder #1 – Confirm your database and system backups

First, if you are on premise you need to tend to the presumed confirmations that your database backups are being successfully performed – according to your maintenance plans.  Note: If you have a Saleslogix cloud deployment, this database step is being performed on your behalf.

Reminder #2 – Run your Saleslogix Integrity Checker

Secondly, in Saleslogix there is a built in tool that allows a Saleslogix administrator to review the health of their Saleslogix platform.  The handy utility is called the Integrity Checker and is an out-of-the-box application to check the database integrity and confirm the status of the Saleslogix data.

For the administrator, there are many things to think about to keep your systems running in top shape.  Here are a couple of easy tasks to put on a recurring reminder and check as needed.  Remember that your business data is the lifeblood of your company.  Call us for additional training or support assistance.

“An intelligent person armed with a checklist is no substitute for experience.”Joy Gumz

If you would like to discuss upgrading your system, or to see a free demonstration, please contact Simplesoft Solutions.

Also, if you would like to learn more tips, or have a CRM topic you would like us to write about, please contact Simplesoft Solutions, Inc.

Remember to check our CALENDAR and register for free training, demo sessions, and the Heartland Saleslogix Users Group Events.

http://www.simplesoft.net/blog/wp-content/uploads/2012/11/SS-Border.png

Dayton/Cincinnati, OH | Charleston, WVCharlotte, NC

Comments Off on Top 2 Simple Tasks to Manage Your Saleslogix Data


 

 

 


scroll up

Hit Counter by technology news