Login /
Register
 search
 syndication
|
|
 |
Note: this subscription applies to the current blog only.
You will receive each new post via e-mail. Your e-mail
address will not be used for any other purpose.
Browse by Tags
All Tags » SalesLogix ( RSS)
-
|
For some who have been working in the SalesLogix LAN client for years, the transition from using SQL queries to retrieving data using a repository with the entity model can be a difficult change. This post will look at some common data retrieval methods and the SQL equivalents to help you get your head around how to get work done using the entity model.
|
-
|
Ever since Sage released their official SalesLogix community website & forums, I've wanted a better way to search and browse the forums. I've been working on a desktop client that does just this in a better, faster, and more efficient way. So, I'd like to announce the public release of Community Explorer.
|
-
|
For anyone who uses Git Extensions for SalesLogix, I've released a small update that adds some core functionality and makes it possible to complete the entire scenario of setting up and using Git with a SalesLogix project - all from within the SalesLogix Application Architect!
|
-
|
Whether you're using Git, or some other source control system, there are certain files in a SalesLogix model that you do not want to include in your source control. Many part of the files in an exported SalesLogix model are automatically generated by the Application Architect and by the build process when you build your web platform. Having these files under source control would only complicate things when working with multiple developers since you'd each need to merge these automatically generated files with each pull/checkout from source control since they change every time.
|
-
|
The official Sage SData Specification has not been released. SData (which stands for "Sage Data") is a Sage communication protocol. Using SData you have a common protocol that defines data access, consumption, and exchange between Sage application and 3rd party applications as well. The SData specification is now released and public.
|
-
|
Yesterday I announced my new project Git Extensions for SalesLogix. I received a lot of e-mails from people who read that post, so I thought it would be a good idea to record a quick video so you can see it in action and get a better idea how it works. This quick 4-5 minute video will show you how to commit changes in Application Architect to a Git repository and push the changes to an online repository as well, all from inside Application Architect using Git Extensions for SalesLogix. You'll also get a peek at a few other pieces of functionality as well. All in all, if you already use Git Extensions then this will be a no-brainer to use. If you're new to Git, or to source control at all, then this will lower the learning curve significantly and make things much easier to get into.
|
-
|
This blog post is the first of many that will cover the topics of using source control with SalesLogix development, Customer FX's open source initiative, and the new Git Extensions for SalesLogix module for Application Architect. These are three things I am completely excited about. Using source control with SalesLogix development in Application Architect is a necessity if you want to do it right. Git Extensions for SalesLogix is the first of the Customer FX open source initiative that builds on the idea of using source control with SalesLogix development to make it even easier to use Git source control right from inside Application Architect as a natural, built-in part of the application.
|
-
|
There are many reasons why extracting a SalesLogix Report from the SalesLogix database might be useful. There are possibilities of integration, automated running of reports, as well as the need to generate a PDF from some code on a server using a SalesLogix Crystal report. This post will show you how and show you the code to do it.
|
-
|
I announced a while ago that we will be offering some public developer training classes for SalesLogix Web. We will be making some changes to the class outline I posted earlier.
|
-
|
I added a new utility to the Customer FX Labs tonight, the SalesLogix Group Explorer. This utility allows you to dig deeper into the definition of SalesLogix groups than you ever thought possible. You can see the group's layout, included columns, conditions, sort order, and way more. Not only that, but you can also see the SQL query behind the group and view the data that makes up the group, all from outside of SalesLogix. The Group Explorer also gives you the ability to quickly export group data, exporting 100,000 records in a fraction of a second.
|
-
|
Many people who customize SalesLogix have become accustomed to using the built in "SLX Database Support" script to provide things like the quick and easy GetField function to return a single database value. If you've ventured into the .NET Extensions realm, you might want an easy equivalent. The following is a repost of something I posted around a year ago in the Sage Business Partner newsgroups
|
-
|
Over the past several years I've maintained a SalesLogix related weblog at SalesLogixBlog.com. This blog has now moved to a new URL and a new perspective. SalesLogixBlog.com can now be located on the new Customer FX 3.0 website at http://customerfx.com/crmdeveloper.
|
-
|
A question that comes up every now and then is how to create a shorter, prettier key like the Ticket ID used in the support client. This is needed if programatically creating tickets, or if you need some unique number for some custom module such as a quote number. Using the SalesLogix table ID for something such as a quote ID results in a long hard to read value (and won't win you many points with your customer). Creating a SalesLogix “Pretty Key” is easy, but there are some things to know about
|
-
|
The SalesLogix Activity & History tables use a 'Type' field to store the type of Activity. If you look at the TYPE field, you'll see that the values there are numeric values such as '262147'. This number represents the type for the given activity or history record. But for someone new to SalesLogix it might be difficult to determine how & where these types are defined.
|
|  |
|