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.
- Log on to the SalesLogix Administrator as admin.
- From the list of users, double-click the Administrator user.
- 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.)
- Click OK.
2. Deploy the SData portal:
- Log on to the SalesLogix Application Architect as admin.
- From the Deployment Explorer, expand the Deployments node, and then double-click Core Portals.
- From the list of Deployment Targets, right-click the sdata node, and then click Deploy Portal.
- 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:
- Within IIS, right-click the sdata node, and then click Properties. The SData Properties window appears.
- Click the Directory Security tab.
- Next to the Authentication and access control option, click Edit. The Authentication Methods window appears.
- Clear the Integrated Windows authentication check box, and then click OK.
- Click OK to close the Properties window.
5. Configure handler mapping:
- Within IIS, right-click the sdata node, and then click Properties. The SData Properties window appears.
- From the Virtual Directory tab, click the Configuration button.
- From the list of application extensions, click the ascx extension, and then click Edit.
- Right-click in the Executable box, and then click Copy.
- Click Cancel to return to the Application Configuration window.
- Click Insert.
- Right-click in the Executable box, and then click Paste.
- Clear the Verify that file exists check box.
- Click OK, and then click OK again.
- Close and restart IIS.
Now let’s check to see if it’s working!
- Open Internet Explorer. (You can use any browser, but the feed is easier to read in IE.)
- Browse to http://[yourservername]:3333/sdata/$system/adapters.
- Enter any SalesLogix username and password, and then click OK.

- 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.
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.
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.

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.






