|
Company -> Blog...
October 9th, 2014 by Paul
Autumn (fall) is a wonderful time of year (my favorite!). I love the crisp cool air and foliage changes. It is a time of year that you are straightening up the yard, raking and pulling weeds, and putting away summertime outdoor furniture – generally preparing for the next season. With the seasonal change, I was thinking it is also a good time to be cleaning up systems and data related tasks for the next round of technology changes with Infor CRM. It’s a great time to think about cleaning up your Saleslogix system and data.
1. A faster system means less waiting for end users and more productive end users. 2. A tuned system means users can help your business serve your customers. 3. Cleaner data means that end users will have more meaningful insights in dashboards, reports, and groups. 4) Clean data increases trust and helps with a positive sales culture avoiding a bad reputation with data inaccuracies. Do you want?
Dirty data can negatively impact alerts, Dashboards, entity groups and many other aspects of your systems like integration between systems. It can impact marketing to the incorrect customers in the incorrect manner (bad reputation) or even impact forecasting sales. Data is a precious thing and will last longer than the systems themselves. — Tim Berners-Lee Attend our Fall Data Cleanup Webinar on Tuesday, October 21st at 2:00 pm to learn more. You can also contact us to learn more about our data cleansing services. If you would like to discuss upgrading your system, or to see a free demonstration, please contact Simplesoft Solutions. Remember to check our CALENDAR and register for free training, demo sessions, and the Heartland Saleslogix Users Group Events.
Comments Off on Fall Data Cleanup with Your Favorite Saleslogix Consultants
September 25th, 2014 by Paul
This article is written to help Saleslogix customers to take corrective actions for a known data related issue that applies to the web client only upon Opportunity creation. We have found the issue is not consistent from one implementation to another, but wanted to make this available for immediate impact. When you are planning to move from a v7.5.x Saleslogix to v8.x/v8.1.x, here is a set of proactive steps to ensure one less issue for the users of Saleslogix. Our goal is to always maximize the experience of the end user. Note: This correction helps to avoid an error message while inserting opportunities. The error message description encountered would be like below: We’re sorry, your request could not be completed. When you receive an error in the browser like the one above it is always a good idea to find the matching Windows Event viewer entry for the more complete information on the issue. Once the issue is determined to be the Account Partner Picklist issue then follow the steps below for the potential issue resolution. 1. How to find the records that may need updated. In SQL Server Enterprise Manager, on the Tools menu, click SQL Query Analyzer to run SQL Query Analyzer connected to the Saleslogix database. Note: The SQL can be ran in the Execute SQL in the Administrator as well. 2. Run the following select statement to identify the potential records for correction. select * from sysdba.picklist where text = ‘Account Partner’ Note: If more than one row is returned from the above query, remove the extra listings through Pick list Manager and rerun the previous query. You may need to drop the table owner reference, sysdba.picklist vs. picklist, depending on how the statement is being ran. 3. If duplicate records exist, then open the Saleslogix administrator and go to Manage | Pick lists and remove any duplicate pick lists. Note: If the result set has the itemid as ‘kSYST0000346’, there is nothing more to do. If the Itemid is another value then, save the current itemid value and run the following SQL statements. Maybe copy to a notepad file or similar tool. 4. Run the following update statements, be sure to replace Itemid and PicklistID with the saved ItemID value. update sysdba.Picklist set ItemId = ‘kSYST0000346’ where ItemId = ‘<Retained ItemID>’ update sysdba.Picklist set PicklistId = ‘kSYST0000346’ where PicklistId = ‘<Retained ItemID>’ 5. Verify the results of the changes, by running the SQL statements below. select * from sysdba.picklist where text = ‘kSYST0000346’ select * from sysdba.picklist where PicklistID = ‘kSYST0000346’ Note: The first query should return 1 row, and the second query should return all the values/items from your Account Partner pick list. 6. Validate in the web client that the insert opportunity feature does not produce an error. Ask the user who initially ran into the issue to confirm the problem or business analyst as needed. 7. Communicate the results Let people know the problem was corrected. In the unlikely case the problem persists, contact your Saleslogix implementation partner or Saleslogix support if you have an active business care plan. When you take the time to proactively check and ensure that your end users will not hit data issues it is like fixing a leaky faucet – ultimately it will help you save energy, water, and money. For IT, you are adding value to your environment and helping your systems to run smoothly. The key is to work with a Saleslogix business partner who has the insight and experience to help provide answers and solve problems. I like to encourage people to realize that any action is a good action if it’s proactive and there is positive intent behind it. — Quote by Michael J. Fox For more Saleslogix tips and tricks, stay tuned to our blog! If you would like to discuss upgrading your system, or to see a free demonstration, please contact Simplesoft Solutions. Remember to check our CALENDAR and register for free training, demo sessions, and the Heartland Saleslogix Users Group Events.
Comments Off on Proactive Data Corrections for Inserting Opportunities
January 31st, 2014 by Paul
Many Saleslogix power users are aware of using Boolean logic (AND / OR) to find data records in applications. Technical Note: If you have a long list of OR’s, it is more efficient to use the IN command with groups. Act! and Saleslogix both support advanced queries and advanced finds for locating results. Additionally, there are some fancy, yet easy, ways to search for data records, and which help narrow or broaden the search results, and result in finding the records you are looking for without the advanced features. Here are a couple of sample defintions of the “wild” characters when performing a look-up or find:
For right now, let’s keep it simple and I will leave out the fancy ‘escape’ methods for searching for 100% and other odd database characters. When you are searching applications, you can sometimes take advantage of the database SQL functionality and use wildcards for a fancier, and many times easier, method for finding what you want. Wild Search Examples:
With newer versions of Act! using Universal search, and Saleslogix using SpeedSearch, or even filters in Saleslogix web, these wildcard search tools are trumped by technology advances and are not needed as much.Wildcards are nice to have in your back pocket for such an occasion to quickly find records. “Searching is half the fun: life is much more manageable when thought of as a scavenger hunt as opposed to a surprise party.” 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.
Comments Off on Gone Wild with Searches In Act and Saleslogix
September 18th, 2013 by Paul
I’m pleased to republish portions of an article by Don Farber, Vice President of Sales & Marketing of Vineyardsoft. Thank you Don for your permission to adjust it for CRM and share this: Do you know when your Customer Relationship Management (CRM) data is trying to tell you something important, such as:
Enabling your CRM data to speak to you – instead of you going to it – enables you to become a more “data-driven” organization and be more responsive to the needs of your staff and customers. Giving your CRM data a voice starts with identifying what you want your CRM data to tell you. For example, you might not need your data to alert you when an opportunity’s forecast close date is coming, but you might want it to tell you if that opportunity becomes overdue for closing. There are eight conditions under which your data should speak to you: 1) Date-sensitive conditions. E.g., leases or support contracts about to expire. 2) Approaching thresholds. E.g., support reps with too many calls assigned to them. 3) Exceptions to normal processing. E.g., orders below a certain total with discounts exceeding a certain percentage. 4) Things that have not happened – but should have. E.g., a repeat customer who has not purchased within the last 30 days. 5) Data Integrity. E.g., checking to see if phone numbers have the correct number of digits, or that a requested discount has received the needed approval. 6) Trend Analysis. E.g., an account manager whose sales numbers have increased or decreased by ‘x’ percent over a certain time period. 7) Data Inconsistencies. E.g., a project that is less than 50% complete but has used up more than 50% of its budget. 8) Data Changes. E.g., changes to a client’s credit limit or credit rating. Once you identify such conditions, you’ll require a technology that gives a voice to your CRM data, and one such technology is Business Activity Monitoring (BAM). BAM solutions monitor your CRM data for important conditions and then trigger one or more automated responses. In this way your data is the initiator of intelligent actions across your organization. BAM is a unique combination of four underlying technologies. First is a Business Intelligence (BI) component. BAM is very sophisticated in terms of the types of conditions it monitors within an underlying CRM application. And, unlike traditional BI solutions, BAM monitors in an automated manner; it automatically scans your data for the information that your organization is interested in. Once a BAM solution identifies the conditions that you’re interested in, the second component — Alerts – takes over. Typically, alerts are delivered via a wide variety of devices, including instant message, email, fax, mobile device (e.g., cell phone), dashboard, Twitter™ and so on. The third BAM component is Reporting – and is an extension of alerts. In some cases, alert data may be no more than a short text message sent to your cell phone; in other cases, it may be an analytical report (e.g., “Forecast Sales Report”), a customer lease, or even hazmat item warnings. And finally there is the Workflow component of BAM. This technology enables a data-driven environment in which the CRM data itself not only initiates an awareness within an organization’s staff, but goes even further to actually act on that CRM data. For example, a BAM solution that detects that a sales opportunity has not been followed-up on could not only send an alert to the sales rep who owns that account, but could also schedule an activity (such as a phone call) for the sales rep to make the next day to that prospect. How has your company’s business processes evolved to give a “voice” to your CRM data? A moment’s insight is sometimes worth a life’s experience.
Remember to check our CALENDAR and register for free training, demo sessions, and the Heartland SalesLogix Users Group Events. Comments Off on What Does Your Saleslogix CRM Data Say?
March 29th, 2011 by Paul
How to identify your SQL Server version and edition http://support.microsoft.com/kb/321185 2. Find the webpage with the corresponding Microsoft SQL Server Feature Pack link MS SQL Server 2005 Links MS SQL Server 2005 SP3 Feature Pack Link – 9.00.4035 MS SQL Server 2005 SP2 Feature Pack Link – 9.00.3042 MS SQL Server 2005 SP1 Feature Pack Link – 9.00.1399 MS SQL Server 2008 Links Microsoft SQL Server 2008 Feature Pack – 10.00.1600.60 Microsoft® SQL Server® 2008 R2 Feature Pack – 10.50.1600.1 Microsoft® SQL Server® 2008 R2 SP1 Feature Pack – 10.50.2500 http://www.microsoft.com/download/en/details.aspx?id=26728 Microsoft® SQL Server® 2008 R2 SP2 Feature Pack – 10.50.4000.0 http://www.microsoft.com/en-us/download/details.aspx?id=30440 MS SQL Server 2012 Links Microsoft® SQL Server® 2012 Feature Pack – 11.00.2100.60 http://www.microsoft.com/en-us/download/details.aspx?id=29065 Microsoft® SQL Server® 2012 Service Pack 1 Feature Pack – 11.00.3000.00 http://www.microsoft.com/en-us/download/details.aspx?id=35580 Microsoft® SQL Server® 2012 Service Pack 2 Feature Pack – 11.0.5058.0 http://www.microsoft.com/en-us/download/details.aspx?id=43339 MS SQL Server 2014 Links Microsoft® SQL Server® 2014 Service Pack 1 Feature Pack – 12.0.4100.1 https://www.microsoft.com/en-us/download/details.aspx?id=46696 3. Once the right page is found, you will need to scroll down the page to find the Microsoft SQL Server 2008 Native Client files. Download the appropriate installation files for the bit edition of the client workstations (32 bit vs. 64 bit etc.) The download file will be named (sqlncli.msi) for 32 bit or (sqlncli_x64.msi) for 64 bit edition. 4. Lastly, copy the file(s) to a shared installation point on the network. A good tip is to place them in a well named folder and copy the link of the download URL as well. I tend to create folder like ‘MS SQL SQL native client – 64 bit for MS SQL 2008 SP1’ so that when I come back to the folder later I will know what the folder means. 5. If you find that your version of MS SQL Server is not patched up, then you can take the time to plan to patch to the latest server pack that is on the compatibility list. When you do that, make sure that you review your backup plans and patch the client computer and other server computers that have client connectivity back to the server. How to obtain the latest service pack for SQL Server 2008 http://support.microsoft.com/kb/968382 How to obtain the latest service pack for SQL Server 2012 http://support.microsoft.com/kb/2755533 This little article will help you find the links that you need to keep your installations updated and SalesLogix running smoothly. Upon the subject of education, not presuming to dictate any plan or system respecting it, I can only say that I view it as the most important subject which we as a people may be engaged in. That everyone may receive at least a moderate education appears to be an objective of vital importance. Abraham Lincoln (1809 – 1865) 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. in one of our Cincinnati/Dayton (OH), Charleston (WV), or Charlotte (NC) surrounding area office locations: Dayton, Ohio Office: Ripley, WV Office: Charlotte, NC Office: Comments Off on Using MS SQL for SalesLogix? A Collection of Helpful Links to Feature Pack Articles
February 28th, 2011 by Janetta
Spring is a great time to involve all your users in help cleaning up Sage SalesLogix. Let’s consider some basic cleaning tasks by major entity: Accounts – Some key fields at the Account entity are Type, Subtype, Industry, and Status. Clean up your pick lists for each, lock down the pick lists for each, and create some administrative groups to push out to your users where these fields are blank. Be very specific about what fields are to be completed, the name of the Account Group, and give them a target date for completion. Along with the key fields above, you should also encourage general address, phone number, and web address information be completed and updated. Create some positive press on the project by sending out emails with updates on who has completed the tasks and/or what % of the tasks has been completed. Ex. 75% of our Accounts are complete! Contacts – The key fields for Contacts are Status and email. Again, create the groups with missing information and set a timeline for completion. Opportunities – The key fields for updating Opportunities are Status, Close Date, Probability, and Opportunity Value (which is done by making sure the products and pricing are current). If you are serious about using SalesLogix for forecasting these fields must be kept up to date and your users should be conditioned to update these fields on a regular basis. Activities – Encourage users to update their scheduled Activities that are way out of date range. You could create groups for Activities 90 days old, 6 months old, and 12 months old then suggest they reconnect with these Prospects, etc. When making a fire people like to join you, when cleaning the ashes you are often alone” African Proverb Interested in more on this topic? – join us for the next Heartland SalesLogix Users Group 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. in one of our Cincinnati/Dayton (OH), Charleston (WV), or Charlotte (NC) surrounding area office locations: Dayton, Ohio Office: Ripley, WV Office: Charlotte, NC Office: Comments Off on SalesLogix Spring Cleaning – End User Tasks
January 17th, 2011 by Paul
An Administrator writes: Dear Paul, Are there any issues with giving a SalesLogix user the ability to delete ‘Contacts’ in the LAN client? Answer: There are two philosophies on how to do this. The first is to create a policy and to keep the permissions as an Administration function or secondly to just provide the user with the capability. There are pros and cons to both. What I mean by policy is to add an item to the contact/account status pick list with a value of ‘Delete’. Next, have the user provide a note explaining the reason on why it needs to be deleted or archived to team that only the admin user can access. Then the Administrator can review a group based on the status field of delete on a periodic basis and take appropriate action. Creates work on your part, but pretty easy. If you provide the user the ability to delete contact, account, etc. (Administrator | user profile | Security tab and feature security tab to adjust the delete item menu access) then you will not have to monitor the group or take action. But if the user deletes an account or contact by accident that is very important then you will need to restore a copy of the database with a new name. Then use a tool called ‘Group Copy’ to bring the data back into the production database. This takes time also and is a reactive way to manage your system. I tend to prefer the first option of creating an admin policy. It creates more maintenance work for me but is proactive data management. It prevents headaches from data loss and working in emergency mode (reactive). 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. in one of our Cincinnati/Dayton (OH), Charleston (WV), or Charlotte (NC) surrounding area office locations: Dayton, Ohio Office: Ripley, WV Office: Charlotte, NC Office: Comments Off on Dear Paul, should we give SalesLogix users the ability to delete?
January 11th, 2011 by Paul
A few database thoughts for Sage SalesLogix installation considerations and planning I had a dream last night that I was running queries in a database. I ran the following query: SELECT * FROM [paul].[thoughts] The result was no records found. 😉 Who knew? I wanted to write an article that might provide assistance with installation and planning for SalesLogix with MS SQL Server with a focus on MS SQL Server 2008 considerations in particular. My intention is this: To help the average IT Administrator plan for a Sage SalesLogix deployment of less than fifty (50) user seat client side installation for an on-premise solution and answer some common questions. 
1. Database Qualifications with SalesLogix SalesLogix v7.5 works with both MS SQL Server and Oracle. With Oracle, that is Oracle 11g or Oracle 10g R2. With MS SQL Server, there are two versions available for compatibility: MS SQL Server 2005 and MS SQL Server 2008. MS SQL Server 2008 came into compatibility with SalesLogix v7.5 SP2 but worked just fine before that qualification announcement. Disclaimer: Please refer to the Sage SalesLogix system requirements for the exact and current details, like the SalesLogix Service Packs, etc., because future releases from both Sage and Microsoft make these items a fast moving target. 2. MS SQL Server installation with SalesLogix I get asked about how to install MS SQL Server for SalesLogix with some regularity. The frequent requests are especially understandable for the server-side installation tasks as they are not documented well because of the nature of the rapid changes by both Microsoft and Sage. Many times a client is doing the planning far in advance of having the software media in hand as well. Here is my answer for the bare minimum installation: When MS SQL Server is installed there are a few services that can be installed, like Database Services, Analysis Services, Reporting Services, Notification Services, Integration Services, Client Components and Documentation & Sample Data. Most of them are not needed unless they are being shared with other applications or other factors like advanced requirements. Here is what is recommended for SalesLogix to run properly:
3. Server Configuration Tips For sizing the RAM for the data load, I am going to assume that we are dealing with a single application database and a single purpose server for the database services functionality. This is not always true, esp. in today’s “do more with less” IT world. But let us begin with this ideal, as adjustments can be made according to the particular needs of a given situation. A good minimum would be 3 Gb of RAM; for Windows 2003 Server that is 32 bit. If you are running Windows 2008, consider more, especially if 64 bit. I also recommend one Gb for each Gb of database size; in other words, if the database has 4 Gb of data and you have 50 users. You will want to consider having 7 Gb of RAM as a good starting point for responsiveness. For configuring SalesLogix Connection Manager with MS SQL Server 2008, there is a tweak that is needed for the Connection settings:
This should correct the issue for the client connections with the connection resetting to blank password. Confirm by logging in to a SalesLogix application. The matching SQL Native client tool will need to be installed on each additional server that has components that will be connecting and opening the SalesLogix database. 4. Client Installation tips for SQL Native Client Components. Always make sure that the SQL Native client tool for the network users matches the server edition (2005, 2008, etc.) and database service pack. Let’s assume that you have MS SQL Server 2008 SP1 (10.00.2531.00). You will want to locate and download the matching SQL Native client for the client workstations.
Note: The MS SQL Native client doesn’t need to be downloaded for disconnected remote users. The MS SQL Express will install the SQL Native Client Components. The installation step for the SQL Native Client can be performed on the client network workstations independent of the Sage SalesLogix application. Installing this program will save time on the client network workstation for a deployment for upgrade. Hopefully this article answers some common questions for planning out MS SQL Server installation tasks for an on-premise deployment related to the database. “I have traveled the length and breadth of this country and talked with the best people, and I can assure you that data processing is a fad that won’t last out the year.” –The editor in charge of business books for Prentice Hall, 1957 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. in one of our Cincinnati/Dayton (OH), Charleston (WV), or Charlotte (NC) surrounding area office locations: Dayton, Ohio Office: Ripley, WV Office: Charlotte, NC Office: Comments Off on SalesLogix Database Planning Considerations
September 22nd, 2010 by Jim
As a SalesLogix Administrator, have you ever had a user come up to you and say…. “I accidentally deleted one of my Accounts.”? I am sure this has happened to most of you at one point in your SalesLogix career. When this happens, you have a couple of options. You can go back and restore a copy of your database from the most recent backup, but how do you just get the deleted account and not have to restore the full database? SalesLogix offers you a little known, but very powerful tool to allow you to recover just the missing Account and any record related to the Account like Contacts, Opportunities, History items, Activities, etc…. It is called GroupCopy. As the name implies, it copies a group of records from one database to another. It is also Sync aware, which means that the record will get sent to all of your remote users without you having to do any additional work. So, if you have the deleted Account in another database, all is not lost. There is a bit of work that needs to happen before you begin your restoration project. You will need to restore the backup of your database to a new/separate database than your PRODUCTION database, very similar to creating a TEST database environment, the only real difference is this copy is only temporary until you get the deleted record restored. Once the database is restored, you will need to create an entry in Connection Manager for the database and a DataLink connection for the database in SalesLogix Client application. You will also need to create a group in the SalesLogix Client that contains the record you want to restore. This group can be restricted to only include a single record or expanded to include a selection of records that you choose. For naming the group, make it something that you will easily remember like ‘Account Fix List’, ‘Fix Listing’, or something similar. That is all the prework that you need to do. Located in the SalesLogix installation folder under Program Files is an executable called ‘GroupCopy.exe’. When you run this executable, you are initially prompted to enter connectivity information to the Target database.
This is the database where you want your restored record to end up. The next dialog box you are presented with allows you to select the Source database to connect to.
This is the database where the deleted record resides. The next dialog box that displays, on the first tab, allows you to select the User that you created the group under and the group name itself, along with how often to commit records to the database and whether or not to show the details as the process is running.
The second tab allows you to set any conflict resolution that may need to occur.
The default settings for the information contained on this tab are usually sufficient. Once you have your settings on both tabs correct, you are ready to Test the copy. Clicking the ‘Test’ button runs the copy, running the necessary steps to copy the deleted record from the Source database to the Target database, and then rolling back the transactions. After you have tested the copy, click the ‘Go’ button to run the actual copy job. The end result will be your record that was deleted being restored to your PRODUCTION database. As with everything, there are always a few caveats. The first is you will lose any changes/updates that were performed by anyone to this record you are restoring after the last database backup was taken. The next is that some of the record creation dates come over as the date the Group Copy was ran and not the actual creation date of the record (this is typically a minor issue and only happens in very isolated situations on stand-alone tables). In conclusion, Group Copy is a very powerful tool that has a specific application in the SalesLogix world. It has proven to be a lifesaver at our clients when the words …. “I accidently deleted one of my Accounts.” is spoken by a user. 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. in one of our Cincinnati/Dayton (OH), Charleston (WV), or Charlotte (NC) surrounding area office locations: Dayton, Ohio Office: Ripley, WV Office: Charlotte, NC Office: Comments Off on SalesLogix Group Copy is your friend
July 13th, 2010 by Janetta
You know how in life you run into those small things where you wished you had slowed down to make a better decision… Like where to place the butter tub in the refrigerator, so it doesn’t fall out and bust all over the kitchen floor. I can only hope this is resonating with some of you and you aren’t all the type who very strategically place your grocery items in their assigned quadrants in the fridge. I work with some of you quadrant folks, but many of you will understand my perspective. I know from experience there are plenty of you who have painstakingly planned, with your user departments, the best “pick lists” possible for all areas of SalesLogix. Now, you wonder “how did that data get in there?” You forgot one very important step; way back in the beginning. You forgot to lock down the pick list so the users could not add their own values. Maybe you didn’t know it was possible, maybe you thought by giving them so many choices they wouldn’t add their own, or maybe you thought it would be nice to provide your users that flexibility. Whatever the reason … I bet most of you are second guessing your decision now. I was working with a client in the Cincinnati, OH area last week, training them on building query groups in SalesLogix, and they were shocked at some of the values in their data. We are talking about two tiny little checkboxes. These two checkboxes will save you hours of frustration. See below! You need both ‘Text must match a list item” and “Users can not edit items” to fully lock down pick lists. The Picklist Manager can be found in the Administrative Client under Manage>Pick Lists:
Note: The default setting for pick lists does allow users to Add items of their own (unchecked). OK, so now you know to go back and lock down the pick lists, but what about all that data you don’t want in your pick lists? I have a good answer for you and another area of SalesLogix to explore in this article. There is a SalesLogix maintenance tool called “Replace Data” that can help get your data back under control. This menu is available through the Sales Client, as an administrative user, from the Tools>Manage>Replace Data menu option. Use the Replace Data Wizard to replace one or more values with another value in the ACCOUNT, CONTACT, or OPPORTUNITY tables. You can only replace data in accounts, contacts, and opportunities to which you have access rights. The Replace Data Wizard works with the current account, contact, or opportunity group.
The first screen of the replace data wizard prompts you to choose which type of records to update (Account, Contact or Opportunity).
The next decision is the type of data replacement to perform on the current group
The last screen prompts for a target field and value. If you have chosen a replacement type that requires more input values (search and replace, for example) this is where you will be prompted for those as well. *Simplesoft Solutions recommends that all of the actions described in this post be performed by and limited to Administrative SLX Users. If your SalesLogix data cleansing job is bigger than you can handle, contact us a sales@simplesoft.net to discuss the data cleansing services we provide at Simplesoft Solutions, Inc. Dayton, Ohio Office: Comments Off on A small decision can save you a million headaches in life and SalesLogix!
|
SEARCH BLOGS
RECENT BLOG POSTS
ARCHIVES
TOPICS
- Spreading the News (211)
- Managing Common Administrative Tasks (38)
- Enhancing Deployment (35)
- Reviewing Tips and Tricks (35)
- Improving Skills and Usage (30)
- Saleslogix updates (26)
- Exploring CRM Strategy (24)
- Optimizing Configuration (17)
- Infor CRM What's New (17)
- Infor CRM update (14)
- Refining Data Management (12)
