Kinda Back

its been a while since I last blogged. Unfortunately life gets in the way and its has been very busy with the company. I am hoping to be able to blog more often as I get back on track of sharing information on development and now Infor CRM (formally Saleslogix). Shortly I will be heading to Build 2016, the Microsoft developer conference and I am looking forward to see the direction of the platform (OS) as well as the development tools. Just recently Xamarin announced it was acquired by Microsoft, and as a certified Xamarin developer I am also looking for more information with regards to Microsofts direction of the tooling. Finally I have been accepted into the Hololens developer program, and will be attending a developer session while in San Francisco. It will be great to kick the tires on some actual equipment.

Not much to add at the moment, other then Infor CRM 8.3 should be released really soon …


Posting Quotes in MAS from ERPLink

One of our customers required posting quotes from Saleslogix into MAS. Though the transaction type was available it was not possible to actually post anything except for a standard order. It seems that the spSOApiSalesorderIns stored procedure had a fixed transaction type of 801 (order) where as quote would have needed a value of 840.

We have updated the stored procedure to now accept a transaction type (801, 840) and when selecting either an ‘Order’ or ‘Quote’ the correct type will be passed down and processed as expected.

This updated will be in the next version of ERPLink 2014.

Dynalink 2014 – Small Changes

I’ve been working on a update to Dynalink 2014 and sometimes the smallest changes mean the most.

Change 1 – Job Status Window

Dynalink use to show each of the jobs in separate windows for each configuration. The more I thought about it the less it made sense. The window also would show some internal ids (task and map id) which does not actually make sense for a customer facing view. I have updated the window to now consolidate all running jobs on a given server and changed the columns to make more sense.


I have also moved the stop job menu item from the configuration list to the job status list.

Change 2 – Toast Messages

I have been playing around with the notion of making some of the notifications less intrusive. The one place that I was not happy about was when a job was started from the Administrator. When started a a modal message box was displayed that the user would have to close to continue on. Though not a bad thing I was annoying me enough that I wanted it changed.

As such we have added a Toast Service to our architecture that can be called in place of some of the dialog popups to remove the extra step of closing a status dialog.


I am sure there will be other changes over the next few weeks as we continue to improve Dynalink

ERPLink for Saleslogix 8.1

Currently it looks that there is an issues with the Saleslogix .net extensions that brings an incompatibility to any previous versions of a compiled extension. We can get around this issue by explicitly targeting the version of .net extensions that are supplied with 8.1. We are working on a solution but In the meantime if you are upgrading to Saleslogix 8.1 and require a copy of ERPLink get in contact of support and we can provide you a custom build (If you are a Bittelligent customer)

The Great Path Issue .. Crystal Sucks

wow its 2014 and we are still having problems with the path variable. I have installed ERP 2013/2014 to do some development and testing of ERPLink and was getting the Launcher could not be found error. I tried to Google the issue, and even use Sage KB/Sage city to get an indication why the issue would occur. Unfortunately I could not readily find an answer however a thought dawned on me and I decided to look at the path just for giggles and of course it was well over its usable limit. The biggest culprit was crystal reports/business objects. I resolved the issue by creating a new environment variable for CrystalPath and copied all of the business object path parts into the new variable. I tacked ;%CrystalPath% at the end of the Path variable and now ERP 2014 client opens and runs as expected.

Make sure you check your path if your having load issues with the client after an install!

Pruning the Bushes

From time to time we need to cut back the bushes and trees to make them more manageable in our garden. This also helps ensure that they do not grow too big for their surroundings. Once done we can sit back on our deck and have a nice cold drink and just enjoy the view.

With Saleslogix 8 some changes to the way of the product got delivered made be think of this analogy. Within that timeframe a decision was made to include several localizations out of the box (French, Italian, Russian, and Danish I believe). The VFS (where all the customizations were stored) grew from approximately 200 MB all the way to a whopping 1GB when exported to the file system. Now though I think for the community as a whole this is a good thing to ensure that all localized versions are rolled out at the same time it does have a cost for organizations that really only need one targeted language.

Interesting enough a solution is fairly simple before you start your development/upgrade scenario. Lets just do some pruning. Basically I recommend after backing up your VFS for safe keeping going in and purging the non needed localizations


The easiest way to start is to export the VFS to a file based model (FLS) through the workspace manager.This allows us to work locally and use simple search/delete from windows explorer.

The main resource files are scattered throughout the model so I will start at the root and of the model and using the search look for all the files that end with *.[locale].resx


I complete this search for the following terms:

  • *.de.resx
  • *.ru.resx
  • *.it.resx
  • *.fr.resx

Each search should return approx 1522 files. After each search select all the files and [delete]. Once you delete all of the resource files you have removed about 40MB of extra assets.

The next step I do is visit each of the portals in the model. There are 2 sub folders in each portal that we need to be thinking of.

  1. SupportFiles\Bin
  2. SupportFiles\Help

Each of these folders contain specific sub folders for each of the extra Lanages. In these folders select the \RU, \IT, \FR, \DE sub folders and delete them as well. Deleting the sub folders in the bin folder will save several MB however the real win is in deleting the localized help folders. In the SalesLogix client portal the help saves more then 350MB.

Ultimately once this is all done the size of the VFS goes down from 1.04GB to 448MB. Quite the savings and ultimately will aid in deployment times and storage backup needs. This should also lower the memory requirements in depoyment as your removing 6+ K of files that need to be inspected for changes.

As always good development means good practices.