Skip to main content

From the Microsoft Dynamics GP Blogs: Security; ODBC connection; GL year-end close; Bug with payment terms

by MSDW Reporter
Editorial Team,

In this week's Microsoft Dynamics GP blog roundup:

  • Security in Dynamics GP
  • Troubleshooting an ODBC connection
  • Making corrections that impact the GL year-end close
  • Bug with end of month payment terms in GP

Security in Dynamics GP

An author writing on the Professional Advantage blog, noted that Dynamics GP security is only "granted," it's not assumed, which means that every user in the system must be given the permissions that they have. As such, users cannot do anything in Dynamics GP until they get access to the tasks they need to do within each company. And since it is role based, users must also be granted their appropriate roles.

The author explained that the security available in Dynamics GP out of the box is account security and field level security. In the blog post, the author then offered tips to ensure security in Dynamics GP.

Troubleshooting what should have been a working ODBC connection

On the Dynamics GP Support and Services Blog, David Loegering stated that recently he had a case where a customer was setting up a test database and the GP client server stopped connecting. He noted that the troubleshooting steps in his blog post will enable users to figure out the problem when a connection problem comes up.

In this customer's case, although there weren't any errors, GP would just not connect. Loegering stated that when testing the OBDC connection nothing came up, although typically there would be a pop-up saying the connection was successful or that it failed.

We did the regular troubleshooting of temporarily turn[ing] off the antivirus software, removed/added the ODBC connection, made sure the latest updates were installed, checked for pending reboots, temporarily disabled the firewall, and still if you clicked on Test Data Source nothing happened.

Loegering then went through the steps that you can use to troubleshoot a variety of connectivity issues. In this case, he determined the problem stemmed from corrupt or missing files, which he was able to correct.

Making corrections that impact the GL year-end close

FREE Membership Required to View Full Content:

Joining gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us here

About MSDW Reporter
More about MSDW Reporter