Archive for April, 2011

Configure and Troubleshoot SData™

Posted by Kristin Lisson on April 29, 2011
Administrator, Blog, Developer / No Comments

Sage Data (SData) provides a simple standard protocol for reading data from and writing data to Sage Business Applications. It enables desktop, server, and Web-based applications to communicate with each other, and also with third-party applications and the world wide web. To find out more about SData™, visit http://sdata.sage.com.


Let’s configure SData™ for Sage SalesLogix!

Before you can use SData™ in your Sage SalesLogix customization projects, you need to ensure your environment is configured appropriately. Here are a few steps you should take:

1. Map the Sage SalesLogix admin user to your Windows WebDLL user*:

Learn more about the WebDLL user in this excerpt from the Sage SalesLogix Implementation Guide.

  1. Log on to the SalesLogix Administrator as admin.
  2. From the list of users, double-click the Administrator user.
  3. Select the Use Windows Authentication check box, and then map your WebDLL user on your server inside the Windows ID box. If prompted to import information from Active Directory, say no. (Although it shouldn’t matter for the WebDLL user.)


    WebDLL User Mapping
  4. Click OK.


2. Deploy the SData portal:

  1. Log on to the SalesLogix Application Architect as admin.
  2. From the Deployment Explorer, expand the Deployments node, and then double-click Core Portals.
  3. From the list of Deployment Targets, right-click the sdata node, and then click Deploy Portal.
  4. Close Application Architect.


3. Enable basic authentication:

This step is not necessary anymore (since v7.5.3 HF3) because basic authentication is enabled by default. As long as SData is accessed via https, basic authentication provides you with the security you need. Read more about SData and basic authentication/digest authentication from a previous post.


4. Disable Windows Authentication in IIS:

  1. Within IIS, right-click the sdata node, and then click Properties. The SData Properties window appears.
  2. Click the Directory Security tab.
  3. Next to the Authentication and access control option, click Edit. The Authentication Methods window appears.
  4. Clear the Integrated Windows authentication check box, and then click OK.
  5. Click OK to close the Properties window.


5. Configure handler mapping:

  1. Within IIS, right-click the sdata node, and then click Properties. The SData Properties window appears.
  2. From the Virtual Directory tab, click the Configuration button.
  3. From the list of application extensions, click the ascx extension, and then click Edit.
  4. Right-click in the Executable box, and then click Copy.
  5. Click Cancel to return to the Application Configuration window.
  6. Click Insert.
  7. Right-click in the Executable box, and then click Paste.
  8. Clear the Verify that file exists check box.
  9. Click OK, and then click OK again.
  10. Close and restart IIS.


Now let’s check to see if it’s working!

  1. Open Internet Explorer. (You can use any browser, but the feed is easier to read in IE.)
  2. Browse to http://[yourservername]:3333/sdata/$system/adapters.
  3. A log on prompt should appear. Make sure the dialog says “The server [yourservername] at SalesLogix Client requires a username and password.” If it is blank or says something else, something isn’t right.

  4. Enter any SalesLogix username and password, and then click OK.

    SData Logon
  5. You should now see your SalesLogix SData feed. Click on some of the links to see what kind of data is returned. For example, http://[yourservername]:3333/sdata/slx/dynamic/-accounts. You should see a list of all your SalesLogix accounts.

    SData Feed


Uh oh. It’s not working

If your SData feed did not appear, recheck your steps. The error message that you receive from your browser can tell you a lot. Check out this flow chart to see if your error matches any of these.

Troubleshoot SData

Another option is to visit the Sage SalesLogix community. Chances are, someone has already posted a question that relates to the same issue you might be having. If not, you can post your own and get answers from other Sage SalesLogix experts.

Also check out the Sage SalesLogix Customer Resource Center for links and other contact information for the Sage SalesLogix Support team.


*As of 7.5.3 HF3, when using Basic Authentication, you no longer need to configure the WebDLL user with ADMIN User.


Tags: , , , , , , ,

Sage SalesLogix Desktop Integration for Web v7.5.3

Posted by Kristin Lisson on April 25, 2011
Blog, End User / No Comments
Sage SalesLogix Log On Screen

Log On Screen

Odds are, most of you have accessed the v7.5.3 Web Client log on screen, entered a user name and password, and continued on your merry way. But did you notice the “Enhance SalesLogix” button? Perhaps your inner skeptic told you to ignore it? Or maybe you even clicked the button and downloaded the installer. Then after making it through the installation wizard, you were left with that “Now what?” feeling. Well, I’m here to tell you “Here’s what!” about Sage SalesLogix Desktop Integration.




Installing Desktop Integration

Installation Wizard

When you click the “Enhance SalesLogix” button, your browser starts to download a small executable file called SlxDesktopIntegrationSetup.exe. This file gets saved somewhere on your computer, the process of which depends on the browser you use. Internet Explorer, for example, prompts you for the file destination (default is My Documents). Firefox and Chrome, on the other hand, will most likely download the file automatically, and the default file destination is My Documents\Downloads. Either way, to begin Desktop Integration installation, you must close your browser after downloading the file. Then run the file (double-click), and follow the onscreen prompts in the installation wizard (see right). This process should take less than a minute. When installation is finished, launch your browser again. This time on the Log On screen, the message below the “Enhance SalesLogix” button should say, “Enhancements have been installed.”


What Changed?

After installing Desktop Integration, you’ll note a few differences when you log on to Sage SalesLogix Web:

1. Write Menu: You now have access to mail merge features (letters, e-mails, templates). Without Desktop Integration, the Write menu is hidden from view.
Write Menu


2. Drag-and-Drop Support: You can now drag files from your desktop or Windows Explorer into the Attachments tabs on a main view.
Drag-and-Drop


3. E-mail Integration with Microsoft Outlook: This is the big one, folks—at least if e-mail is as important to your work-flow as it is to mine. With e-mail integration, you can use the Send SLX button, attach files to an e-mail message using the SalesLogix library, and drag-and-drop e-mails to SalesLogix history. Because this feature comes with a little bit more gusto than the others, let’s explore it in its own section below.
\Outlook Integration Features


E-mail Integration (More Details)

Desktop Manager

Desktop Manager Icon

If you want to use E-mail Integration, the first thing you should do is configure the Sage SalesLogix Desktop Manager. (The what?!) Don’t worry, this application is just a simple dialog that captures your SalesLogix database connection and history options. Open the Desktop Manager by double-clicking the icon in your Windows System Tray. If you can’t find the icon, you can also launch the Desktop Manager from C:\Documents and Settings\[Windows Username]\Local Settings\Application Deta\Sage\SlxDesktopManager.exe.

The Database Information options should default for you. Click the “Test” button to ensure you receive a “Connection was successful message.” If not, verify that the Portal URL shows exactly what you have as your Sage SalesLogix Log On screen URL, omitting “/SlxClient” and everything after it. If you continue to have connection errors, please contact your system administrator.

Desktop Manager

Desktop Manager

The History Options apply to the Send SLX button for sending e-mail. The Send SLX button records the message to SalesLogix history, so you can decide how and when SalesLogix prompts you for confirmation:

  • Prompt for Duplicate Contacts – Prompt before sending the message if SalesLogix finds a duplicate contact (i.e. with the same e-mail address) as the one you entered in the To/CC/BCC fields.
  • Prompt for Contacts - Prompt before sending the message for any contact that you add to the To/CC/BCC fields.
  • Prompt for Unresolved Contacts - Prompt before sending the message if SalesLogix cannot find the contact in the database that matches the one you entered in the To/CC/BCC fields.
  • Display History Details before saving - Show the SalesLogix Complete Activity screen to show/modify history details before saving it to the History tab for the selected contact.




Now that you have a taste of you’re missing without Desktop Integration, check out the complete Sage SalesLogix Desktop Integration video that’s available in the Demo version of the Sage SalesLogix End User’s Subscription. For more videos like these—including using Intellisync to synchronize your Sage SalesLogix contacts with Microsoft outlook—purchase the full version of the End User’s Subscription at Sage University. Contact training.crm@sage.com if you have questions.

Tags: , , , , , , , ,