Dynamics GP includes functionality to
automatically name new accounts based on the account segments selected.
For example, if a user creates account number 01-4000-000 and the three
segments correspond to Company A, Revenue Account, and South Region,
Dynamics GP can automatically name the account Company A-Revenue-South.
This is a huge time saver, reducing data entry for new accounts.
If, however, a user keys a segment without an
associated description they get an informational message providing the
opportunity to add a description. Included in that informational message
is the option to turn off the message:
The actual wording of the checkbox is Do not display this message again
and it really means it. Once this checkbox is selected for a user the
feature to allow entry of a segment description on the fly is completely
disabled for that user. Additionally, there is no option within
Dynamics GP to turn it back on. This can be a real nightmare if the user
designated to create accounts accidentally turns this off.
Since Microsoft has forgotten to include a switch to
turn this feature back on, administrators will need to hack their way
through some simple SQL code to make this available again. Turning
Account Segment warnings back on is the focus of this recipe.
How to do it...
To re-enable Account Segment warnings:
1.
Open Microsoft SQL Server Management Studio and connect to the SQL
Server used for Dynamics GP. Use either a username and password or
windows authentication to connect.
Because of the
way that security is implemented between Dynamics GP and SQL Server a
Dynamics GP user login will not normally work here. The exception is the
sa user, which is also the SQL Server system administrator login:
2. Click on New Query and select the appropriate company from the drop-down menu on the top left. The sample company is named TWO. In the query area on the right, enter the following script:
Delete from SY01401
where coDefaultType = 13
This will enable Account Segment warnings for all users.
3. To turn on Account Segments for a single user add this third line and change myUserID to the appropriate user ID:
4. Click on Execute to run the script:
How it works...
Fixing features that the developer left out
is what hacking is all about. In this case, Microsoft simply missed the
option to turn this feature back on for a user and it can be very
painful if the primary account entry user accidently turns it off.
Fortunately, an administrator can re-enable the Account Segment warning
with just a few lines of SQL code.
