Error: A get/change operation on table HR_orientation_V2 failed. A record was already locked.
On the Orientation Checklist window, once an employee ID is entered if you check a checkbox in the list it produces Error: ‘A get/change operation on table ‘HR_orientation_V2′ failed. A record was already locked.’ This is a known bug. The current workaround is as follows: In SmartFill, please open the Repository Maintenance window. Do a
Languages supported in SmartFill
Subject: Describes whether Smartfill will works with other languages. Information: Yes. SmartFill will work with other country codes such as Spanish because the stored data it is pulling would be in Spanish. However, SmartFill window labels would still display in English (i.e., Select Record).
Error: You cannot change vendors on a document. To change vendors, delete the transaction and re-enter a new document
Error: You receive the following message in the Purchase Order Entry window after tabbing off the Vendor ID field. You cannot change vendors on a document. To change vendors, delete the transaction and re-enter a new document. Or You can’t change vendors on a document. To change the vendor, delete the current document and enter
Decimals do not show correctly in the SmartFill Make a Selection
Issue: When numerical values are used in SmartFill, decimals do not show correctly in the Make a Selection window. Cause: SmartFill was not designed to display decimals in the Make a Selection window. Resolution: You may use a SmartFill Custom SQL Object to display the decimal places in the window. For more information on Custom
SmartFill randomly stops working in Dynamics GP 8.0 or newer versions.
Issue: After launching Dynamics GP 8.0 or newer versions, you notice that SmartFill randomly stops working. Recommendations: Microsoft has added a lot of initialization processes to Dynamics GP 8.0 when compared to previous versions. When you start Dynamics GP, even when the product screen shows up and allows you to interact with the software, it is
Why doesn't Smartfill work in the Account Maintenance window on Great Plains 10.0 ?
Why doesn’t Smartfill work in the Account Maintenance window on Great Plains 10.0 ? The problem is due to a known GP Quality Report, which has been addressed with the GP Hotfix. The tabbing from the last segment of the account number field does not move focus on to the next field in the tab
What is the difference between SmartFill and Lookup Pro?
What is the difference between SmartFill and Lookup Pro? 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
SmartFill spSmartFill.sql File
Subject: Describes what the spSmartFill.sql file included with SmartFill is used for. More Information: The spSmartFill.sql file is a template for a SQL Stored Procedure that can be used to add functionality to your lookups that could not otherwise be done through the SmartFill windows. For instance, if you want to search using a complex
Error: Unhandled database exception: A get/change first operation on table ‘SF_Object_MSTR_OLD’ failed accessing SQL data. Number of results columns doesnt match table definition
Error: When upgrading from Dynamics GP 10 to Dynamics GP 2013, the following error appears: Unhandled database exception: A get/change first operation on table ‘SF_Object_MSTR_OLD’ failed accessing SQL data. Number of results columns doesnt match table definition. Cause: There are some table columns changes between Dynamics GP 10.0 and Dynamics GP 2013 in SmartFill. This
Error: Unhandled script exception: [Microsoft][ODBC SQL Server Driver][SQL Server] Could not find stored procedure Name.dbo.spSmartFill'. error
Why are we getting an Unhandled script exception: [Microsoft][ODBC SQL Server Driver][SQL Server] Could not find stored procedure Name.dbo.spSmartFill’. error when we try to do lookups after creating a new company? You are getting this message because you are using Custom SQL for one of your SmartFill objects and the stored procedure spSmartFill does not
Back to Top