Login /
Register
 search
 syndication
 about
|
|
 |
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 » Application Architect ( RSS)
-
|
Once you've started creating customizations for your SalesLogix Mobile, at some point you'll want to start getting those customizations into production by deploying them or bundling them to add to your production system. This article will walk...
|
-
|
Using external assemblies in SalesLogix development, rather than built in Code Snippets, is a better & more efficient way to customize SalesLogix entities, with far less headaches. Some of the benefits include a better and more complete development environment and having all your code in one place (instead of digging around through all the entities to get to the code). Let's take a look at how to do it.
|
-
|
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.
|
-
|
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.
|
-
|
I just came across some new info that has been added to SalesLogix 7.5.2 (currently in beta). The ability to add custom controls to Application Architect for use on QuickForms. This is a completely welcome and awesome addition to the SalesLogix Application Architect. The following is taken from the 7.5.2 AA help files...
|
-
|
The transition from using pre-version 7.5.1 "C# Snippet Actions", where the code is placed inline in the form, and the new "Code Snippet Actions", where the code is compiled into a separate DLL and a psudo-form reference is passed in, can be frustrating at times. I ran into yet another instance of that today. Before, we were spoiled using the C# Snippet Actions. We had access to everything on the form. Everything. That's no longer the case with Code Snippet Actions. While in a Code Snippet Action, I needed a reference to the current parent entity (not the current entity that is exposed via form.CurrentEntity, but it's parent). This Code Snippet Action was on a LoadAction of an Insert screen so the parent had not yet been set. Let's take a look at how to solve that.
|
-
|
Usually by the third time I see a question asked, I realize it needs to be a blog post. I've been asked by a couple of customers how to add a default sort to the products list on the Add Opportunity Products form in the SalesLogix Web client. The question of how to add a default sort to the list of products in the Add Opportunity Products form in the web client surfaced again today so I am posting the answer here.
|
-
|
A while back I wrote an article on setting the sort for a DataGrid in SalesLogix Web at runtime. That solution worked great in SalesLogix 7.2. However, things changed in SalesLogix 7.5 so I thought it was time for an update to that original post. Let's see what changed and how to make it work again.
|
-
|
There are likely many cases in SalesLogix Web where you need to access properties on the User and Security related entities that are not included in the entity by default, meaning that there is no public property exposing the value. For example, the IsManager property on the User entity. Modifying these entities won't work, so how do you get to these properties? This post provides an explanation of why you can't modify these entities and how to get to these property values.
|
-
|
There might be times when you need to do some custom formatting in SalesLogix DataGrids that goes way beyond just simple formatting. A perfect example of this is taking a simple value, such as an indentifier from another external system where you want the value in the DataGrid to be a part of a hyperlink to this other system. In this scenario, you might have a value like "12345", which identifies a matching record in another system and you want this to become <a href="http://theothersystem.com/something?id=12345">12345</a> in the grid. This is where the CustomFormatColumn column type comes in. The problem is that this column type can be a little confusing and not well documented.
|
-
|
When you're developing for SalesLogix Web in the Application Architect, there are three actions that a developer must use during the process: building interfaces, building the web platform, and deployment. For someone starting out with the Application Architect, the reasons behind each of these actions can be confusing. Even more confusing can be when one is used vs another. This post will attempt to explain these three actions and when/why they are used.
|
-
|
I last posted about creating a business rule to return a list of objects. Today, I will take that a step further and bind the List to a DataGrid using the built-in GetByMethod for binding the list.
|
-
|
One of the best things about working with the SalesLogix 7.2 Web application is how great the entity model is. You have this single place to put all your rules and logic, the UI is really just an afterthought. Something that I do quite often is create business rules to return data specific to an entity instance. For example, a rule to return the primary contact for an account. Let's take that a step further and return a list of objects from an business rule. For this scenario, we'll create a business rule that will return a list of child accounts for the current account instance.
|
-
|
IIS7 is not yet officially supported for hosting SalesLogix 7.2 Web, but this post will outline a new find that will make it possible to develop and test a SalesLogix Web deployment on Vista (and Windows Server 2008)
|
-
|
A common thing that any developer will do when creating a form for an application is to create sections for controls to group similar controls in a panel or other container, making it easy for the user to see that the values are related. There isn't exactly support for creating these "sections" in the SalesLogix Web QuickForms. With a quick bit of tweaks we can easily accomplish this result.
|
|  |
|