Product:   Auditor
Category: Functionality

Auditor is a simple background process that has no noticeable effect on performance. During data entry and processing, users cannot type fast enough to slow any processing of audits. In rare cases, if an audit is set up to track changes to records that are being batch processed, such as posting, you may see up to a 5% slowdown in the process. For instance, if it takes 10 minutes to post a batch of records, with Auditing you may see that process take an additional 30 seconds.

One potential slowdown that could be encountered is a server slowdown should the audit log fill up and overtake a SQL server. Basic planning and system maintenance of the audit log will prevent any issues arising from the audit log growing too large.

Product:   Auditor
Category: Functionality

Within Great Plains, audits can only be viewed with Smartlist. Standard Smartlist security can secure this Smartlist object at the level appropriate for your environment. A purging and export utility window, whose security is defined using standard Great Plains security, will allow a user to export audits to an xml file. Finally, all audits appear in a single system table in the database, from which users with appropriate access can report.

Product:   Auditor
Category: Functionality

Depending on your need to answer the "why?" question of audits, you may optionally choose to have users prompted to enter a note when an audit occurs. For instance, you may be auditing US payroll and may want to track audits to Last Name, First Name, and Social Security number. Because it is uncommon for someone to change their SSN, you may require a user to enter a reason for such a change. A note-entry screen will pop up for the user to complete when such an audit is set up.

Product:   Auditor
Category: Functionality

The primary method for viewing audits is through Smartlist (formerly Explorer) within Great Plains. There is an Audits object added to the Smartlist tree view. Standard Smartlist security can secure this Smartlist object at the level appropriate for your environment.

A built-in archiving and purging utility can export audits into an xml file which can be used in a variety of methods for reporting. Additionally, since all audits are tracked in a single system table, reporting using an external reporting tool such as Crystal Reports is straightforward.

Product:   Auditor
Category: Troubleshooting

The latest versions of Auditor have an Integrity Check button on the About Box, which will also run automatically if there are errors in a setup of an Audit. Print out this report and use the guide below to resolve specific issues. If you get stuck on any issue, e-mail your report list to support and we will direct you with what to do.

TABLE XXXX IS NOT ASSOCIATED WITH A GROUP. This is because the table isn't associated with a group, and the latest version requires each audited table to be associated with a group. Open Group Maintenance and create a group if you haven't already. Then use the ADD/PLUS button to the right of Tables to look up a table to add. Find the unassociated table in the list, and select it.

FORM XXXX IS NOT ASSOCIATED WITH A GROUP.This is because the form isn't associated with a group, and latest version requires each audited form to beassociated with a group. Open Group Maintenance and create a group if you haven't already. Then use the ADD/PLUS button to the right of Forms to look up a form to add. Find the unassociated form in the list, and select it.

TABLE XXXX IS NOT MARKED TO TRACK EDITS, BUT HAS FIELDS CHECKED TO AUDITFrom Group Maintenance, display the group this table is in. Double-click on this table in the tableslist to enter Auditor Table Maintenance. Check the "Track Edited Record" checkbox. ClickOK to save.

TABLE XXXX DOES NOT HAVE A COLUMN SEQUENCEFrom Group Maintenance, display the group this table is in. Double-click on this table in the tables list to enter Auditor Table Maintenance. Click the OK button. This will add background data that is needed for the table to audit properly.

FORM XXXX FIELD YYYY IS NOT AUDITABLE AND MUST BE UNMARKED.From Group Maintenance, display the group this form is in. Double-click on this form in the forms list to enter Auditor Form Maintenance. In the list of fields, find the specified field and unmark it for auditing. Certain fields, such as push buttons, cannot be audited.

FORM XXXX DOES NOT HAVE ANY KEY FIELDS SPECIFIED. From Group Maintenance, display the group this form is in. Double-click on this form in the forms list to enter Auditor Form Maintenance. Use the wizard or choose fields from the list of fields on specific windows to pick key fields. Each audited window must have at least one key field selected. If you aren't sure what a key field is or what to choose, contact support. (An example of a key field in Vendor Maintenance would be the Vendor ID. In Customer Address Maintenance, the key fields would be Customer ID and Address ID.)

Product:   Auditor
Category: Functionality

The Activity Tracking feature in Great Plains is different in its scope and purpose than Auditor. Here are the major differences.

First, Activity Tracking will track failed logins and failed accesses to forms and reports. It also tracks posting actions and process server actions, as well as access to Report Writer and Modifier. Auditor is not intended to track these things.

Where there is some overlap, Activity Tracking will track additions, deletions, and modifications of Master records, Setup records, and Transaction records. Master records include Employee Master, Customer Master, Vendor Master, etc. However, when a modification occurs on a record, Activity Tracking only tells you that a given record was modified, but does not tell you what was modified. On the other hand, Auditor will track not only Master records, it will track any and all records, including those in third party products. When a change is made to a given field, Auditor will track the field name, its old value, and the value it was changed to. Auditor gives much more detail on the specifics of changes.

Another issue with Activity Tracking is when it tracks changes for tables that have more than one field as a primary key. For instance, it will track Customer Address changes, but when it reports, it will only tell you the Customer ID. The Address ID will be missing. With Auditor, you will be able to capture both the Customer ID and the Address ID to determine which record was audited.

Auditor will allow you to pick and choose which tables or windows you wish to audit. If you only want some master tables, no setup tables, and a few transaction tables, it is entirely in your control. While the information you obtain for adds and deletes is essentially the same between products, the modifications are much more informative in Auditor. You capture which specific fields changed, as well as the old and new values. Additionally, you can capture notes for users to explain why they made a change. Modifications are the main reason to audit your system. While adds and deletes are useful to track, changing data is what often matters most.

Finally, Auditor has other abilities, such as mapping data in fields to more useful values (like document types, rather than being 1, 2, 3, it is useful to see Quote, Order, Invoice, etc.). Auditor can also audit conditionally, and e-mail specific people when audits occur. Activity Tracking does not have any of these features.

Product:   Conditional Field Level Security
Category: Pre-Sales

If you have experienced Conditional Scripting in a previous version of Great Plains, this product is designed to replace that functionality. If you do not have experience with this product prior to Great Plians 8.0, it probably will not interest you.

Product:   Conditional Field Level Security
Category: Pre-Sales

Microsoft saw Conditional Scripting as a security threat, because users could modify their registration keys by using this product, as well as modify data while bypassing security. However, it is easy for any developer to do this. We do not understand why Microsoft made this decision, as this behavior is not only illegal but unethical, and it has not been a concern with other products before.

Product:   Crystal Integration Archives
Category: Functionality

Crystal Integration is a product designed to launch Crystal Reports directly out of Great Plains Dynamics or eEnterprise. Many businesses using Great Plains tap into the reporting power of Crystal Reports. Before Crystal Integration, users had to launch separate reports outside of the Dynamics or eEnterprise environment. Now, users can launch Crystal reports from within Dynamics or eEnterprise. To the user, the integration is seamless -- which means they needless training or awareness of Crystal Reports because the reports appear to be part of the accounting system.

Product:   Crystal Integration Archives
Category: Functionality

No. Crystal Integration launches Crystal Reports, it does not replace existing Great Plains reports. However, Crystal Integration allows you to launch a Crystal Report directly from within the Dynamics interface. For example, if you have a SOP invoice written in Crystal Reports, you can launch the report directly from the Dynamics SOP Entry screen (or anywhere else for that matter).

Product:   Crystal Integration Archives
Category: Pre-Sales

The Crystal Reports that a company uses must be authored or obtained by that company or one of its designees. Rockton Software can also author reports as a separate consulting engagement. Often, most Great Plains resellers have consultants who are trained to write Crystal Reports.

Product:   Crystal Integration Archives
Category: Troubleshooting

It is important to read and follow the installation instructions included with Crystal Integration (see the file CrystalIntegration.pdf). Often, this error occurs because pathnames have not been set up correctly. Set up the system and company pathnames as documented, and then relaunch Dynamics/eEnterprise and try the installation again.

Product:   Crystal Integration Archives
Category: Setup

While newer versions of Crystal Reports have the ability to use a single parameter to accept a range of values, Crystal Integration can not use these parameter types. If you wish to use a range, you must use two separate parameters. While it is slightly more work for setting up, the end user still has to specify the same amount of data, so the result is the same.

Product:   Crystal Integration Archives
Category: Troubleshooting

This error occurs when the Crystal Report is not connecting to the ODBC data source specified in the report. Make sure this workstation has an ODBC connection set up identical to the one saved with the report. Also, make sure the report does not have the "Save Data With Report" option checked (under the File menu in Crystal Report Designer).

Product:   Crystal Integration Archives
Category: Troubleshooting

In some SQL systems, you may receive an error during installation regarding the pass-through SQL connection. This occurs in some instances when the Great Plains ODBC connection is not set up correctly. If this occurs, check that your ODBC connection has "Use ANSI Quoted Identifiers" unchecked. If this does not fix the problem, and you are using MSSQL Server 7.0 or 2000, run Grant70.sql (from Microsoft) against the company and DYNAMICS databases using SQL Query Analyzer. Also, please contact Rockton Software, as we are working with Great Plains to understand what causes this random error.

Product:   Crystal Integration Archives
Category: Troubleshooting

This error occurs when the parameters in the report do not match the setup in Crystal Integration. Open the report and count the number of parameters, and note their data types (string, date, boolean, etc.) in order. Then, in Crystal Integration Report Maintenance, make sure you have the same number of parameters set up and that the data types match. If you are using a SQL stored procedure, the SQL stored procedure parameter count must also match, as well as the data types.

Product:   Crystal Integration Archives
Category: Troubleshooting

Let’s face it, setting up Crystal Reports in a network environment can be frustrating. Working with Crystal can be frustrating too. But once you get it to work, it’s a beautiful thing. This is the recommended troubleshooting checklist that works 99% of the time. If you follow this list and are unable to produce results, then contact us for support.

1. Start at a workstation that has Crystal Reports and Crystal Integration both installed.
2. Open up the report in Crystal Reports. Preview the report with actual data you know is in your Great Plains system. Check that the ODBC connection is correctly set up, and that you are using an ODBC connection which is separate from the Great Plains login. Make sure the "Save Data With Report" option (under the File menu) is unchecked. Save the report, and note where on the network you saved it.
3. In Crystal Integration, look at the system settings (Reports >> Crystal Reports >>System Setup). Make sure the physical path is indeed the path you just saved the bove report to.
4. In Crystal Integration, open the report in Report Maintenance (Reports >> Crystal Reports >>Report Maintenance). Verify the report physical name is the name you saved above. Also check that the parameters set up in Crystal Integration match the report definition. For testing purposes, choose the "Ask Each Time" option.
5. In Crystal Integration, select the report you set up (Reports >> Crystal Reports >>Print Reports). Enter the SAME parameters you used above. Print the report to screen. It should print.
6. Now go to a different workstation that has Crystal Integration installed, but does NOT have Crystal Reports installed. Try step 5 again. If you have problems at this workstation, the most likely cause is that the ODBC connection is not set up on this workstation identical to the setup on the first workstation. Also, make sure you are able to map to the network drive specified in step 3.

Product:   Crystal Integration Archives
Category: Functionality

Web reporting does not use the security features. It passes a URL to the Crystal Web Server with the report name and parameters exposed. To implement security for web-based Crystal Reports, you may need to write your own custom web pages with built-in security or pursue a different product. We do not plan to further the security model of Crystal Integration with web reports. However, for internal Great Plains reporting, printing a report to the web is an excellent feature because it does not tie up the Great Plains user session.

Product:   Version Pro
Category: Functionality

Version Pro has an optional log setting available that the system administrator can use to log errors at workstations. The log can be viewed by the system administrator at any time.

Product:   Version Pro
Category: Functionality

Absolutely. This is one of the powerful features of Version Pro, because users who are using the wrong products or versions can cause data corruption.

Product:   SmartFill
Category: Pre-Sales

Yes, SmartFill will replace Lookup Plus and Lookup Pro. There will be a transition time in the Spring and Summer of 2005 to bring awareness of this new product to our existing customers. Customers who have purchased Lookup Pro before May 31, 2005 will receive the full upgrade to SmartFill an no additional cost, provided they are on a current Annual Maintenance Agreement. Through May 31, 2005, customers can purchase SmartFill at the introductory price of Lookup Pro.

Customers using Lookup Plus can continue to use their existing product. It will be phased out over time. For certain, Lookup Plus will no longer be available on Great Plains version 9.0. We encourage all users of Lookup Plus to consider upgrading to SmartFill for its added functionality. Customers who have downloaded Lookup Plus prior to May 1, 2005 will receive special promotional pricing as we migrate towards SmartFill. Please contact your reseller or our sales team for more information.

Product:   SmartFill
Category: Functionality

Yes, SmartFill works with any other Dexterity-based Great Plains product. It can lookup and auto-fill values from any object. It may need to be initialized, so if you are unable to set up your SmartFill object, contact us and we'll be happy to help.

Product:   SmartFill
Category: Functionality

SmartFill now allows the functionality of Lookup Pro to work ANYWHERE on ANY object. Lookup Pro was limited to just Customers, Vendors, Items, Accounts, and Employees. SmartFill does not have this limitation; it can work with Shipping Methods, Receivables Transactions, or any other primary ID you can think of in Great Plains. It also works with Primary IDs in other products as well, such as jobs in WennSoft's Job Cost or Service Management series.

SmartFill will work anywhere, any way you like, within Great Plains or any third-party Dexterity-based product. For example, if you’d like to find a customer by a zip code, simply type that in and the customer will auto-populate. (If there is more than one customer with that zip code, all will be displayed). If you’d like to find an account, simply type in part of the account name, and forget about memorizing annoying and lengthy account numbers.

Product:   SmartFill
Category: Functionality

Advanced Lookups are a core part of Great Plains, introduced back in version 6.0. These are the standard lookups that have always been part of the core functionality, and are driven by the user clicking on the looking/magnifying glass icon to the right of a key field, such as Customer Number.

The steps are as follows:

1. Optionally enter part of the beginning of the Customer ID in the Customer ID field.
2. Press the Looking Glass icon.
   
3. A new lookup window displays, sorted by Customer ID, with the optionally entered partial Customer ID from step one beginning the sort at the top.
4. Scroll, search, and find the customer desired.
5. Press Select and the Customer ID is returned to the window.

Auto-Fill is a function introduced in Great Plains 7.5 and is now fully functional with almost all key fields in 8.0. This feature "remembers" common entries typed into key fields, and then auto-fills appropriate values as suggestions as you type. At first, the "remembered" listis empty, but grows as you add values. Suppose you have "CAB001" and "CAR001" as values that are "remembered" in your list.

The process would work as follows:

1. Type "C" into the Customer ID field. Immediately "CAB001" will fill into the field, with your cursor between the "C" and the "A". The first portion will be white as typed; the last portion will be reversed black-on-white to let you know it was auto-filled. If you press TAB, the entire value will be typed into the field.
2. Continue typing an "A" into the field. The same value will stay, but the cursor will move between the "A" and the "B".
3. Continue typing an "R" into the field. The field will now change to "CAR001", with the cursor after the "R". You can continue typing additional characters to change the ID, or press TAB to select what is auto-filled.

SmartFill takes an entirely different approach to lookups. We believe that users often don't know the Customer ID, but almost always know the Customer NAME. Therefore, by typing part of the Customer Name into the Customer ID field, the user experiences both an auto-fill and/or a filtered lookup depending on what they type. Suppose a Customer exists with a Customer ID of MAIN001 and a Customer Name of "Main Street Bakery".

The process works as follows:

1. Type "Bakery" into the Customer ID field. Note we are entering the NAME into the ID field.
2. Press TAB. Immediately "Bakery" is replaced with "MAIN001".

The simplicity of SmartFill makes it much easier to use, more intuitive, and extremely efficient. Given the scenario above, additional actions may occur. If there was another customer in the system with a name of "Happy Time Bakery", when the user presses TAB a shortened list of "Main Street Bakery" and "Happy Time Bakery" will appear. Only these two entries will appear, because they are the only two customers that contain "Bakery" in their names. The user can then choose one of the two customers and press the Select Button, and the valuewill be returned to the window and overtype the word "Bakery" with the Customer ID.

Optionally, the user can also type in "Bak" into the ID field, and both these bakeries would be listed, along with any other Customer whose name contains the three sequential letters "Bak".

Product:   SmartFill
Category: Troubleshooting

Microsoft has added a lot of initialization processes to Great Plains 8.0 compared to previous versions. When you start Great Plains, even when the product screen shows up and allows you to interact with the software, it is not fully initialized. If you immediately open a window and SmartFill fails to work in that window, simply closet the window and reopen it. That should solve the issue.

You can also experience faster loading by moving SmartFill to the second position in your Dynamics.set launch file. For information on how to do this, please contact your reseller or reference your Great Plains documentation.

We have brought this issue to the attention of Microsoft and hope they will work towards a quick resolution.

Product:   SmartFill
Category: Setup

When you install SmartFill, it will detect the presence of Lookup Plus or Lookup Pro. If either is found on a workstation, SmartFill will give you the option to automatically uninstall it. Once it uninstalls, you must exit Great Plains and log in again as 'sa' to continue the installation.

Product:   Omni Price
Category: Pre-Sales

Unlike the Extended Pricing module, Omni Price works for both Dynamics GP Standard and Professional.

Product:   Omni Price
Category: Pre-Sales

Unlike the Extended Pricing module, Omni Price works for both Invoicing and Sales Order Processing.

Product:   Omni Price
Category: Functionality

Omni Price is much easier to configure, simpler to maintain and more flexible in its selection options and pricing methods. It also includes very powerful inquiries, reports and transaction logging facilities.

Product:   Omni Price
Category: Functionality

Unlike the Extended Pricing module, Omni Price can use the Markdown field to show a discount. This can be achieved as a Markdown Amount or as a Markdown Percentage. Omni Price can also change the Account used for the Markdown distribution so that the discounts for a particular contract can be tracked in the General Ledger.

Product:   Omni Price
Category: Functionality

Yes, you can either do this by selecting that contract from the Transaction Logging Inquiry, or you can use the Markdown Mode to chose a specific General Ledger account to post the discounts to.

Product:   Omni Price
Category: Functionality

Omni Price can change pricing by altering the Unit Price or adding a Markdown Amount or Percentage. It works on a single line in a transaction basis. It does not add lines or change quantities. This means it cannot do promotions such as "Buy 2, Get 1 free". However, it can easily do price changes which last for a promotional period.

Also because it only works on a single line and does not look other lines in the current transaction or at historical transaction data, it is unable to change a price based on the items (or item classes) purchased on a particular transaction or over an historical period.

Product:   Omni Price
Category: Troubleshooting

Please confirm that the Customer Pricing System is actually activated, go to Cards >> Omni Price >> Setup Omni Price and check "Activate Customer Pricing System".

Product:   Omni Price
Category: Troubleshooting

If the price on the contract is higher than the price specified by the standard Great Plains inventory system, Omni Price will only use the higher price if the "Use Customer Pricing even if Special Price is higher" option under Cards >> Omni Price >> Setup Omni Price is checked.

Product:   Omni Price
Category: Setup

If you need to select Items or Customers which cannot be selected by common factors such as Classes or any other of the 20 available fields, then create an Item Filter or Customer Filter and select a range of Items or Customers by Item Number or Customer ID that includes all the the Items or Customers in your company. Then after inserting the restriction, click on the restriction line and click on the Details button to open the Intra-range selection window. You may now select individual Items or Customers to be included, use the find option to move quickly through the list.

Product:   Omni Price
Category: Troubleshooting

Here are some things to check to ensure that Omni Price is setup correctly: 1) Make sure that the Omni Price dictionary is installed, Omni Price must be installed on a workstation for it to be able to work on that workstation; 2) Go to Omni Price Setup (Cards >> Omni Price >> Omni Price Setup) and check that "Activate Customer Pricing System" is checked, "Do not log details when Customer Pricing System is used" is unchecked and "User Customer Pricing even if Special Price is higher" is checked; 3) Then use the Price Check window and inquiry windows to test your contracts and filters.

Product:   Omni Price
Category: Functionality

From the transaction windows you can press Ctrl-R to recalculate the current transaction line, You can also press Ctrl-T to recalculate the entire Transaction.

Product:   Omni Price
Category: Functionality

From the transaction windows you can press Ctrl-Z to zoom to the Price Check window. This window will show all the valid contracts for the given situation and which one was selected. You can also use the alternate windows to show the Contract ID field.

Product:   Omni Price
Category: Troubleshooting

If there are valid contracts shown in the Price Check window, but none were selected, it could be the "Use Customer Pricing even if Special Price is higher" option in the Omni Price Setup (Cards >> Omni Price >> Setup Omni Price) which is stopping the contract from being selected. This option must be checked if you want to force a Contract ID to be used when the contracted price is more expensive than the price from standard pricing.

Product:   Omni Price
Category: Functionality

Yes, Omni Price has alternate windows to show the Contract ID for the Sales Transaction Entry and Sales Item Detail Entry windows for SOP transactions, the Sales Transaction Inquiry Zoom and Sales Item Detail Inquiry Zoom windows for SOP inquiries, the Invoice Entry and Invoice Item Detail Entry windows for Invoicing transactions, and the Invoice Inquiry and Invoice Item Detail Inquiry windows for Invoicing enquiries.

Product:   Omni Price
Category: Setup

Yes, but only if the original windows is still be used. If the user does not have access to the window or there is already an alternate, modified or modified alternate window in use, Omni Price will not change the security settings.

Product:   Omni Price
Category: Setup

No, the use of the alternate windows is entirely optional. They are only there to provide the ability to see the Contract ID on the window. Omni Price will still be working whether or not the alternate window is in use.

Product:   Omni Price
Category: Troubleshooting

For the Contract ID to be displayed in the alternate windows, Transaction Logging must not be disabled. Please make sure that the "Do not log details when Customer Pricing System is used" option in Omni Price Setup (Cards >> Omni Price >> Setup Omni Price) is not checked.

Product:   Omni Price
Category: Troubleshooting

If you receive a "This item belongs to a class not available to the current Customer, please select another" warning message, this is because the "Restrict by Item Class in SOP" extra Omni Price module being registered but not set up. You can either set it up using the information in the Omni Price User Guide or you can disable it. To disable it please use the Omni Price Control Panel window (Cards >> Omni Price >> Control Panel) to check the "Disable SOP Item Restriction". It would probably be best to make this a system wide setting. If using the Omni Price Customer Pricing core module, there is functionality to only allow items which are on a contract which can provide a similar function to the SOP Item Restriction with more flexibility.

Product:   Omni Price
Category: Setup

There is a hidden Game in Omni Tools and Omni Price called BlackBox. You can get to it from the Details window accessed from the About Omni Tools or About Omni Price windows.

Product:   Omni Tools
Category: Functionality

If the Password is changed on the Setup >> System >> Users window and password expiry is active you will be asked if you wish to force the user to change their password on next login. If you say "yes" to this dialog, the system will change the date recorded as the last password changed date for that user to 01-Jan-1980. This then forces the password to become expired and the user will be forced to change their password on next login. Note that you must enable at least 1 grace login to allow them to change their password after it has expired.

Also there is an Extras Menu option available from the Setup >> System >> Users window. You may select this option from the menu bar to force the user to change their password without having to change the password.

Product:   Omni Tools
Category: Functionality

There is an Extras Menu option available from the Setup >> System >> Users window. You may select this option from the menu bar and change the dates recorded as the last password changed dates to 01-Jan-1980. This then forces the passwords to become expired and the users will be forced to change their password on next login. Note that you must enable at least 1 grace login to allow them to change their password after it has expired.

Product:   Omni Tools
Category: Troubleshooting

The 'sa' user password cannot actually be changed from within Great Plains, it must be changed using the MS SQL Server Enterprise Manager. Therefore it does not make sense for Omni Password to attempt to expire the password when it cannot be changed from Great Plains anyway.

Product:   Omni Tools
Category: Functionality

Normally, if you maintain the passwords from within Great Plains SQL versions, the passwords will be stored on the SQL Server encrypted. This adds the ability to give a user access to the accounting system, but not to the data from any other application. If access is required from another application then the passwords must be maintained via SQL Enterprise manager or some other method. Omni Password now offers the ability to maintain the passwords from within the Great Plains application and store the passwords in the SQL Server without encryption. This means you can have all the facilities of Omni Password AND still be able to use the same password from an external application, such as FRx or Crystal Reports.

Note: The option to store passwords without encryption is not available on v9.0 onwards due to the password security changes made in the core application.

Product:   Omni Tools
Category: Troubleshooting

This option can only take effect when a password is changed after the option has been activated. Omni Password will not update all users' password when the option is turned on. Please change the user's password via Setup >> System >> Users or Setup >> User Preferences >> Password for the encryption to be removed. You can confirm if the encryption has been removed if you can use the same login to connect via SQL Query Analyser.

Note: The option to store passwords without encryption is not available on v9.0 onwards due to the password security changes made in the core application.

Product:   Omni Tools
Category: Troubleshooting

The passwords in the SY_Users_MSTR (SY01400) table will always be encrypted as this is how the table is defined. The bit that is not encrypted is the actual SQL Server passwords stored in the internal SQL Server system. Because the actual SQL Server Password is no longer encrypted, you can use these Login ID's to connect to SQL Server from other applications, such as Crystal Reports, FRx and SQL Query Analyzer.

Note: The option to store passwords without encryption is not available on v9.0 onwards due to the password security changes made in the core application.

Product:   Omni Tools
Category: Functionality

Omni Password can be used to lock users out of a company or the entire system when you need to perform system maintenance. It can also pop up an "impending maintenance shut-down" warning to notify a user who is already logged in. It also offers an Inactivity timeout feature to automatically log inactive users out of the system, without just killing them. This can be very useful on a Citrix system when a user is disconnected.

Product:   Omni Tools
Category: Functionality

As it is not actually possible to track inactivity with Dexterity, Omni Password's Inactivity Timeout feature works by tracking the last time any of a number of common activities have occurred within the system and resetting a last activity date and time counter. Activities such as opening tables and forms, and moving between records on a form will reset the counter. It then uses a periodic background process to check if there has been no activity for longer than the allowed time it will try and exit.

Product:   Omni Tools
Category: Functionality

Omni Password tries to exit by replicating a user's actions to select File >> Exit from the menu. If any dialogs pop up, such as "Do you want to Save, Discard or Cancel", the automatic log out will stop. It is too dangerous to force the log out when a user decision must be made first.

Product:   Omni Tools
Category: Functionality

The Inactivity Timeout feature resets its last activity counters when a Form, Report or Table is opened (trigger on Security global procedure), a table, SQL table or SQL stored procedure is opened or executed (triggers on Pathname, SQLPath, SQLScriptPath global procedures), or when a Window Note or Record Note is checked for (triggers on Check_For_Note and Check_For_Record_Note global procedures). This will pick up most activities within Great Plains and prevent the Inactivity Timeout activating prematurely.

Product:   Omni Tools
Category: Troubleshooting

If the Inactivity Timeout is attempting to exit while a user is in fact not idle, it would be because they are not performing any of the activities the Inactivity Timeout feature is looking for. To resolve this issue, you can either de-activate the Inactivity Timeout feature for the users in question using the Omni Tools Control Panel (Cards >> Omni Tools >> Control Panel) or you could use VBA code to update the counters, such as this:

Dim CompilerApp As New Dynamics.Application
Dim CompilerApp As Object
Dim CompilerMessage As String
Dim CompilerError As Integer
Dim Commands As String

Create link without having reference marked
Set CompilerApp = CreateObject("Dynamics.Application")

Commands = ""
Commands = Commands & "call with name ""WDC_Pathname_PRE"" in dictionary 2054;" & vbCrLf

Execute SanScript
CompilerError = CompilerApp.ExecuteSanscript(Commands, CompilerMessage)
If CompilerError <> 0 Then
MsgBox CompilerMessage
End If

Product:   Omni Tools
Category: Troubleshooting

Omni Password's Inactivity Timeout replicates the user selecting File >> Exit, by creating and executing a small macro file "on-the-fly". This macro tries to select the menu choice for File >> Exit. We have found that a translated runtime may not use the same words ie. "File" and "Exit" and can cause the macro to fail. Version 6.0 and version 7.X builds allow you to use the modifier to change the following messages; 22673 = "File" and 22674 = "Exit. If you change these to match the correct wording for your runtime, the issue will be resolved.

This is no longer an issue on v8.0 onwards due to the change in the menu implementation.

Product:   Omni Tools
Category: Troubleshooting

The Inactivity Timeout uses a small macro file which it creates and executes "on-the-fly" to replicate the user selecting File >> Exit. This macro file was written into the application folder, the latest builds from version 7.50 onwards will now use the current user's temp folder.

If you have denied write permission to the application folder with the earlier builds it can prevent the Inactivity Timeout from exiting as it is unable to create the macro file it needs. The latest builds of version 7.5 onwards will also log the issue or failing to create the macro file, if the WDC_Debug setting in the Dex.ini file is set to LOG.

Product:   Omni Tools
Category: Functionality

The Inactivity Timeout feature relies on the Automatic Check (WDC_Periodic_Check) process to execute on a regular basis. It is this check which will decide if it is time to attempt to exit once the inactivity period has expired. So the time to exit will be between the Inactivity Timeout setting and the Inactivity Timeout setting plus the Automatic Check period. It will be the first Automatic Check that executes after the Inactivity Timeout period is over.

Product:   Omni Tools
Category: Functionality

Omni Password's Inactivity Timeout and System Maintenance Lockout features both with the WDC_Periodic_Check timed background process to allow them to check the status of the system every X minutes. The time is set in the Omni Password Options window. The process runs very fast and will only execute once every few minutes, so no it will not slow your system down.

Product:   Omni Tools
Category: Functionality

Sadly, it is not possible to link to the Windows or Active Directory passwords at this stage. However, it can be a benefit to have an extra password as an additional line of security between the Financial system and the rest of the world.

This is because Omni Password sits on top of the Great Plains password functionality which only supports SQL Authentication.

Product:   Omni Tools
Category: Functionality

Even though this feature has been requested a number of times, it is not technically possible from inside a SQL based application. To deny access after a number of failed attempts we need to be able to store the number of attempts and also store a setting to say whether access is now denied as well as read how many attempts are allowed. To store this information requires access to the SQL data so it can be written to a table, and that is precisely what we don't have access to.

As you can see this is a "Catch - 22" situation, only the SQL Server itself can implement this type of functionality. We believe that SQL Server 2005 will have this ability.

Product:   Omni Tools
Category: Troubleshooting

There are three main reasons for an Omni Password feature not to work: 1) It has not been setup correctly, but as the user interface is very simple, it is fairly unlikely; 2) The Omni Tools dictionary is not installed on all workstations, Omni Password can only work on a workstation when it is actually installed on that workstation; 3) The feature has been disabled for the system, company, user or user and company using the Omni Tools Control Panel (Cards >> Omni Tools >> Control Panel).

Product:   Omni Tools
Category: Functionality

The Great Plains password functionality only works for Microsoft Dynamics GP 9.0 AND SQL Server 2005 AND Windows Server 2003 with Active Directory. If you have all of this, then you can use the GP password functionality. If you have Omni Password active as well, you will need to meet the requirements of both Omni Password and the standard password functionality. Omni Password will strengthen the standard password functionality with its additional password policy options, as well as its Inactivity Timeout and System Maintenance Lockout features.

Note: The option to store passwords without encryption is not available on v9.0 onwards due to the password security changes made in the core application.

Product:   Omni Tools
Category: Troubleshooting

This issue has been resolved in the 02-Feb-2006 builds (and later) of Version 8.0 onwards of Omni Password. Omni Password was not detecting the deletion of the user as it was being performed by a stored procedure rather than from the Great Plains code itself. This situation is now handled and users deleted from this build onwards will be deleted from the Omni Password tables as well. To cleanup old entries in the table you can run the following script:

DELETE A FROM DYNAMICS.DBO.WDC11140 A LEFT JOIN DYNAMICS.DBO.SY01400 B ON B.USERID = A.USERID WHERE B.USERID IS NULL

Product:   Omni Tools
Category: Functionality

The user will need access to the User Preferences window in the Company Series of the Great Plains dictionary and User Password Setup in the System Series of the Great Plains dictionary. You can use Advanced or Standard security to make the changes. Advanced Security can be used to easily check if all users have access by selecting each window in turn in the tree and checking statuses shown against the users and classes.

Product:   Omni Tools
Category: Functionality

Discounting that fact that the Omni Menu user interface is much more powerful and easier to use, Omni Menu will allow the editing of the Great Plains Toolbar and will allow the editing of palettes from Third party products (as long as they follow the standards). Omni Menu can display nested palettes (ie. a palette which opens another palette) in its "By Toolbar" view.

Note: Omni Menu for Version 8.00 only edits the User Defined Palettes provided by Omni Palettes as palettes have been replaced by menus.

Product:   Omni Tools
Category: Setup

Unlike the standard Great Plains palette editor, Omni Menu can be used to add a window belonging to the System Series to any palette or toolbar.

Product:   Omni Tools
Category: Setup

For Omni Menu to be able to edit a Third party palette it must be able to identify the palette form from the Palette series in the Third party dictionary, and find the palette entries in the SY_Palette_MSTR table.

Product:   Omni Tools
Category: Setup

You must find the existing Third party palette entries under By Dictionary >> Great Plains main product. They will be shown as Unknown palettes. You can then use the Attach button to associate these palette entries with the actual Third Party palette's form.

Product:   Omni Tools
Category: Functionality

Due to a additional Product ID field not be in the SY_Palette_MSTR table, it is not possible to identify automatically which entries in the table are associated with which Third Party palette form. You can create this relationship in Omni Menu using the Attach feature. Once the association is created it is used by Omni Menu and Omni Security to access the palette via the "By Toolbar" view.

Product:   Omni Tools
Category: Troubleshooting

You have not attached the palettes and so all your palettes are being entered with the same Palette ID of 0. You must Attach the Third Party palettes to show the existing entries and not add the entries again manually.

Product:   Omni Tools
Category: Functionality

It purely removes any Batch Activity records and resets the Batch Status. It does not repair partially posted transactions, but it will make the batch "Available" again.

Product:   Omni Tools
Category: Functionality

Please do, but Batch Recovery cannot always help as the batch may not have crashed during posting, also it is only available to systems running on SQL Server. In the situations where Batch Recovery cannot help you have the choice of a huge Techknowledge which cause you to lose information, or fix the problem with a single click in Omni Reset.

Product:   Omni Tools
Category: Functionality

Omni Palettes allows two user defined palettes to be setup on a company basis. You can put common tasks for users onto the palette and then make the palette open automatically using the Startup folder in the Shortcut bar.

Product:   Omni Tools
Category: Troubleshooting

Omni Palettes needs to be added to the menu tree, Work Button or Shortcut Bar before they can be used. They can be found as User Defined Palette 1 & 2 under Product: Omni Tools and Series: Palette. Use Omni Menu to add Omni Palettes to the Toolbar or to another palette, or use Setup >> Company >> Palettes to add Omni Palettes to another palette. You may also use the Shortcut Bar (Ver 6.0 and above) to navigate to the User Defined Palettes.

Product:   Omni Tools
Category: Setup

Please use Omni Menu or Setup >> Company >> Palettes to edit the entries of a User Defined Palette.

Product:   Omni Tools
Category: Setup

While the palette is selected, just choose the Edit Palette option from the Palette Menu on the Menu Bar. Alternatively just click on the name to change it.

Product:   Omni Tools
Category: Functionality

The settings for Automatic Login are stored in the DEX.INI file in the WDC_Auto_Login setting.

Product:   Omni Tools
Category: Troubleshooting

Because each workstation will have its own DEX.INI file, the settings stored in the DEX.INI file will be for the current workstation only.

Product:   Omni Tools
Category: Functionality

Yes and No. The password is encrypted so that it cannot be obtained by looking at the DEX.INI file. However, having the workstation log in without asking for a password is a security risk which you are accepting by using the Automatic Login (with password) functionality of Omni Login.

Product:   Omni Tools
Category: Setup

To disable Omni Login when you are unable to login, delete or comment out (with a semicolon) the WDC_Auto_Login setting in the DEX.INI file.

Product:   Omni Tools
Category: Troubleshooting

Microsoft Dynamics GP already remembers the user, and Omni Login will remember the company. This makes logging in much easier.

Product:   Omni Tools
Category: Functionality

Yes there is, especially on a Citrix system as half of the User ID/Password has been supplied. Omni Login can be asked to forget the last user and last company used to avoid this weakness.

Product:   Omni Tools
Category: Setup

You could, but that would cause any other software which attempts to write to the DEX.INI file to fail. Omni Price and Omni Tools store information in the DEX.INI file, as do many Rockton and other 3rd party products.

Product:   Omni Tools
Category: Troubleshooting

You can use the Control Panel to disable this feature. It was added after many users complained of accidentally exiting Great Plains and then having to wait to login again.

Product:   Omni Tools
Category: Pre-Sales

No, Omni Tools was acquired by Rockton Software from Winthrop Dexterity Consultants in August 2006. We have moved this product to a suite-based product and the individual modules are no longer sold independently. Those users with any Omni Tools modules will now receive the additional functionality of other modules at no additional charge.

Product:   Omni Tools
Category: Troubleshooting

One of Omni Notify's features is to include the name of the company you are logged into in the Application Title Bar. Some VBA code may reference the text of this Title Bar and so may fail if it is changed. If you have this issue, please use the Omni Tools Control Panel to turn off this Omni Notify feature on a system wide basis.

Product:   Omni Tools
Category: Troubleshooting

From version 7.00 onwards, you may have Omni Tools and Advanced Security installed on the same system. One of Omni Notify's features is to detect problems with Toolbar and Palette entries and display a warning dialog. If Advanced Security is installed and the "Hide windows on palettes when denied security" option is enabled, the palette entry numbers are altered to allow this functionality to work. If Omni Notify's code runs before the palette number is altered, it will check the incorrect palette entry for is validity.

To ensure this works correctly, Advanced Security must run its code first before Omni Notify does its checks. The order of the products listed in the DYNAMICS.SET launch file controls which application runs first. The latest builds of Omni Tools now have the following warning: "When both Advanced Security and Omni Tools are installed on a system, Advanced Security must appear before Omni Tools in the DYNAMICS.SET launch file. Please alter the launch file and relaunch the application"

To modify the DYNAMICS.SET launch file, right mouse click on it and select edit:

make sure the lines below
  2054
  Omni Toolsare directly below the
  3104
  Advanced Security

lines and that the Omni Tools dictionary pathnames (NOTE: actual paths may differ)
  :C:Dynamics/OMNITOOL.DIC
  :C:Dynamics/OTOO_FRM.DIC
  :C:Dynamics/OTOO_RPT.DIC

are directly below the Advanced Security dictionary pathnames
  :C:Dynamics/ADVSECUR.DIC
  :C:Dynamics/ADVS_FRM.DIC
  :C:Dynamics/ADVS_RPT.DIC

If you have more than one set of dictionary pathnames in your DYNAMICS.SET, please update each set.

Product:   Omni Tools
Category: Functionality

The Control Panel can be used to configure many of the additional features in Omni Tools. Features can be applied to the entire system, a single user, a single company or a specific user and company.

Product:   Omni Tools
Category: Functionality

The Runtime Execute window can be used to enter Dexterity Sanscript code and execute it without requiring the Dexterity Development environment loaded. It can be used to execute scripts supplied by support personnel by cutting and pasting the script into the window and pressing the Execute button Please note that this window is extremely powerful and should only be used by authorised personnel.

Product:   Omni Tools
Category: Functionality

The SQL Execute window offers the ability to execute Transact-SQL queries from within your Great Plains SQL version system without needing additional SQL Administration Utilities loaded. The result set can be displayed as text or as a Listview.

However, one of the best features is that you can use Dexterity Technical names when writing your query and they will automatically be converted into the correct physical name for the field or table prior to execution.

Product:   Omni Tools
Category: Functionality

There is a hidden Game in Omni Tools and Omni Price called BlackBox. You can get to it from the Details window accessed from the About Omni Tools or About Omni Price windows.

Product:   Dynamics Report Manager
Category: Pre-Sales

Yes, Dynamics Report Manager is the next generation of Crystal Integration. All current users of Crystal Integration on active maintenance plans can migrate to Dynamics Report Manager at no additional product cost. Crystal Integration is no longer available or supported.

Product:   Dynamics Report Manager
Category: Pre-Sales

We support Great Plains 8.0 and higher. Dynamics Report Manager will not be available for previous versions of Great Plains.

Product:   Dynamics Report Manager
Category: Pre-Sales

Crystal Reports Versions 9.0 and higher.

Product:   Dynamics Report Manager
Category: Pre-Sales

SQL 2000 and SQL 2005.

Product:   Dynamics Report Manager
Category: Pre-Sales

Crystal Integration was replaced by Dynamics Report Manger in May 2006. We have extensively notified and campaigned all existing customers and resellers to upgrade to Dynamics Report Manager. Crystal Integration is no longer available or supported. However, archived downloads will be available for a short time. Those customers who are current on maintenance for Crystal Integration receive Dynamics Report Manager for no additional charge.

Product:   Dynamics Report Manager
Category: Pre-Sales

No, all users of Crystal Integration on a current maintenance agreement will upgrade to Dynamics Report Manager at no additional charge.

Product:   Dynamics Report Manager
Category: Pre-Sales

Yes. As of December 31, 2006, Crystal Integration is no longer supported, except for minimal support on legacy systems on Crystal Integration for Great Plains versions 7.5 and older. Crystal Integration will not be enhanced or modified further on any platform. Any customer current on their maintenance plan can upgrade from Crystal Integration to DRM at no addtional charge.

Product:   Crystal Integration Archives
Category: Troubleshooting

No. We want all customers to upgrade to Dynamics Report Manager. Crystal Integration is no longer supported.

Product:   Dynamics Report Manager
Category: Setup

Both products are completely separate and share no code or installation between them. You are encouraged to install Dynamics Report Manager parallel to Crystal Integration and make sure all of your reports are running correctly through Dynamics Report Manager before uninstalling Crystal Integration. Additionally, Rockton will provide a special SQL Script to migrate most report setup data from Crystal Integration to Dynamics Report Manager, and will also provide specialized support services for this migration. We plan to begin our focus on the migration for current Crystal Integration customers to Dynamics Report Manager in August of 2006. However, you are welcome to upgrade your system at any time.

Product:   Dynamics Report Manager
Category: Troubleshooting

Configuring the SQL Report Server and launching a report is not the most intuitive thing. It took us a long time to figure it out, so hopefully this explanation will help.

Your Dynamics Report Manager System Settings for the SQL Report Server Virtual Directory needs to be in this format (DRM Report Explorer | Admin View | Admin | System Settings):

http://BOB/ReportServer

Where BOB is the name of the computer/server, and ReportServer is the name of the Report Server. The name ReportServer is the default with SRS installs but can be changed. You can check your admin panel in your SRS setup to see the name of the Report Server by going to Start | Programs | Configuration Tools | Reporting Services Configuration.

What makes this so incredibly quirky is that when a report is launched, the URL we send is not the URL that ends up being displayed. Suppose this report is set up inside DRM with the following Report Technical Name:

/MarkTest2/MyTestReport1

Well, what DRM builds to send to the URL is

http://BOB/ReportServer/MarkTest2/MyTestReport1

and what you see in the URL is

http://bob/ReportServer/Pages/ReportViewer.aspx?/MarkTest2/MyTestReport1

So check your Report Server and try again. If you send the same thing you see in the URL, the report will fail.

Product:   Dynamics Report Manager
Category: Troubleshooting

If you received an "Enter Values" box when printing a Crystal Report to screen, usually after pressing the Refresh button, you may receive an "Enter Values" screen with incomplete graphic images for the OK and Cancel button. Additionally, if you try to type into any fields, you may experience error messages, including "debug" messages to solve the problem. You may have to terminate the application to exit or experience several errors while closing.

The reason for this is due to an error in Business Objects' published merge modules, the components we receive from Business Objects (creator of Crystal Reports) to include in our software that allows them to launch. Earlier versions of their merge modules included this error. We have since updated our installation package with the new merge modules and the problem is now resolved.

To receive the updates to fix this issue on your computer(s), download the latest DRM Launcher for Crystal 11 on our web site. Use the Windows Add/Remove programs to uninstall your current version of the DRM Launcher for Crystal 11, and install this new version. Make sure to install it to the Great Plains installation directory. Repeat on all affected workstations. You will not lose any setup data or report information in your environment by performing these steps.

Product:   General
Category: Uninstalling

The easiest way to uninstall a Rockton product is to remove reference to the product from the Dynamics.set launch file. Consult your reseller for instructions on how to edit the launch file. Details are also available on CustomerSource and PartnerSource. If you need specific details on how to remove the data tables from the database, please contact support. Most products have little impact on disk space so few people delete the back-end tables when uninstalling.

Product:   General
Category: Annual Maintenance Agreement

Having an Annual Maintenance Agreement (AMA) will save you time, money and give access to the latest and greatest of the Rockton Products not to mention, unlimited support!

The Rockton Software Annual Maintenance Agreement provides support and upgrade protection for customers and resellers of all Rockton products. The AMA is required for the first year of all new products purchased, and is optional thereafter. Maintaining the AMA is a sound investment, allowing for technical support, product enhancements, and product upgrades.

With an active AMA plan you have access to our support staff via telephone, fax, email and/or web conference without any additional charges. We are continually adding to and improving our products. With an active AMA plan your company will be able to download, install and enjoy our latest enhancements.

Without an active AMA, no technical support is offered and a customer who upgrades their Great Plains system to the next major version will lose all functionality of their Rockton product, unless they choose to repurchase the product at full price.

  Click here for further details of our Annual Maintenance Agreement.

Product:   Dynamics Report Manager
Category: Troubleshooting

Synopsis: I get an Error 429 ActiveX message when trying to print a report.

Answer: The Error 429 ActiveX message indicates the DRM Crystal report launcher has not been installed on the workstation you are trying to print the report from.

Recommendation:

The DRM Crystal report launcher will need to be installed on each workstation you wish to print reports from. Here are the quick installation steps from the DRM readme download file. The DRM manual includes further detailed installation instructions.

INSTALLING

1. Download and install the DRM Crystal Launcher 11. This is labeled Part 1 of 2. This Installshield package will install the Crystal Components used for launching Crystal reports. It must be installed on every workstation or server where printing will occur. Make SURE you install it to the Great Plains installation directory.

2. Install the latest build, which is labled Part 2 of 2, for your relevant Great Plains edition. Copy the contents of this zip file into your Great Plains directory. The file DRMCI11.exe WILL overwrite the previous version installed from step 1.

3. If there is a Hot Fix of the DRMCI11.exe launcher file, it will be on the web site labeled as a Hot Fix. It is just an update of the DRMCI11.exe file. Copy it last to the Great Plains directory and overwrite the old version.

NOTE: If the above steps do not fix this error message the message may be caused by an old MSVBVM60.dll file. In this case, you will need to do a complete search on the workstation to find all of the MSVBVM60.dll files. Right click on each file to find the most recent file and then override the older MSVBVM60.dll files with the most recent version of the file.

Product:   Dynamics Report Manager
Category: Troubleshooting

Synopsis: I get a GetForeignStringFieldValue message when trying to print a report in DRM. What can I do to resolve this error message?

Answer: The GetForeignStringFieldValue error normally indicates a setup issue with the launch point, which is trying to set a parameter from a window to a report.

Recommendation:

1. Verify the launch point is setup correctly
2. Make sure launch point is not referencing a field from a 3rd party product which is no longer loaded on the Terminal or Main Server.
3. If the launch point is setup correctly we will want to refresh settings by opening the Launch Point Maintenance window and resaving the launch point (Admin View| Launch Point | Select the launch point in question | Edit Launch Point | Click Save).

Product:   Dynamics Report Manager
Category: Troubleshooting

Synopsis: We are getting a DSN %1 is missing message in DRM when printing a report. What can I do to resolve this error message?

Answer: This error message typically indicates the report is not connecting to the database correctly.

Recommendation:

1. The ODBC DSN setup and test it to make sure it tests successfully. Please note the DSN must be setup using GP requirements. The ANSI settings must be unmarked.

2. In DRM check the global settings to verify the DSN, username and password information is entered correctly (Admin View | Global Report Defaults).

3. Check the Connections tab for the specific report to make sure the DSN, username and password information is correct here as well (Admin View | Reports | Select the report | Click on the Connection tab).

Product:   Dynamics Report Manager
Category: Troubleshooting

Synopsis: When trying to print a report in DRM I'm getting a "Record Not Found" error message. What can I do to resolve this message?

Answer: This error message typically indicates the report is not connecting to the database correctly.

Recommendation:

1. Check to see if you are getting the same error message when printing the report directly in Crystal Reports. When printing the report in Crystal Reports verify you are using the same DSN, Username and Password you have entered in DRM. If you are getting the same error message you will need to correct it within Crystal Reports.

2. You may also want to Verify Database in the report, or set the DSN in the report to a brand new DSN to flush out any connectivity problems.

3. Verify the DSN, Username and Password you are using are correct in DRM. To check the global settings go to Admin View | Global Report Defaults. To check the specific report go to Admin View | Reports | Select the report | Click on the Connection tab.

Product:   Dynamics Report Manager
Category: Troubleshooting

Synopsis: I'm getting "An open operation on table DRM_User_Favorites_VIEW failed accessing SQL data" error message when trying to print a report.

Answer: The ANSI settings in the ODBC DSN connection are marked and they will need to be unmarked.

Recommendation:

1. Check your DSN connection you are using for Great Plains.
2. Unmark the ANSI settings.
3. Exit Great Plains
4. Log back into Great Plains and use DRM to print the report again

NOTE: Your DSN has to be set up per GP specifications or you will get this error message.

Product:   Dynamics Report Manager
Category: Troubleshooting

Synopsis: We have some user stating sometimes their DRM reports disappear from the Extras menu. Why is this happening?

Answer: It is possible that people are logging into Great Plains and opening windows before DRM has had a chance to fully initialize. Great Plains will need to initialize fully before a user can access their DRM Extras menus. This is usually indicated by the username and company. name in the upper left turning from grey to black.

During the initialization process Great Plains is loading all the products listed in the Dynamics.set file. You can move your DRM references in the Dynamics.set file up in the list as well, which will make them load sooner. However, because the initialization process is a feature of Great Plains users will need to allow Great Plains to fully initialize before trying to access the Extra's menu.

Anytime a user is in a screen where a report does not appear, have them close just that window and re-open it, and it should appear again.

Product:   Dynamics Report Manager
Category: Troubleshooting

This error message indicates a connection issue.

Recommendations;

1. Verify your DSN is set up with a SQL Server driver instead of SQL Native Client driver.

2. If the Override Report Credentials option is being used in the Dynamics Report Manager Global Reports Defaults window check to see if the Crystal Report connection was created using a SQL direct connection. If the report was created using a Trusted Connection it will need to be updated to use a SQL direct connections.
a. Open the report you are working with in Crystal Reports
b. Go to Database |Set Datasource Location
c Click to expand the properties

If you see Trusted Connection:1 listed under properties this indicates the connection was created using a Trusted Connection.

To change the connection double click on Trusted Connection and change it to Trusted Connection:0. After updating the connection make sure to Verify Database or reconnect to the SQL data source within Crystal Reports before printing the report using DRM

3. Test the ODBC DSN connection to make sure it is testing successfully.

4. Verify the DSN, username and password information in the Global Report Default settings is correct (Admin View |Global Report Defaults | Listed under Crystal Global Connections Settings).

5. If you have chosen to override the Global Report Default connection settings, verify the DSN settings for the specific report. Under Admin View, select this report and open the Connections tab. Verify the DSN, username and password information is correct here as well. Note if the Override Global Connections checkbox is unmarked then disregard this step.

6. If the report was created using a SQL commands in Crystal Reports make sure it is pointing to the correct database.

7. This error message could also indicate the reports were created on a Crystal Reports version prior to version 9.0. Reports created on Crystal Reports version 8.5 will not work in CI or DRM. If the reports were created on an earlier version of Crystal Reports they will need to be resaved in a more resent version. Please contact our technical support staff for further questions regarding this item.

Product:   Dynamics Report Manager
Category: Setup

DRM doesn't have to be installed on each workstation. DRM only needs to be installed on the workstations where you wish to launch reports from.

Product:   Dynamics Report Manager
Category: Setup

Synopsis: How can a user who has not installed Microsoft Dynamics Great Plains use DRM to launch reports from their workstation?

Answer: A DRM Desktop Shortcut Launch Point can be created to accomplish this.

Recommendation: 1. Create a "dummy" Great Plains (GP) folder on the user's workstation.

2. Install the Dynamics Report Launcher (DRMCI11.exe) in the GP folder created in Step 1.
NOTE:The Dynamics Report Launcher will need to be installed on all workstations you wish to use DRM to launch reports from.

3. Create a Desktop Shortcut Launch Point from a workstation which has GP installed. a. Under the Admin View in DRM select Launch Points b. Click on New Launch Point c. Select Desktop Shortcut as the Launch Point Type, enter a New Launch Point ID and click OK d. Click on the Reports tab and select the report you would like to print.
NOTE Only SQL or Crystal Reports are allowed when creating a Desktop Shortcut Launch Point e. Under the Settings tab click on Create Shortcut and Save

4. Verify the Desktop Shortcut is successfully working.

5. Copy the DesktopShortcutREPORTNAMTE.rsci file, located in the GP application folder, to the "dummy" GP folder created in Step 1.

6. Copy and paste the actual shortcut from the workstation with GP to the workstation without GP installed.

7. Once the shortcut has been copied to the other workstation, right click on it and select Properties to edit the shortcut with the correct Target and Start in information.

8. If the workstation without GP has a different DSN you will need to edit the .rsci file to have the correct DSN information as well. a. Right-click on the .rsci file and select to open with Notepad b. Edit the DSN information and save the file

Example: Below is an example using the information above.

1. Create a dummy GP folder - C:\Program Files\Microsoft Dynamics\GP
2. DRMCI11.exe installed - C:\Program Files\Microsoft Dynamics\GP
3. Launch Point ID - Commissions Report
4. Tested Successfully
5. Copy the DesktopSortcutCommissionsReport.rsci into the dummy GP folder
6. Copy the Commissions Report short cut to the other user's Desktop
7. Edit the shortcut - Target = "C:\Program Files\ Microsoft Dynamics\GP\DRMCI11.exe" " DesktopShortcutCommissionsReport.rsci"

Product:   Dynamics Report Manager
Category: Troubleshooting

Synopsis: When I try to create parameters that allow multiple values, I get an "Invalid Report Definition: Complex Parameter" error message. How do I resolve this error message?

Answer: In DRM build 11 we increased the number of Crystal multi-range parameter values.

Recommendation: Install the latest version of DRM Launcher and DRM.

Verify you have the latest build of DRM Launcher and DRM. Check the DRM Launcher version by right clicking on the DRMCI11.exe file in your Great Plains application directory, select properties and click on the Version tab. Within Great Plains, go to Help About Microsoft Dynamics GP | click on the Extra's menu | Additional | About Dynamics Report Manager to check the version information for DRM.

The most recent version of DRM Launcher and DRM are available on our web site under Products | DRM | Downloads for the most recent build.

Product:   Dynamics Report Manager
Category: Troubleshooting

Synopsis:Error msg: Type mismatch error occurred while you were trying to assign value "to parameter 2, which is a Number datatype."

Answer: This error message may be caused by a blank parameter, older version of DRM or a conflict with Crystal 8.5 dlls.

Recommendation:

1. Check the parameter listed in the error message to make sure a blank value isn't being set. For example, Parameter 2 is a number Data Type and you may be trying to pass a blank value. In this case the error message is being generated because DRM needs to pass a parameter, even if it is zero, and it is blank.

2. Verify you have the latest build of DRM Launcher and DRM. Check the DRM Launcher version by right clicking on the DRMCI11.exe file in your Great Plains application directory, select properties and click on the Version tab. Within Great Plains, go to Help About Microsoft Dynamics GP | click on the Extra's menu | Additional | About Dynamics Report Manager to check the version information for DRM.

The most recent versions of DRM Launcher and DRM are available on our web site under Products | DRM | Downloads for the most recent build.

3. If you are getting this error message and your report only has one parameter and/or you have the latest build of DRM CI and DRM installed then this error may be caused by a conflict with Crystal 8.5 dlls. You will need to make sure Crystal 8.5 dlls not longer exist on the workstations you have DRM loaded on. You can contact us or Business Objects for further instructions on how to manually uninstall the Crystal 8.5 dlls.

Product:   Dynamics Report Manager
Category: Troubleshooting

Synopsis:When trying to print a DRM report I'm getting "The Report Initialization file C:\Program Files\Microsoft Dynamics\GP\DRMREPORTNAME.rsci does not exist. Please try again or contact support. If you are launching this executable directly, this is not a setup file, and is not intended to be launched directly." error message.

Answer: The message is being generated one of the following reasons;
A. You are using a Desktop Shortcut to launch the report and the .rsci file the shortcut is looking for has been deleted, renamed or moved,
B. The user printing the report doesn't have read/write access to the GP application folder,
C. You are double clicking on the DRMCI11.exe file.

NOTE: The DRMCI11.exe is not an install file.

Recommendation:

1. Verify the .rsci, referenced in the error message, exists in the Great Plains application folder.
2. Verify the user has read/write permissions to the Great Plains application folder.
3. Do not double click on the DRMC11.exe file.

Product:   Dynamics Report Manager
Category: Setup

Synopsis: Does Great Plains need to be installed on the workstation I'm using DRM to print reports from?

Answer: Great Plains does not need to be installed in order to use DRM to print reports. Dynamics Report Launcher, however, will need to be installed.

Great Plains will need to be installed on at least one workstation to configure the reports.

Please see the "Steps to print DRM reports from workstations without" FAQ for detailed steps on how to set up the desktop shortcut.

Product:   Dynamics Report Manager
Category: Setup

Launch Point Explanation:
You can create desktop shortcuts to launch Crystal and SQL Reporting Services reports directly from the desktop without having Great Plains open.

NOTE: This option is only available for Crystal and SRS reports, and the parameters cannot be changed at runtime, as they are preset at the time the desktop shortcut is made.

Setup Steps:

1. Log into Great Plains as a user who is set up as a DRM Report Administrator
2. Under the Admin View in DRM select Launch Points
3. Click on New Launch Point
4. Select Desktop Shortcut as the Launch Point Type, enter a New Launch Point ID and click OK.
5. Click on the Reports tab and select the report you would like to print.
6. Under the Settings tab click on Create Shortcut and Save

Example:
The following is an example of how to print a report using a Desktop Shortcut Launch Point.

1. Click on New Launch Point
Launch Point Type = Desktop Shortcut
New Launch Point ID = Commissions Report
2. Reports tab: Click (+) and browse to my Commissions report and click Select
3. Settings tab: Click the Create Shortcut button

Product:   Dynamics Report Manager
Category: Setup

Launch Point Explanation:
Using the Schedule Launch Point you can schedule your reports to launch when you want them, and keep a running calendar of when the next time a given report will launch..

Setup Steps

1. Log into Great Plains as a user who is set up as a DRM Report Administrator
2. Under the Admin View in DRM select Launch Points
3. Click on New Launch Poin
4. Select Schedule Launch as the Launch Point Type, enter a New Launch Point ID and click OK.
5. Under the Settings tab select and enter the Frequency information.
6. Under the Report tab select the report(s) you would like to schedule to print.
7. Under the Reports tab use the add button (+) to add the report(s) you would like to have print from this item on the Extra's Menu.
8. Use the Access tab to setup security restriction
9. Use the Actions tab to additional actions such as, Set Parameter to Field, Launch All Reports, etc.

NOTE: The Schedule Report Monitor window will need to be open in order for the scheduled reports to print. You can also print reports, such as "Missed" reports, directly from the Scheduled Report Monitor window.

Example:
The following is an example of how to schedule a Customer List report to print on the 25th of each month at 3:00am

1. Click on New Launch Point
Launch Point Type = Schedule Launch
New Launch Point ID = Customer List
2. Settings tab: Frequency = Monthly, On the 25th at 3:00am
3. Reports tab: Click (+) and browse to my Customer List report and click Select

Product:   Dynamics Report Manager
Category: Setup

Explanation:
Reports can be launched from the regular shortcut bar using the Shortcut Bar Launch Point option

Setup Steps:

1. Log into Great Plains as a user who is set up as a DRM Report Administrator
2. Under the Admin View in DRM select Launch Points
3. Click on New Launch Point
4. Select Shortcut as the Launch Point Type, enter a New Launch Point ID and click OK.
5. Click on the Reports tab and select the report you would like to print.
6. Under the Settings tab click on Create Shortcut and Save

NOTE: You will need exit and reenter Great Plains in order for the Shortcut Menu to refresh.

Example:
The following is an example of how to add a Commissions report to the Shortcut Bar.

1. Click on New Launch Point
Launch Point Type = Shortcut Bar
New Launch Point ID = Commissions Report
2. Reports tab: Click (+) and browse to my Commissions report and click Select
3. Settings tab: Click the Create Shortcut button

Product:   Dynamics Report Manager
Category: Setup

Launch Point Explanation:
The floating palette is a context-sensitive pick list which can be accessed from the Dynamics Report Manager Toolbar. This palette can be "pinned down" so it does not leave the desktop, and can be moved to any position on the screen where it will remember its placement next time it is opened. This palette provides a list of reports that shrinks and grows as you open and close specific windows, providing a pick list for reports that are relative to what windows you have open at a given time.

Setup Steps:

1. Log into Great Plains as a user who is set up as a DRM Report Administrator
2. Under the Admin View in DRM select Launch Points
3. Click on New Launch Point
4. Select Toolbar Floating Palette as the Launch Point Type, enter a New Launch Point ID and click OK.
5. Under the Settings tab select a Toolbar Options:
a. Always appear on Toolbar Palette, OR
b. Only Appear on Palette when specific form is active
i. Select the Product, Series and Form you would like the report available from.
6. Under the Reports tab use the add button (+) to add the report(s) you would like to have print from this item on the Extra's Menu.
7. Use the Access tab to setup security restrictions
8. Use the Actions tab to additional actions such as, Set Parameter to Field, Launch All Reports, etc.

Example:
The following are examples of how to add a report to Toolbar Floating Palette.

Toolbar Options - Always appear on Toolbar Palette:

1. Click on New Launch Point
Launch Point Type = Toolbar Floating Palette
New Launch Point ID = Sales Report
2. Settings tab: Toolbar Option = Always appear on Toolbar Palette
3. Reports tab: Click (+) and browse to my Customer List report and click Select
4. Access tab: Set security restrictions.
5. Action tab:

Toolbar Options - Only Appear on Palette when specific form is active:

1. Click on New Launch Point
Launch Point Type = Toolbar Floating Palette
New Launch Point ID = Sales Report
2. Settings tab:
Toolbar Option = Only Appear on Palette when specific form is active
Product = Microsoft Dynamics GP
Series = Sales
Form = Customer Maintenance
3. Reports tab:
Click (+) and browse to my Customer List report and click Select
4. Access tab: Set security restrictions.
5. Action tab:

Product:   Dynamics Report Manager
Category: Setup

Launch Point Explanation:
The Window Field or Button Launch Point provides a trigger point, usually from a button on a window, from which to launch a report. The print button on a window is a common example, but you can launch a report from a Posting button or when a user enters a dollar amount in a specific field.

Setup Steps:

1. Log into Great Plains as a user who is set up as a DRM Report Administrator
2. Under the Admin View in DRM select Launch Points
3. Click on New Launch Point
4. Select Window Field or Button as the Launch Point Type, enter a New Launch Point ID and click OK.
5. Under the Settings tab select a;
a. Trigger Type
b. Attach Type
c. Product, Series and a Form
d. Window and/or Field - These fields will be available based on the selection(s) in step C.
6. Under the Reports tab and select the report you would like to print.
7. Use the Access tab to setup security restrictions
8. Use the Actions tab to add additional actions such as, Set Parameter to Field, Launch All Reports, etc

Example:
The following is an example of how to add a Customer List report to the Customer Maintenance window. Step 5 in this example is optional. It has been included in the example to display how to set a parameter in a Launch Point.

1. Click on New Launch Point
Launch Point Type = Window Field or Button
New Launch Point ID = Cust Report Button

2. Settings tab:
Trigger Type = Window Print Menu
Attach Type = Before original Script
Product = Great Plains
Series = Sales
Form = Customer Maintenance
Window = Customer Maintenance
Field = N/A

3. Reports tab:
Click (+) and browse to my Customer List and click Select

4. Access tab: accept default

5. Actions tab:
Click (+)
Action = Set Parameter to Field
Report = Customer List
Parameter = Customer ID
Product = Great Plains
Series = Sales
Form = Customer Maintenance
Window = Customer Maintenance
Field = Customer Number
Click (+)
Action = Launch Specific Report
Report = Customer List

Product:   Dynamics Report Manager
Category: Setup

Launch Point Explanation:
The Windows Extra Menu Launch Point provides a menu item under Extras >> Additional, where users can launch reports from. Windows Extra Menus can appear for any form throughout Great Plains or any 3rd party product.

Setup Steps

1. Log into Great Plains as a user who is set up as a DRM Report Administrator
2. Under the Admin View in DRM select Launch Points
3. Click on New Launch Point
4. Select Window Extra Menu as the Launch Point Type, enter a New Launch Point ID and click OK.
5. Under the Settings tab select the Product, Series and Form.
The report will only be available under the Extra's menu when the form you specified here is open.
6. Under the Reports tab use the add button (+) to add the report(s) you would like to have print from this item on the Extra's Menu.
7. Use the Access tab to setup security restrictions
8. Use the Actions tab to additional actions such as, Set Parameter to Field, Launch All Reports, etc.

Example:
The following is an example of how to add a report to Extra's menu when the Customer Maintenance window is open.

1. Click on New Launch Point
Launch Point Type = Windows Extra Menu
New Launch Point ID = Customer List
2. Settings tab:
Product = Microsoft Dynamics GP
Series = Sales
Form = Customer Maintenance
3. Reports tab:
Click (+) and browse to my Customer List report and click Select

Product:   Omni Price
Category: Setup

Synopsis: Do I really have to install Omni Price on ALL workstations?

Answer: Yes, if you want the full functionality. If you don't install on all workstations, the functionality listed below for the different modules will NOT work on the workstations where the chunk is not installed.

Omni Price - Core Module: All functionality will not work.
Omni Price - Extra Features: All functionality will not work.

Product:   Omni Tools
Category: Setup

Synopsis: Do I really have to install Omni Tools on ALL workstations?

Answer: Yes, if you want the full functionality. If you don't install on all workstations, the functionality listed below for the different modules will NOT work on the workstations where the chunk is not installed.

Omni Password: All functionality will not work.
Omni Menu: Cannot use interface where not installed.
Omni Work: Cannot use interface where not installed.
Omni Reset: Cannot use interface where not installed.
Omni Palettes: All functionality will not work.
Omni Login: All functionality will not work.
Omni Notify: All functionality will not work.

Product:   Omni Tools
Category: Setup

Synopsis: I am trying to install Omni Tools but the Installation window never opened?

Answer: Please install the chunk file again and make sure you select "New Install" when asked. Then log on as 'sa' and complete the installation process.

Please confirm that your DEX.INI is not set as Read Only.

Product:   Omni Price
Category: Setup

Synopsis: I am trying to install Omni Price but the Installation window never opened?

Answer: Please install the chunk file again and make sure you select "New Install" when asked. Then log on as 'sa' and complete the installation process.

Please confirm that your DEX.INI is not set as Read Only.

Product:   Omni Tools
Category: Troubleshooting

Synopsis: I am getting an error referencing the WDC_Registration or WDC_Version_Info tables, what's wrong?

Answer: The installation of Omni Tools on your Great Plains SQL versions system has not been completed. Please install the chunk file again and select "New Install" when asked. Then log on as 'sa' and complete the installation process.

You can also force Omni Tools into Install mode by changing the line in the DEX.INI file to WDC_New_Install2054=TRUE.

Product:   Omni Price
Category: Troubleshooting

Synopsis: I am getting an error referencing the WDC_Registration or WDC_Version_Info tables, what's wrong?

Answer: The installation of Omni Price on your Great Plains SQL versions system has not been completed. Please install the chunk file again and select "New Install" when asked. Then log on as 'sa' and complete the installation process.

You can also force Omni Price into Install mode by changing the line in the DEX.INI file to WDC_New_Install1999=TRUE.

Product:   Omni Tools
Category: Troubleshooting

Synopsis: When logging in with a user other than 'sa', I am getting permission errors referencing the WDC_Registration or WDC_Version_Info tables, what's wrong?

Answer: The installation of Omni Tools on your Great Plains SQL versions system has not been successfully completed. The Automatic Granting code has failed for some reason. Just run the GRANT.SQL or GRANT7.SQL script from the SQL Enterprise Manager Query Analyser.

Your install may be out of date as the issue which may have caused this has been fixed. Please download the latest build located under Products | Omni Tools | Downloads.

Product:   Omni Price
Category: Troubleshooting

Synopsis: When logging in with a user other than 'sa', I am getting permission errors referencing the WDC_Registration or WDC_Version_Info tables, what's wrong?

Answer: The installation of Omni Price on your Great Plains SQL versions system has not been successfully completed. The Automatic Granting code has failed for some reason. Run the GRANT.SQL or GRANT7.SQL script from the SQL Enterprise Manager Query Analyser.

Your install may be out of date as the issue which may have caused this has been fixed. Please download the latest build located under Products | Omni Price | Downloads.

Product:   Omni Tools
Category: Troubleshooting

Synopsis: Why do I keep getting asked to login as 'sa' to complete installation?

Answer: This can occur if the installation of Omni Tools has not successfully completed. It can also be caused by installing mixed builds of Omni Tools. If you are installing a new build of Omni Tools, please make sure that all workstations have the same dictionary installed. The dictionary can be copied from one workstation to another after the initial installation.

Product:   Omni Price
Category: Troubleshooting

Synopsis: Why do I keep getting asked to login as 'sa' to complete installation?

Answer: This can occur if the installation of Omni Price has not successfully completed. It can also be caused by installing mixed builds of Omni Price. If you are installing a new build of Omni Price, p