I'm trying to get from 4 to 2009 but can't due to Lanham not releasing their credit card code in 2009. Does ANYONE have an in with Lanham that can get this done? We were told in November that all their add-ons would be ready for the release (November 08). EShip was not released until March, and we are still waiting to get their Credit Card add-on.
EDIT- I should not have posted a rant here- sorry.
"There are only two truly infinite things: the universe and stupidity. And I am unsure about the universe." - Albert Einstein
Corollary- Build and idiot proof system and nature will build a better idiot.
0
Answers
That's not really a fair statement for Lanham specifically.
You should hold up on upgrade if you have ANY add-on, or until it's actually released by the company that made the addon.
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
As much as 2009 is a great product, and I think for new clients its probably a great starter product, I really would recommend that you wait for Service Pack 1 if you are upgrading. If you don't then you are going to really regret it a week after SP1 is released, and you realize all the stuff in it that you need, and the additional cost its going to add to your project.
I know you really don't want to hear this, and I would agree with you that the delay's from Microsoft are extremely unfair, especially for people that have been paying support for 3 years in anticipation of this new product. You have waited a long time to move from 4xx, so it is probably better to wait just a few more months for the new product.
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
What's funny is that Lanham was actually part of TAP program, and there are customer that are using 2009 version of E-Ship. My guess, they are running into many technical issues, and so they don't want to release the software because it won't work.
Lanham Credit card uses I believe IciVerify and I wouldn't touch IciVerify with a 10 foot pole. That software is integrated through a file based integration that fails constantly. Iciverify has build a virtual modem in Java and that's how it communicates with credit card authorization. It constantly fails, and you have to reboot the pc for it to work.
Not really. I think that the big issue is the technology jump of making add-ons work with the RTC. Once that is done, moving to SP1 should be quite trivial since it will just be a code update. Its quite a job to get some add-ons to work in this new environment, lots of experimenting and testing, but of course once that is all done the next one is easy.
2.0 - 2.6 - the line was it is a major upgrade.
2.6 - 3.1 - the structures have changed, bla bla bla
3.1 - 3.7 - bla bla bla
3.7 - 4.0 - bla bla bla
4.0 to 4.0 SP1, SP2 SP3, the same thing
In fact the delays and problems with add-on's actually discouraged us from upgrading, we skipped 2.6, 3.1, 3.7, and waited all the way to 4.0. Of course we also had to skip the 4.0 SP1, SP2 and SP3 , instead we had to pay our developers to downgrade the bug fixes, since the cost of actually appling the whole service pack was cost prohibitive
The other issue is that there is no information as to how much testing and quality of code has been done.
Also when addons upgrade their version to Nav version, very little testing is done.
For example LS Retail released 4.0 sp2 version of their database. First of all it was late for months, and when we finally got it we couldn't post a single transaction. There was a key changed in ILE and LS Retail was using the old key.
So obviously they didn't test at all. The quality of the code speaks for itself if you look at the LS code.
I would be very careful of solution that effect inventory/serial/lot. NAV has bugs in these area and they are constantly fixing them. When you add a vertical solution that modifies these areas, you will be in a world of trouble when you start running into issues.
MS NAV should implement the missing on inventory features and do not rely on ISV in regards to inventory.
Another issue with Lanham is that they've combined E-ship and EDI into one product, so if you purchase E-ship you get hundreds of objects from EDI that you may never use.
Our add-ons are relatively straight forward and come out on time.
Eship is addressing a major area of functionality that probably should be in the base product.
Microsoft should take some of the money it is throwing around and use it buy key ISV products and bundle them into the base product.
I was amazed that Microsoft was willing to pay 44 to 47 billion dollars for yahoo. For a tiny fraction of that they could buy every broad-based ISV product out there and integrate them into their ERP systems.
http://mibuso.com/blogs/davidmachanick/
For example MS bought warehouse management from Lanham, it took 3 or 4 version and in several areas a complete rewrite to make it a usable product.
RIS Plus, LLC
The add-on does use ICV however, since version 3.19 of Lanham and the current version of IC Verify, we have had very few problems. I haven't had to reboot the server running the software for months. We have 4 locations in three states pushing over 5K transactions last month. I think one failed to retrieve the answer from ICV. It works.
As to the rush, we are rebuilding our web site on a new platform. Need to tie it into NAV. Want to use Web Services to do this. Plan to roll out 2009 in classic client and use the Server service to just handle web service requests from the web site. The business perception is that the new site will increase our web revenue by a significant amount (very important in this market) thus the priority.
As this started as a rant :oops: , thus should not have started, I'll leave it here. We like the add-ons supplied by Lanham.
Corollary- Build and idiot proof system and nature will build a better idiot.
A combination of NAS with XML and SQL views also works well if you need instantaneous responses.
http://mibuso.com/blogs/davidmachanick/