Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#237 closed defect (invalid)

Search.php results showing improper nulls

Reported by: amorsell Owned by: waltweltonlair
Priority: P2 Milestone: 2.0
Component: Widgets Version: 1.1.1
Severity: Major Keywords:
Cc: Browser: All
External ID: 1015380 Operating System: All
state: New


The search widget is returning null values for valid fields in some instances. The best way to see this is to load the package that can be found here:

The isNull fix needs to be in place from ticket 236 before effectively trying this scenario (you can also use this package to see that error before implementing it). Open the flexible layout in a browser. Go to Search by Owner under Parcel Search. Search by a last name of "Jones". Notice that the second result of JONES, EILEEN shows no parcel ID value. Click on the result to zoom to it. Notice in the property pane that there is indeed a valid parcel ID. Now, use that parcel ID of 39101.9035 in the Search by Parcel ID search instead. It will report that there are no matches.

Change History (4)

comment:1 by amorsell, 15 years ago

Milestone: Future2.0

comment:2 by waltweltonlair, 15 years ago

External ID: 1015380
Owner: changed from madair to waltweltonlair

comment:3 by waltweltonlair, 15 years ago

Resolution: invalid
Status: newclosed

There's no defect here. The parcels data set in the attached package contains two attribute columns containing IDs: PID and PARCEL_NUM. Some rows have a value for PID but not a value for PARCEL_NUM. For example, the row for JONES, EILEEN has a PID value of 39101.9035, but its PARCEL_NUM value is empty / null / missing. When the parcel is select the Properties UI displays the PID attribute. But 'Search by Parcel ID' uses PARCEL_NUM, so of course it won't find 39101.9035. Also 'Search by Owner' displays PARCEL_NUM in its Parcel ID column, and not PID. If the Search tasks are changed to use PID and not PARCEL_NUM then everything is consistent.

comment:4 by amorsell, 15 years ago

Thank you for catching my mistake. I apologize for the oversight.

Note: See TracTickets for help on using tickets.