From the Microsoft Dynamics GP Blogs: 'Closing the loop'; Problems logging in; Project accounting; Post to history

From this week's Microsoft Dynamics GP blogs:

• Are you ‘closing the loop' with your Dynamics GP system integrations?
• Problems logging into Microsoft Dynamics GP as "sa" after password change
• Dynamics GP project accounting
• Post to history in Dynamics GP

Are you 'closing the loop' with your Dynamics GP system integrations?

On the Dynamics GP Land blog, Steve Endow wrote that he's been developing system integrations for such a long time that he often forgets that some parts of system integration design might not obvious to his customers:

I have been working with a company that is integrating their document management solution into Dynamics GP. Their software will capture a scan of a document, such as a vendor invoice, their workflow will route the document image, a user will verify the vendor and the expense accounts, and once the workflow is complete, the software will import the invoice data into Dynamics GP using eConnect. 

Then once the invoice is imported, a GP user can view the payables transaction invoice in Dynamics GP, as well as open the scanned invoice image directly from GP, Endow wrote.

Although all that sounds pretty straightforward, Endow wrote that the non-technical customer contact, who doesn't design or work with system integrations on a regular basis, likely isn't aware of an important issue - closing the loop between the two systems.

You can find out why that's important here.

Problems logging into Microsoft Dynamics GP as "sa" after password change

On his AzureCurve blog, Ian Grieve wrote that recently he's been working with a client ...