Features are not returned by the search function in the ArcGIS for Local Government Park and Recreation Finder

Description

No features are returned by the search function in the ArcGIS for Local Government Park and Recreation Finder when the FacilitySitePoint feature class and ParkRecInfo table are stored in an SDE database.

Cause

This is a known issue related to NIM086322.

Workaround

1. Open Parks.mxd
2. Right-click the Parks and Recreation Areas layer in the Table of Contents window and choose Properties.
3. On the Joins & Relates tab, verify the ParkRecInfo table is joined to the FacilitySitePoint feature class using the FACILITYID field. Click OK to return to the map
4. Right-click the Parks and Recreation Areas layer in the Table of Contents window. Click Data > Export Data.
   
   Use the following inputs:
   • Export: All features
   • Coordinate System: this layer’s source data
   • Specify a name for the new feature class and where it is to be stored.
   
   Click OK.
5. Add the newly created feature class to the map as a layer.
6. Right-click the new layer in the Table of Contents window and choose Properties.
7. On the Symbology tab, click the Import button and choose the Parks and Recreation Areas layer. Click OK to return to the map.
8. Right-click the original Parks and Recreation Areas layer in the Table of Contents window and choose Remove.
9. Click the List By Source button in the Table of Contents window and remove the ParkRecInfo table from the map.
10. Rename the remaining layer Parks and Recreation Areas.
11. Save and close the map document, then restart the Parks map service.
    
12. Using Windows Explorer, navigate to the Parks Finder application files and open the configuration file (config.txt) in a text editor.
13. Remove any reference to FacilitySitePoint. and ParkRecInfo. including the period (.) from the configuration file.
    
    Twenty lines of code should be modified in total.
    
    Example:
    

    {"FieldName":"FacilitySitePoint.NAME","Alias":"Name of Facility"}

    
    Becomes:
    

    {"FieldName":"NAME","Alias":"Name of Facility"}

    
    
14. Save and close the configuration file.
15. Follow any additional configuration and publishing steps for the application that have not already been completed.