Sage 100

I have seen the chatter on the SDATA subject as related to CRM but I don't see any comments about the new Security Tab in Roles for Sage 2013 ERP (5.0). Trying to accertain what purpose and impact does the new security tab in Role Maintenance SDATA have. Tried to get information on this from Support but no one could give me a straight answer. Tried the Help files and publications but nothing as far as the SDATA application and how it should be used. Anyone with information on this ROLE security feature specifics please share.

@PhilMcIntosh and @JohnnyPabian do either of you have any info?

I have been pestering Lori Maloof for SDATA docs regularly since the Atlanta Customer Symposium in January and have not yet gotten past ""We'll have it at Summit."" There are sessions scheduled at Summit, for 100 & 300. As for the security tab, I believe it is like the ODBC tab except it controls SDATA access instead of ODBC access. However, I could be attributing logic to Sage development efforts that is not in fact there...

Wasn't this announced LAST year? Perhaps not having a technical staff has restricted their ability to deliver what has been promised.

Joan - ""SData Security"" tab in Role Maint is used for granting access to MAS tables for applications that are built with the new SData connector. You can't click that tab until you click Enable Native SData Provider option in LM > System > System Config. Then you'll see the tables and the ""contracts"" (the parent-child table relationships). But for all 5.0 clients at this point, since nobody is using it (no doc) it shouldn't have a bearing on any issues you're running into with 5.0, as far as I know. You didn't find any help files or docs on which is true - some of us have been seeking a proper blow by blow doc for a while. In fact, I hope they create videos on it similar to what Steve Malmgren did for scripting - who knows. But I did find this ""starter"" guide a few weeks ago. It's not bad. It may not be official yet either but it will keep @PhilMcIntosh busy for awhile :) The pic on Page 5 gives you an idea how it supposed to work at a high level.

Right on @JeffSchwenk

Here's a link from Sage's site talking about where they plan to use SDATA. We shall see. http://interop.sage.com/daisy/sdataOverview/CurrentSDataProjects.html

Interesting that they are using it to integrate Sage 50 with Act.

Thank you all for your feed back. There are errors now when trying to rerun Crystal install either from the Productivity Tools in Autorun or from the folder from the iso packet. C++ is showing needed but error when trying to install. Now wants full installation of MAS on the workstation. Crystal is installed but does not reflect in MAS with a designer button. The installation of the crystal is to the C drive. This does not register it then as a program file (not seen in the program listing as you normally would under the Sage application). The Installation is going to the program folder under SageSoftware. Still Sage has no specifics on this SDATA 'Feature'; used in providing external applications access to the MAS data. Well that includes Act, SPS, and Crystal. I went ahead and set this up on the second client install to see if the issue continues. There may be one more factor in this mess and that is the designer button. (error is specific to the workstation and not convinced that the SY_ReportSetting record is being created corrupt. The 2 areas this is happening in also involve subreports (payroll and AP checks). Hope this resolves soon.