

Until one day we noticed that some records that were sent to the product through my integration weren't in the database. Great, makes sense.Īfter working through numerous bugs in the product, we finally got it working and I got my integration working with it as well.

That web service also serves as the API if you want to integrate with their product. The product has a web service that serves as the back end to their Dynamics GP integration-so their custom GP windows call the web service, rather than calling DLLs. In 10 minutes I found a half dozen bugs in the product-and that was on just 1 window. These are glaring, obvious, brick-wall-in-the-middle-of-the-road bugs that will cause an error with the simplest data entry example.

These aren't subtle bugs where you need to perform 26 steps with specific data in perfect sequence to trigger them. While the product sometimes technically works, it is absolutely riddled with bugs. The last several months, I've been working with a third party product that integrates with Dynamics GP.
