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.

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.

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 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 series of JOINs to several different tables, you could use this stored procedure to do it.

If you do use this stored procedure, you will also have to set the search type to Custom SQL on the Object Maintenance window in SmartFill.

This is a modification you can make to the Repository to get around this problem:

1. Close the Purchase Order Entry window.
2. Go To Tools > Setup > System > SmartFill Repository.
3. Select Vendors in the Objects drop-down.
4. Now search thru the list for the Repository entry for the Vendor ID field on the POP_PO_Entry form/window. Select this record; then click the Modify button on the right.
5. On the Modify Repository Record dialog, click the "Skip running change script for this field" box and click OK.
6. Click OK to close the Repository Maintenance window.

Now open the Purchase Order Entry window and try it again. This time it should bring back the vendor, but the Vendor ID field will still be editable, as if you just entered it manually. Tab off the field and it should now behave normally. You should only have to make this change once, from one workstation, and it should correct the problem for all workstations.

You can use the Lookup Creation Wizard to add SmartFill functionality to current objects.  Go to Tools | Setup | SmartFill | Repository | New to open the Lookup Creation Wizard.  The Wizard will walk you through updating the Repository with additional fields.  The Wizard allows you to browse to the specific window and field to which you would like to add SmartFill functionality.

Example: The following steps outline how to add SmartFill functionality to the Vendor ID field in the Return Transaction Entry window.

1. Tools | Setup | SmartFill | Repository | New and click Next
2. Select the Vendor Object and click Next
3. Browse to the Return Transaction Entry window and place your cursor in the Vendor ID field (Transactions | Purchasing | Return Transaction Entry)

4. Click Add Lookup
5. Click Finish in the Lookup Creation Wizard window to save your changes.

Yes.  You can also use the new Field Mapping feature in SmartFill to accomplish this. 

Field Mapping is available only for table fields (i.e., it is not available for constant
values). The only types of fields that can be mapped are ones that have a string
datatype, or a numeric datatype that is not a Currency type. For instance, Integers and
Drop-down List fields can use Field Mapping; Date fields and Currency fields cannot.

This error message is indicating there is a link missing in the Secondary Table setup of the Address Object. 

Recommended Steps:
1. Log into GP as sa
2. Go to Tools | Setup | SmartFill | Objects
3. Select to Edit the Address Object
4. Click on the blue arrow in the right of the Table Name field.  This will open the SmartFill Object Secondary Tables window.
5. Highlight the RM_Customer_MSTR table and click on the plus symbol under the Links section.
6. Under the Primary Table Field section select the Customer Number
7. Under the Secondary Table Field section select the Customer Number
8. Click Link, Ok and Ok to Save the changes and close the SmartFill windows.

Steps:

1.  Open SmartFill objects
2.  Open customer object
3.  Click the blue arrow to the right of Table Name field
4.  Under Secondary Tables, click Plus+ to add new table
5.  Product: MS dynamics GP
6.  Series: Sales
7.  Choose RM _CUSTOMER_MSTR_SUM table, click on Select
8.  Fields (left side) select customer Number | Fields (right side) select Customer Number
9.  Click the Link button
10. Click on OK
11. Choose next available line in the Lookup Fields area
12. Choose Table RM_Customer_MSTR_SUM from the down arrow and Customer Balance from Field Name down arrow 13. Check the box to Display.
14. Adjust your width to equal a total of 100%

Typically this error comes from either the SmartFill version being different than your GP version, or the creation of a custom Object that was done incorrectly.

Recommendations:

1.  Ensure you have the same version of SmartFill and latest build that  matches your GP version.
2.  Create a new SmartFill Object by going to Tools | Setup | SmartFill | Objects.
3.  Click on New.
4.  Fill out all the fields correctly.

Extender is a set of generic windows and fields.  Suppose you used Extender to create two objects with forms, such as Vehicles and Drivers.

Whenever you open an Extender window, you open Window1, and it re-arranges and aligns Field1 to Field25.  If you open what you defined as Vehicles first, it will open in Extender’s Window1.  If you then open Drivers, you will get Window2.  Now close all the windows.  If you open Drivers, you get that in Window1, and opening Vehicles would get you Window2.

SmartFill has to get assigned in the Repository to a specific GP Window.  So suppose you choose Extender’s Window1.  Well, if you do a Vehicle Lookup against that window, and you open the Drivers object through Extender, the lookup for Vehicles will work in the Drivers window, which would be confusing.

So you can use SmartFill when you have a simple use for Extender, and it will work in most cases if you have, say, just Vehicles and nothing else.  That’s because you’ll only be opening Window1 with Vehicles each time in practical usage. 

If you have a simple Extender setup, then you would have to determine which windows to set SmartFill against.

To disable SmartFill functionality in a window field:

1. Go to Tools>Setup>SmartFill>Repository
2. In the Repository Maintenance window, choose the Product that contains the window where you want to disable SmartFill
3. In the Repository Maintenance window choose the Object that contains the field you want to disable (e.g. Addresses) from the drop down list
4. Find the field you want to disable in the Repository list and select it
5. Click on the Delete button (the red X icon just above and to the right of the list area of the window)
6. Click OK to close the Repository window

To re-enable SmartFill functionality in a window field

1. Go to Tools>Setup>SmartFill>Repository
2. In the Repository Maintenance window, choose the Product that contains the window where you want to re-enable SmartFill
3. In the Repository Maintenance window choose the Object that contains the field you want to re-enable (e.g. Addresses) from the drop down list
4. Click the Add button (the plus symbol (+) icon just above and to the right of the list area of the window)
5. Go through the Lookup Creation Wizard
6. Click OK to close the Repository window

You can temporarily disable SmartFill by typing something on any window that is not an exact match, so that you get the Select Record window. Click the Temporary Disable button at the bottom. You can choose to temporarily disable Just this time or For this window.

The temporarily disable SmartFill function disables SmartFill for just the User that has disabled it. No other Users are affected. Also, the disable functionality only occurs while the window is open. Once the window is closed. then SmartFill is automatically enabled again for that user and that window.

You are getting this message because you are using Custom SQL for one of your SmartFill objects and the stored procedure spSmartFill does not exist in the new company’s database. You can simply copy this stored procedure from an existing company database to the new one and that will give you the same functionality for that object in the new company. 

You may need to also grant Execute permission to this stored procedure. You can do this by running the following SQL script:

GRANT EXECUTE ON spSmartFill TO DYNGRP

There have been a few issues when using Integration Manager while SmartFill is enabled. We recommend you disable SmartFill during the integration. Once the integration is complete, you can enable SmartFill again.

To disable SmartFill go to GP Tools>>Customize>>Customization Status. Locate the Product SmartFill and click on the Disable button.

To enable SmartFill go to GP Tools>>Customize>>Customization Status. Locate the Product SmartFill and click on the Enable button.

When SmartFill is installed, all of the windows that an average User needs to use the product are automatically included in the DEFAULTUSER Security Task.  Therefore, a user must be assigned to at least one Security Role that contains the DEFAULTUSER Task in order to access all of the "normal" GP windows that SmartFill requires to work. Check the User's Security settings to ensure the User is assigned to at least one Role with the DEFAULTUSER Task.

Note that even if a User is assigned to the SMARTFILL ADMIN Role, they must also be assigned to a DEFAULTUSER role.

This issue was resolved in the latest builds of SmartFill. Upgrade to the latest build of SmartFill, or edit the spSmartFill.sql stored procedure file for each of your company databases as follows:

Here’s what the top part of the stored procedure may look like now:

CREATE PROC spSmartFill
                @SmartFillObjectID INT,
                @UserID CHAR(15),
                @CompanyID INT,
                @SearchValue CHAR(50)
AS
DECLARE @SmartFillObjectName CHAR(50)

Make the following changes (changed lines are in bold):

CREATE PROC spSmartFill
                @SmartFillObjectID INT,
                @UserID CHAR(15),
                @CompanyID INT,
                @SearchValue CHAR(50),
                @SearchValue2 CHAR(50),
                @SearchValue3 CHAR(50),
                @SearchValue4 CHAR(50),
                @SearchValue5 CHAR(50),
                @SearchValue6 CHAR(50),
                @SearchValue7 CHAR(50),
                @SearchValue8 CHAR(50),
                @SearchValue9 CHAR(50)
AS
DECLARE @SmartFillObjectName CHAR(50)

By default, when the calendar is installed per user it is defined to use the F2 accelerator key to operate. This message indicates that the F2 key is already assigned to something else, so you will need to define the calendar to use a different accelerator key. To modify which accelerator key you wish to use, please follow these steps.

Steps:

1.  Right mouse click on the Calendar item on the Navigation Pane.
2.  Select Shortcut Properties.
3.  Modify the Keyboard Shortcut to your liking.

You can grant or remove access to companies and users by opening each SmartFill Object. At the bottom of each Object screen you’ll see an Access button. Click on it to open the access window where you can set the access for that Object. You’ll want to do this for each of the Objects where you want companies or users to have access.

This error typically indicates that the field referenced in the Repository no longer exists. For example, the Account Number field on the GL_Account_Maintenance window was renamed to Account Number CS. The new name is not recognized by the Repository and therefore, does not exist. This commonly happens when there have been fields removed from a form in the GP dictionary from one release to another, but our Repository entries still refer to the fields in the old version of the form.

Recommendation:

Update the Repository by deleting the obsolete fields and adding the new fields.

This is a current issue with SmartFill that we have recently discovered. This error indicates there are two objects with the Vendor ID for example, in the repository.  In other words, the Vendor ID for the Vendor Maintenance window is listed in the Repository for the Vendor object and the newly added Multi-Facility Vendor's object.

Please check to see which one of the two Objects you need.  If you are not using Multi-Facility then you can delete the Multi-Facility Vendors, Multi-Facility Customers, Multi-Facility Employees and Multi-Facility Items objects from the Object setup window. If you are using Multi-Facility, then you can delete the Vendors, Customers, Employees and Items objects instead.

Basically, the same field/window/form combination cannot be list in the repository under multiple objects.  So it has to be removed from one of the objects in order to work correctly and without error.

After you have removed the appropriate Object(s), exit out of GP and then re-launch GP.
Everything should now work correctly.

If you get an "Unable to find a table" error during the unchunking process, it is likely caused by the runtime engine not having write access to the application folder.  The probable cause for this on the new versions of Windows is User Access Control (UAC). UAC will block write access to the C:\Program Files folder to prevent malicious software installing itself. 

Recommendation:

You will need to use the Run As Administrator option once, to allow the code to be included. The other alternative is to disable UAC, but this will cause the system to be less secure.