From the GP Blogs: The Basics of Integration Manager; Closing Purchase Orders Safely; “Field Service Anywhere” Discontinued; Business Essentials Technical Demonstration Toolkit

by Jared Berezin
published January 14, 2010

Understanding the Basics of Integration Manager: Q Factor's Blog provides a clear and detailed explanation with screenshots for the end user: "I find that most end users have a difficult time understanding the fundamentals of IM, so I want to outline a very simple integration design for those of you who are new to building integrations and feel a bit overwhelmed by the tool.

...

Requires FREE Membership to View

Login
Become a Member Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more, and it’s all FREE. You’ll also receive periodic email newsletters with the latest relevant articles and content updates.
About Jared Berezin
Jared Berezin serves as a contributing writer to MSDynamicsWorld.com. With combined interests in technology and science, Jared previously served as a writer for Dana-Farber Cancer Institute, drafting scientific narrative reports on the latest advancements in cancer research. Jared has also served as associate marketing specialist for International Data Corporation (IDC), a market research firm. In this position, he planned and executed strategic marketing initiatives for IDC's software and services research programs, and wrote outbound communications to the press, existing clients, and prospects. Jared also has experience working for several local newspapers in eastern Massachusetts. Jared graduated with honors from Colby College with a BA in English and creative writing.

Read full bio...

Field Service Anywhere NOT Discontinued

On January 20th, 2010 mpolino said:

Just to be clear, Field Service Anywhere is NOT being discontinued. Microsoft is simply switching it from an OEM product back to a 3rd party vendor product. I.B.I.S. will continue to grow, support and enhance Field Service Anywhere.

I'm sure this was a headline space issue because the body of the article got it right but the headline is misleading.

Mark