Page 1 of 3123

Archive for the ‘System’ Category

Screen Output Magnification Defaults

There was a support request on the forum today, where the user was questioning the setup from where the default zoom for screen outputs in GP is picked up from.

There is a setting the Dex.ini file which determines the Screen Output Magnification Default. It is MagnifyScreenOutput.

Depending on the value defined for this parameter, the reports will print to the screen zoomed at that level. (i.e.) if this parameter was set up as MagnifyScreenOutput=75 in the Dex.ini file, the screen will open up at 75% zoom.

If any user changes the zoom settings on any report, this field is updated in the Dex.ini file.

You can download the comprehensive list of Dex.ini settings here.

Hopefully this helps the community…

Until next post!

August 13, 2011 · veeyeskay · 2 Comments
Tags: ,  · Posted in: Dex.ini, Dynamics, Great Plains, System Total Views: 1,203

Drill downs in the Security Setup windows

This article explains a very simple feature which may times goes unnoticed in Microsoft Dynamics GP 10 and 2010. We have many windows where we define the security related information. They are listed below.

  • Security Task
  • Security Roles
  • User Security
  • Alternate Modified Forms & Reports

In the windows listed above, you can drill down into the actual GP form (or) report so that you can view the form or report easily and determine if the security task needs access to that window or not.

Security Task window

image    image

Alternate Modified Forms & Reports

image    image

In the following security windows, you can directly drill down into the specific security task, by double clicking on the security task name displayed in the window for a specific role.

Security Roles Window

image

In this window explained below, we can drill down into the specific security role that are listed.

User Security Window

image

This when defining security, we have a drill down from the user security access definition window into the actual security role, which in turn has a drill down into the actual security tasks, which in turn has a drill down into the actual forms and reports.

Hope this helps the community…

Until next post!

August 10, 2011 · veeyeskay · 2 Comments
Tags: , , , , , , , ,  · Posted in: Dynamics, Great Plains, Security, System Total Views: 1,027

Security Window Enhancements in Dynamics GP 2010

One of the cool enhancements (which mostly goes unnoticed) in Dynamics GP 2010 is the new checkbox which is applicable in the Security windows explained below, which allows the users to see only the options selected for the particular record (i.e.) in case of the Security Roles window, the checkbox allows us to filter and display ONLY the security tasks which are assigned to the specific role. In Dynamics GP 10, this option was not available and the user has to scroll through the entire list to see the selected options.

This filtering option is available in the following windows.

  1. Security Task Window
  2. Security Roles Window
  3. User Security Window

The screenshots below depict how these filters work and how they help us see just about the required details.

Security Task Window

image

Security Roles Window

image

User Security Window

image

Hope this helps the community…

Until next post!

August 9, 2011 · veeyeskay · 2 Comments
Tags: , , , , ,  · Posted in: Dynamics, Great Plains, Security, System Total Views: 1,148

Summary of Transaction Statuses in GP

All transaction in Dynamics GP, goes through 3 statuses before its purged from the system. They are

Work Status – Transactions which have not been posted

Open Status – Transactions which have been posted

Historical Status – Transactions which have moved to history tables

Each transaction moves through each of these status in various scenarios, which I preferred to explain in this article.

Transaction Name Work Open History
General Entry When the transaction is created and saved in a batch. When the transaction gets posted. When the year end process is completed.
Quick Journal Entry When the transaction is created and saved in a batch. When the transaction gets posted. When the year end process is completed.
Clearing Entry When the transaction is created and saved in a batch. When the transaction gets posted. When the year end process is completed.
Payables Transaction Entry When a transaction is created and saved in a batch When a transaction is posted and its not paid fully (i.e.) there is an unapplied amount in the payable document. When the document is completely paid (i.e.) there is no unapplied amount in the specific document.
Computer Checks When a transaction is created and saved in a batch When a transaction is posted and its not paid fully (i.e.) there is an unapplied amount in the payable document. When the document is completely paid (i.e.) there is no unapplied amount in the specific document.
Manual Payment Entry When a transaction is created and saved in a batch When a transaction is posted and its not paid fully (i.e.) there is an unapplied amount in the payable document. When the document is completely paid (i.e.) there is no unapplied amount in the specific document.
Receivables Transactions When a transaction is created and saved in a batch When a transaction is posted and its paid or unpaid (i.e.) whether there is an unapplied amount in the payable document or not. When the paid transaction removal process is run from Routines >> Sales.
Cash Receipts Entry When a transaction is created and saved in a batch When a transaction is posted and its paid or unpaid (i.e.) whether there is an unapplied amount in the payable document or not. When the paid transaction removal process is run from Routines >> Sales.
Bank Transaction Entry   When the bank transaction is posted. When the bank transaction is reconciled.
Bank Receipts Entry   When the bank transaction is posted. When the bank transaction is reconciled.
Bank Transfer Entry   When the bank transaction is posted. When the bank transaction is reconciled.
SOP Quotes Entry When a quote is created and saved in a batch.   When the quote is transferred to an order/invoice.
When the quote is voided.
SOP Order Entry When an order is created and saved in a batch.   When the order is transferred to a backorder/invoice.
When the order is voided.
SOP Invoice Entry When an invoice is created and saved in a batch.   When the invoice is transferred to a back order.
When the invoice is posted.
When the invoice is voided.
SOP Backorder Entry When a backorder is created and saved in a batch   When the backorder is transferred to an order/invoice.
When the backorder is voided.
SOP Return Entry When a return is created and saved in a batch   When the return is posted.
When the return is voided.
Purchase Order Entry When a purchase order is created and saved.   When the remove complete purchase orders routine is run from Routine >> Purchasing.
Receiving Transaction Entry When the receiving transaction entry is created and saved.   When the receiving transaction entry is posted.
Purchase Returns Entry When the return entry is created and saved.   When the return entry is posted.
Inventory Transaction Entry When the inventory transaction is created and saved.   When the inventory transaction is posted.
Inventory Transfer Entry When the inventory transfer is created and saved.   Wen the inventory transfer is posted.
Assembly Entry When the assembly entry is created.   When the assembly entry is posted.

Hope this article is useful to the community…

Until next post!

May 8, 2011 · veeyeskay · No Comments
Tags: , , ,  · Posted in: Dynamics, Great Plains, System Total Views: 1,032

Rebuilding Corrupt Resource Descriptions in Dynamics GP

Hi all

Today, I was working with one of my colleague on an issue he faced in using the Resource Description functionality to view table and field information for a few tables. When he was browsing through the table details, he noticed that the actual SQL table definition and the table definition in the Resource Description window did not match and had inconsistencies. He had tried to drop and recreate the tables many times and still the same issue. On further analysis he noticed that the inconsistency occurred in many standard GP tables as well and I helped him with the solution on the same which I decided to document here to benefit the community. 

The cause for this issue was corruption of the index files for the table and field resource definitions. These files are located in the Data folder in the Dynamics GP application folder (in case of v9, v10 and v2010).

  • OLFD001.dat
  • OLFD001.idx

Please see the screenshot below for these files on the Data folder.

image

Delete these files (after taking a backup) from this folder and when you launch the Resource Description window and select the Product, these files will be rebuilt again, thereby creating a fresh set of indexes. After the indexes were rebuilt, the resource description windows showed the right table and field definitions.

Most of the time when we note discrepancies, we always tend to assume that the SQL table is at fault and try to recreate it (depending entirely on the resource description window information). However, that’s always not the case as we note in this scenario where the SQL table was correct and it was the indexing file for resource descriptions were faulty.

Hope this helps the community…

Until next post!

May 6, 2011 · veeyeskay · No Comments
Tags: , , , ,  · Posted in: Dynamics, Great Plains, System Total Views: 1,419

Dynamics GP Technical Database Guide –DYNAMICS Database

Hi all

In this article, I have posted the link to my Christmas present to the community folks. This is a detailed database guide for Microsoft Dynamics GP. Smile

I have posted the link to the guide for the system database (DYNAMICS). The company database guide will follow.

This guide provides detailed specifications of the various tables, views and stored procedures present in the DYNAMICS database (excluding HR and Manufacturing module – which would follow suite at a later time). Smile

This guide can be downloaded here.

Hope this is helpful to all. The company database guide will follow soon. Keep watching my blog for more details on it soon. Smile

Note: After downloading the file, right click the CHM file and click Properties. In the General Properties tab, make sure you click on the Unblock button (if it is present and enabled) before you open the CHM file (so that the contents are seen properly).

Until next post!

December 27, 2010 · veeyeskay · 6 Comments
Tags: ,  · Posted in: Dynamics, Great Plains, SQL Server 2005, System Total Views: 1,640

Dynamics GP 10 Login Issue After Upgrade from Great Plains v8

Hi all

I was in the process of upgrading one of our clients from Microsoft Business Solutions Great Plains v8 to Microsoft Dynamics GP SP4. The upgrade process went fine, but after the upgrade was completed, I landed up at a strange issue where none of the users were able to login and they were getting the following error at the time of login.

image

However, the ‘sa’ user was able to login successfully without any issues. Once I tried to reset the password from the User Maintenance window, the user is able to log in without any issues. Wondering what could have gone wrong, I turned to the ever reliable David Musgrave to see if he had an idea on why this happened. He immediately directed me to his blog article which talked of Why does Microsoft Dynamics GP encrypt passwords?

This article threw some light on the password encryptions in Dynamics GP 10. It looks like the password encryption algorithm has changed in Dynamics GP 10. Hence a user enters the password in Dynamics GP 10, the application encrypts the password using the new v10 encryption algorithm and sends it to SQL Server, which causes the GP login to fail, because of the encryption algorithm mismatch between v8 and v10.

However, there is a work around which can overcome this functionality in GP and make GP v10 use the old algorithm to encrypt the password. This needs an update to the Dex.ini file. You can add the below given property line towards the end of the Dex.ini file.

SQLLoginCompatibilityMode=TRUE

Save the Dex.ini file and launch GP and now when the user tries to login using his old password, it allows him to login, but prompts him to change the password during his initial login. The user can change his password and continue logging into Dynamics GP v10 without any issues.

Note: Once all the users have changed their passwords in the initial login, we can remove the above property line from the Dex.ini file.

I should definitely thank David Musgrave for this tip he provided me, which helped me resolve the issue in a jiffy. :) I hope this article is helpful to all.

Until next post!!!

June 14, 2010 · veeyeskay · One Comment
Tags: , , , , ,  · Posted in: Dynamics, Great Plains, System Total Views: 34,793