web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics SL (Archived)

SL2015 Software Development Kit

(0) ShareShare
ReportReport
Posted on by

I am attempting to utilize the Software Development Kit to build a native SL application. While the documentation seems to be a nice reference there is very little about the way to bring everything together. I was looking for something more such as a document that talked about the functional philosophy of the SWIM API, some code examples, and maybe a simple step by step to build a simple multi level application. I've gotten as far as defining the data structures,  and implementing the cursors yet I don't seem to be getting my dbnav to function. In the past there used to be training materials and a course for SL Development. Any help or direction on where to find more documentation beyond the Software Development Kit pdf is appreciated.

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    on at

    Rob,

    The documentation you are asking for went missing many years back.  I agree that the SDK manual is a decent reference when you want to look for a particular event or action but it sorely lacks a section with an example of creating a screen with a grid from start to finish.  Those of us that have been developing with the SDK have basically learned by trial and error (sometimes lots of trials and errors).

    If you want to provide some more detail on your purpose of the screen, the grid contents,  the DBNAV you have set up and what it is doing or not doing, I would be happy to take a quick look for you.

  • Community Member Profile Picture
    on at

    Rick, thanks for the offer. I did manage to have some break though moments today. Lots of trial and error. I was wondering, I was using straight up SQL in the DBNAV but didn't have any joy until I switched to stored procedures. I always wondered why so many stored procedures just to select * from sometable where keyfield=@parm1. I'm also guessing that stored procedures are required when doing PV instead of DBNav, at least if you want to invoke the Lookup.

    Thanks again for your time.

  • Community Member Profile Picture
    on at

    Rob,

    Someone might be able to tell the technical reasons why but, yes, both DBNav and PV must have a stored procedure.  The PV must also have an entry in the PVRec.csv file as that is what defines the PV form content and layout.

    I suspect the need for a stored procedure stems way back to the time before Solomon (now Dynamics SL) used a different back-end database then SQL Server.

    We, as toolkit developers, stopped asking why and just ask what is needed and go with that.

  • Verified answer
    Apps Mexico Profile Picture
    1,090 on at

    Hi,

    This manual will help you to deploy a screen with a Detail level.

    http://appsmexico.mx/shared_folder/manual_vbtools.rar

    Regards.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans