nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Search widget results not showing up in 3.1 attribute table

JasonHarshman

I've checked the box for "Add results as operational layer", and as expected, the results from a search are shown in the legend, layer list, and a tab is added for the results layer in the attribute table. However, the attribute table is blank with no records or fields. The results in the search widget are visible and there parcels selected. I've attached a screenshot to help illustrating what I'm experiencing.

[ATTACH=CONFIG]20817[/ATTACH]

Capture.jpg

3z7a6281.jpg

Najděte více příspěvků označených jako

Accepted answers

All comments

AntGiles

Jason,

Are you using a modified search widget as I have not seen any option to add your results as an operational layer.

Also the attribute table widget and the search widget work independent of each other

Regards

Anthony

JasonHarshman

Anthony,

I'm using the out-of-the box search widget. When you edit the widget in the builder, there's an check box option on the bottom to make results an operational layer.

AntGiles

Jason,

Are you talking about configuring the attribute table widget in the application builder and not the search widget. If so:

"the Attribute Table widget checks for any feature layer feature(s) in the current extent and populates the attribute table with its feature(s)."

This widget is independent of the search widget, so is your search widget searching against a dynamic layer or a feature layer?

Regards

Anthony

JasonHarshman

The check box I referred to is for the search widget. I haven't done anything to configure the attribute table other than turn it on using the builder. But because I've selected the option for my search results to become an operational layer, the attribute table appears to look for this search result operational layer and based on your statement, "the Attribute Table widget checks for any feature layer feature(s) in the current extent and populates the attribute table with its feature(s)." This statement proves true because a new tab shows up in the attribute table for my search results, but like I've mentioned, no data is populated.

RhettZufelt

don't know if the selection is supposed to pass to the attribute table or not.

Just wanted to check and make sure you are using SDE and have published your service as a FeatureService.

The attribute table widget requires a featureservice (not just mapservice loaded as type="feature") in order to populate.

See here for more info:

http://forums.arcgis.com/threads/73842-New-Attribute-Table-Widget?p=258403#post258403

R_

AntGiles

Jason,

For the effect you want have you tried using Roberts esearch widget with a fixed data grid:

http://www.arcgis.com/home/item.html?id=5d4995ccdb99429185dfd8d8fb2a513e

Regards

Anthony

JasonHarshman

The layer I'm searching is indeed a feature service and not a map service.

Robert's esearch widget is great, like many of his widgets, but it has too many features that are unnecessary for my needs. I know I could edit the code to strip its features down, but I'm not a flash developer so that's uncharted territory for me.

If you look at my original post with the screenshot, you can see that the search results are being passed to the attribute table (w/o data) because a new tab becomes available. When I clear my search results, that tab goes away. So if the attribute table needs a feature service to show attributes, why does a new tab show up from the results of a search?

SarthakDatt

I've checked the box for "Add results as operational layer", and as expected, the results from a search are shown in the legend, layer list, and a tab is added for the results layer in the attribute table. However, the attribute table is blank with no records or fields. The results in the search widget are visible and there parcels selected. I've attached a screenshot to help illustrating what I'm experiencing.

Yes, the search and query widgets were both updated at 3.1 to start using feature layer(s) instead of graphics layer to be able to share results.

I tried using the out-of-the-box search widget with the Attribute Table widget working as expected. Would it be possible for you to share the config.xml and the search widget's config. Would be easier to debug.

AntGiles

Sarthak,

Yes, the search and query widgets were both updated at 3.1 to start using feature layer(s) instead of graphics layer to be able to share results.

I tried using the out-of-the-box search widget with the Attribute Table widget working as expected. Would it be possible for you to share the config.xml and the search widget's config. Would be easier to debug.

Is this documented any where as I can not seem to find any reference to it. Does this mean you save the results of many searches as layers in the viewer. If so how do you enable this feature in the config file.

Regards

Anthony

JasonHarshman

config code below:

<?xml version="1.0" ?>
<configuration>
    <zoomscale>50000</zoomscale>
    <shareresults>true</shareresults>
    <layers>
        <layer>
            <name>Parcels</name>
            <url>http://services.arcgis.com/wgcHnVlNZ7zk98J7/arcgis/rest/services/ECP_New_Parcels/FeatureServer/0</url&gt;
            <expression>AsmtNum = '[value]'</expression>
            <textsearchlabel>Search by Parcel Number</textsearchlabel>
            <titlefield>AsmtNum</titlefield>
            <fields>
                <field name="AsmtNum" alias="AsmtNum"/>
                <field name="Zoning" alias="Zoning"/>
                <field name="LUD" alias="LUD"/>
                <field name="ParcelType" alias="ParcelType"/>
                <field name="CalcAcres" alias="CalcAcres"/>
                <field name="Owner_Firs" alias="Owner_Firs"/>
                <field name="Owner_MI" alias="Owner_MI"/>
                <field name="Owner_Last" alias="Owner_Last"/>
                <field name="AssesseeNa" alias="AssesseeNa"/>
                <field name="Mailing_St" alias="Mailing_St"/>
                <field name="Mailing_Ci" alias="Mailing_Ci"/>
                <field name="Mailing__1" alias="Mailing__1"/>
                <field name="Mailing_Zi" alias="Mailing_Zi"/>
                <field name="Mailing_Ad" alias="Mailing_Ad"/>
                <field name="LandValue" alias="LandValue"/>
                <field name="ImprValue" alias="ImprValue"/>
            </fields>
            <orderbyfields>AsmtNum</orderbyfields>
        </layer>
    </layers>
</configuration>

RobertScheitlin__GISP

Anthony,

Just add

<shareresults>true</shareresults>

They seem to have missed this in the Widgets Tag References in the docs.

AntGiles

Robert,

Have you also migrated this change over to your enhanced search widget?

Regards

Anthony

RobertScheitlin__GISP

Antony,

No I don't want the results to show up in the layerlist or the toc so I add hiddenLayer_ to the FeatureLayers name.

SarthakDatt

Hey Jason,

The reason its not showing anything in the AT widget is because Attribute Table component is not able to create the columns. The Search widget should set the outfields on the (result)feature layer for that to happen, otherwise it just shows the 'displayfield'. My guess is your service does not have a display field set, hence you see nothing.

Quick fix for this would be to update the SearchWidget.mxml by adding:

private function createSearchResults(featureSet:FeatureSet, queryFields:XMLList):ArrayCollection
            {
                var result:ArrayCollection = new ArrayCollection();

                var layerDetails:LayerDetails = queryLayer.layerDetails;
                if (!queryTitleField)
                {
                    queryTitleField = featureSet.displayFieldName;
                }

                for each (var graphic:Graphic in featureSet.features)
                {   
                    var resultAttributes:ResultAttributes =
                        ResultAttributes.toResultAttributes(queryFields, textDirection, graphic, featureSet, queryLayer, layerDetails, widgetTitle, queryTitleField, queryLinkField, queryLinkAlias);

                    var searchResult:ResultItem = new ResultItem(graphic, resultAttributes);
                    result.addItem(searchResult);

                    var infoWindowRenderer:ClassFactory = new ClassFactory(PopUpRenderer);
                    infoWindowRenderer.properties = { popUpInfo: configurePopUpInfo(resultAttributes)};
                    graphic.infoWindowRenderer = infoWindowRenderer;
                }
                resultFeatureLayer.outFields = queryLayer.outFields; // for Attribute Table and/or AttributeInspector
                resultFeatureLayer.visible = true;
                resultFeatureLayer.featureCollection = new FeatureCollection(featureSet, layerDetails);
                switch (featureSet.geometryType)
                {
                    case Geometry.MAPPOINT:
                    {
                        resultFeatureLayer.renderer = new SimpleRenderer(resultMarkerSymbol);
                        break;
                    }
                    case Geometry.POLYLINE:
                    {
                        resultFeatureLayer.renderer = new SimpleRenderer(resultLineSymbol);
                        break;
                    }
                    case Geometry.POLYGON:
                    {
                        resultFeatureLayer.renderer = new SimpleRenderer(resultFillSymbol);
                        break;
                    }
                }

                return result;
            }

KennyHoran

Thanks Sarthak, I had the exact same problem and that fixed it. I hope that'll be included in the next release.

JasonHarshman

How do I set a display field for the service so I don't have to edit the mxml?

Or, how do I compile the revised mxml back to a .swf? I was able to get the source code for the searchwidget.mxml off of github, but now I don't know how to get it to widget form.

Thanks!

JasonHarshman

I was able to figure it out. It took downloading the entire flexviewer zip from hithub, but it worked. I did notice the individual mxml file on hithub does not have that line of code, https://github.com/Esri/arcgis-viewer-flex/blob/master/src/widgets/Search/SearchWidget.mxml, but it is included in the flexviewer zip. Oh well. Hopefully it's included in the 3.2 release.

BjornSvensson

Just wanted to follow up and let you know that this has been fixed and will be part of the 3.2 release (see GitHub Issue #22).

FYI: if you want to see what other viewer code changes made it into 3.2, look at the 58 closed and verified issues for 3.2:
https://github.com/Esri/arcgis-viewer-flex/issues?labels=verified&milestone=1&state=closed

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.