Boost Your Dynamics GP: Expert Tips for Upgrading Dexterity-Based Applications

Table of Contents

Microsoft Dynamics GP, formerly known as Great Plains, is a robust enterprise resource planning (ERP) system widely utilized by businesses for managing financials, operations, and customer relationships. Dexterity, a proprietary programming language developed by Microsoft, is the foundation upon which Dynamics GP was built. Upgrading Dexterity-based applications within Dynamics GP is crucial for maintaining system performance, enhancing security, and leveraging new functionalities. This article delves into expert tips for upgrading Dexterity applications, focusing on key aspects that developers and system administrators should consider to ensure a smooth and effective upgrade process.

Optimizing User Interface with Windows XP Theme Support in Dexterity¶

Great Plains 8.0 Dexterity introduced support for Microsoft Windows XP themes, bringing a more modern and visually appealing interface to Dynamics GP applications. This enhancement allowed developers to create applications that seamlessly integrated with the then-contemporary Windows XP look and feel. One notable visual change was the rounding of button corners, contributing to a softer and more user-friendly aesthetic.

Enhancing Button Appearance in Lookup Windows¶

For developers working with lookup windows that utilized buttons in columns, the Windows XP theme support required adjustments to button appearance. To maintain visual clarity and consistency, it became necessary to draw two-dimensional boxes around these buttons. This ensured that the buttons were clearly delineated and easily identifiable within the lookup window interface.

Furthermore, the Appearance property of the buttons needed to be specifically set to 3D Highlight. This setting ensured that the buttons rendered correctly with the intended visual style, complementing the Windows XP theme and providing a consistent user experience across the application.

To achieve a perfect fit within the drawn boxes, developers often found it beneficial to reduce the size of the buttons by one pixel in each direction. This fine-tuning ensured that the buttons sat neatly within their designated areas, contributing to a polished and professional user interface. Attention to these seemingly minor details significantly improved the overall visual appeal and usability of Dexterity-based applications in Dynamics GP 8.0 and beyond.

Pixel Size Adjustment for Buttons¶

Dexterity provided convenient keyboard shortcuts to adjust the pixel size of user interface elements, including buttons. By pressing CTRL + UP ARROW, developers could incrementally increase the pixel size, while CTRL + DOWN ARROW allowed for decreasing the pixel size. These shortcuts offered a quick and intuitive way to fine-tune the dimensions of buttons and other UI components directly within the Dexterity development environment. This capability was especially useful when aiming for pixel-perfect alignment and visual harmony in application interfaces.

Enhancing Security with SQL Server Permission Verification Functions¶

Security is paramount in any ERP system, and Dynamics GP is no exception. Great Plains 8.0 Dexterity introduced enhanced security features by incorporating functions that allowed developers to programmatically verify Microsoft SQL Server permissions of users. These functions empowered Dexterity applications to dynamically assess user rights before allowing them to perform specific actions within the database, such as creating tables or adding new users. This proactive approach to security significantly strengthened the integrity and confidentiality of Dynamics GP data.

Two key functions were introduced in Dexterity 8.0 to facilitate SQL Server permission verification: syUserIsDBO and syUserInRole. These functions provided developers with the tools to implement granular security checks within their Dexterity applications.

The syUserIsDBO Function: Verifying Database Owner Rights¶

The syUserIsDBO function is designed to determine if a specified user has database owner (DBO) rights within a given SQL Server database. Database Owner rights are the highest level of permissions within a database, granting the user full control over all aspects of the database.

The function syntax is as follows:

syUserIsDBO()
function returns boolean O_fIsUserDBO;
in'User ID'I_sUserID;
instringI_sDatabase;

Parameters:

• I_sUserID: This input parameter requires the User ID of the user whose permissions are being checked.
• I_sDatabase: This input parameter specifies the name of the SQL Server database to be examined.

Return Value:

• O_fIsUserDBO: The function returns a boolean value. TRUE indicates that the specified user is a database owner in the given database, and FALSE indicates that the user does not have database owner rights.

Example Scenario:

Imagine a custom Dexterity application within Dynamics GP that allows administrators to perform database maintenance tasks. Before allowing a user to execute a potentially critical operation like database schema modification, the application can utilize the syUserIsDBO function to ensure that the user possesses the necessary database owner permissions. If the function returns FALSE, the application can prevent the operation and display an appropriate message indicating insufficient privileges, thereby safeguarding the database from unauthorized modifications.

The syUserInRole Function: Checking Role Membership¶

The syUserInRole function provides a more granular level of permission checking by allowing developers to verify if a user is a member of a specific SQL Server role. Roles are a mechanism in SQL Server to group permissions and assign them to users, simplifying security management.

The function syntax is as follows:

syUserInRole()
function returns boolean O_fUserInRole;
in'User ID'I_sUserID;
instringI_sRole;
optional in 'Intercompany ID'I_sDatabase;

Parameters:

• I_sUserID: This input parameter requires the User ID of the user being checked for role membership.
• I_sRole: This input parameter specifies the name of the SQL Server role to be verified. This can be a fixed server role or a fixed database role.
• I_sDatabase (Optional): This optional input parameter allows specifying a database context for role checking. If omitted, the function checks roles in the context of the current company database or global variables database.

Return Value:

• O_fUserInRole: The function returns a boolean value. TRUE indicates that the specified user is a member of the specified role, and FALSE indicates that the user is not a member.

Role Constants:

The I_sRole parameter in the syUserInRole function accepts specific constants representing different SQL Server roles. These constants are predefined within Dexterity and simplify the process of specifying roles for permission checks.

Fixed Server Roles:

Fixed server roles are defined at the SQL Server instance level and apply to the entire server. Dexterity provides constants for the following fixed server roles:

• ROLE_SYSADMIN: Represents the system administrator role, granting the highest level of server-wide permissions. Members of this role have complete control over the SQL Server instance.
• ROLE_SECURITYADMIN: Represents the security administrator role, responsible for managing server-level security settings, logins, and permissions.
• ROLE_DBCREATOR: Represents the database creator role, allowing members to create new databases on the SQL Server instance.

Fixed Database Roles:

Fixed database roles are defined within each SQL Server database and apply only to that specific database. Dexterity provides constants for the following fixed database roles:

• ROLE_DBOWNER: Represents the database owner role, granting full control over the database.
• ROLE_DBACCESSADMIN: Represents the database access administrator role, responsible for managing logins and user access to the database.
• ROLE_DBSECURITYADMIN: Represents the database security administrator role, responsible for managing database-level security settings and permissions.
• ROLE_DBBACKUPOPERATOR: Represents the database backup operator role, allowing members to perform database backup operations.

Database Context for Role Checking:

The optional I_sDatabase parameter in syUserInRole allows developers to specify the database context for role verification. This is particularly useful in Dynamics GP environments with multiple company databases. The parameter can accept the following values:

• Company ID of the company master table: This allows checking roles within a specific company database.
• Company ID of global variables: This refers to the global variables database associated with the current company.
• Name of the SQL Server system database: This allows checking roles within SQL Server system databases like master or msdb.

Example Scenario:

Consider a custom Dexterity module in Dynamics GP that handles sensitive financial transactions. Before allowing a user to approve a large transaction, the module could use the syUserInRole function to verify if the user is a member of a designated “Financial Approvers” database role within the company database. If the function returns TRUE, the transaction approval process can proceed. Otherwise, the system can prevent the approval and log the unauthorized attempt, enhancing financial security and control.

Best Practices for Upgrading Dexterity Applications¶

Upgrading Dexterity-based applications in Dynamics GP requires a systematic approach to ensure a successful and stable outcome. Here are some best practices to consider:

1. Thorough Assessment and Planning: Before initiating any upgrade, conduct a comprehensive assessment of the existing Dexterity applications. Identify all customizations, integrations, and third-party add-ons. Develop a detailed upgrade plan outlining the steps, timelines, and resources required.

2. Environment Preparation: Set up a dedicated test environment that mirrors your production environment as closely as possible. This allows for thorough testing of the upgraded applications without impacting live operations. Ensure that the test environment includes the target version of Dynamics GP and SQL Server.

3. Code Review and Compatibility Analysis: Conduct a detailed code review of your Dexterity applications. Analyze the code for compatibility with the target Dynamics GP version. Identify any deprecated features or functionalities that need to be addressed. Utilize Dexterity development tools to assist in compatibility analysis.

4. Incremental Upgrades and Testing: Consider performing upgrades in smaller, manageable increments. This reduces complexity and allows for focused testing at each stage. After each incremental upgrade, conduct rigorous testing, including unit testing, integration testing, and user acceptance testing (UAT).

5. Data Migration and Validation: Plan and execute data migration carefully, ensuring data integrity and consistency. Validate the migrated data thoroughly in the test environment to identify and resolve any data-related issues before deploying to production.

6. Performance Optimization: After upgrading, monitor the performance of the Dexterity applications closely. Identify any performance bottlenecks and implement optimizations as needed. This may involve code refactoring, database tuning, or hardware upgrades.

7. Security Review: Post-upgrade, conduct a comprehensive security review of the upgraded Dexterity applications. Verify that security settings and permissions are correctly configured and that the applications adhere to security best practices.

8. Documentation and Training: Update documentation to reflect the changes introduced by the upgrade. Provide adequate training to users on any new features or changes in application functionality.

9. Rollback Plan: Develop a robust rollback plan in case unforeseen issues arise during or after the upgrade process. Ensure that you have backups of your databases and Dexterity applications to facilitate a smooth rollback if necessary.

10. Ongoing Maintenance and Monitoring: After a successful upgrade, establish a plan for ongoing maintenance and monitoring of the Dexterity applications. Regularly apply updates and patches, and proactively monitor system performance and security.

By following these expert tips and best practices, organizations can effectively upgrade their Dexterity-based applications in Dynamics GP, ensuring continued system stability, enhanced security, and access to the latest features and functionalities. A well-planned and executed upgrade process minimizes disruption and maximizes the value derived from the Dynamics GP system.

Do you have any experiences upgrading Dexterity applications in Dynamics GP? Share your tips and challenges in the comments below!