Enhanced-Search-Widget-for-FlexViewer Part III

[RobertScheitlin__GISP]

All,

   Here is a new thread to post questions and discuss the Enhanched Search Widget. The old thread was getting too long.

[RobertScheitlin__GISP]

Karen,

   Sorry I don't have a clue why the label portion of the query being in front case the error (sounds like a call to tech support). As far as the datagrid and date you just need to specify the dateformat for the gridfield.

<field name="INSPECTIONDATE" gridfield="true" dateformat="MM/DD/YYYY" useutc="true" />

[CaseyMcMillin]

Casey,

   I am unable to test using the data you sent earlier as the second relate is not there. Can you sent all the data for the new test case?

Robert,

Here is the data with the second relationship.  I also included the eSearch config in case I have something horribly wrong in there.  The second hyperlink needs to a folder rather than a document.

Thanks again,
Casey

[RobertScheitlin__GISP]

Casey,

  I do seem to have some sort of issue where you can not only specify on field in the relate if it is a hyperlink field. This is what worked for me:

            <relates>
                <relate id="0" label="Asbuilts" enableprintgrid="false">
                    <fields all="false">
                        <field name="ASBUILTID" gridfieldonly="true"/>
                        <field name="FILEPATH" alias="View Asbuilt" gridfieldonly="true" hyperlinkgridfield="true" hyperlinkaliastext="View Asbuilt" linkprefix="http://GIS01/Asbuilts/" linksuffix=".pdf"/>
                    </fields>
                    <zoomscale usegeometry="true" zoompercent="1.6" />
                </relate>
                <relate id="1" label="TV Projects" enableprintgrid="false">
                    <fields all="false">
                        <field name="FILEPATH" gridfieldonly="true"/>
                        <field name="TVPROJECT" gridfieldonly="true" hyperlinkgridfield="true" hyperlinkaliastext="View TV Project" linkprefix="http://GIS01/TVProjects/"/>
                    </fields>
                    <zoomscale usegeometry="true" zoompercent="1.6" />
                </relate>
            </relates>

Seems how you second relate is not a file but just a directory, do you have directory browsing enabled on your IIS virtual directory?

[CaseyMcMillin]

Casey,

  I do seem to have some sort of issue where you can not only specify on field in the relate if it is a hyperlink field. This is what worked for me:

            <relates>
                <relate id="0" label="Asbuilts" enableprintgrid="false">
                    <fields all="false">
                        <field name="ASBUILTID" gridfieldonly="true"/>
                        <field name="FILEPATH" alias="View Asbuilt" gridfieldonly="true" hyperlinkgridfield="true" hyperlinkaliastext="View Asbuilt" linkprefix="http://GIS01/Asbuilts/" linksuffix=".pdf"/>
                    </fields>
                    <zoomscale usegeometry="true" zoompercent="1.6" />
                </relate>
                <relate id="1" label="TV Projects" enableprintgrid="false">
                    <fields all="false">
                        <field name="FILEPATH" gridfieldonly="true"/>
                        <field name="TVPROJECT" gridfieldonly="true" hyperlinkgridfield="true" hyperlinkaliastext="View TV Project" linkprefix="http://GIS01/TVProjects/"/>
                    </fields>
                    <zoomscale usegeometry="true" zoompercent="1.6" />
                </relate>
            </relates>

Seems how you second relate is not a file but just a directory, do you have directory browsing enabled on your IIS virtual directory?

Robert,
That does not resolve the error for me in the test or production environments.  I do have directory browsing enabled in the virtual directory and the links work for both relates, but they both still cause the map to error.  I am thinking I may just have to duplicate that layer with one relate per layer as a work around.
Thanks,
Casey

[RobertScheitlin__GISP]

Casey,

   In my test environment using your data it works fine... When you say it errors what exactly do you mean (screenshots help)? Is there a particular Facility ID that is erroring? I have been using 143 and 1032 for testing.

[CaseyMcMillin]

Casey,

   In my test environment using your data it works fine... When you say it errors what exactly do you mean (screenshots help)? Is there a particular Facility ID that is erroring? I have been using 143 and 1032 for testing.

Robert,
The error occurs any time I interact with the fixed datagrid (even clicking on the field that is not the hyperlink causes the error) regardless of Facility ID.
Thanks,
Casey

[AngieAllison]

Marie,

   If you notice post #68 That issue is fixed in version 3.3.2.

yes i ran accross that today !!  Thank you for the quick response on those changes !!  I am totally up and running and i am positive the end users are going to love this.  So much easier to use than the old query widget.  Thanks again for your help.  We are goin gto use this as well as a way to PRINT data.  So i careted some searches that are by a facility id and coupied it out 10 or 12 times and then they can enter different facility id's, do the search and get the DATA into excel !!!  awesome !!  we have wanted to print data for a long time.

[RobertScheitlin__GISP]

Casey,

   Remind me are you using the compiled or source code for this widget? If you are using the compiled are you sure that you have replaced the SearchWidgetFixedDG.swf with the latest from the download?

[RobertScheitlin__GISP]

Casey,

   Did you upgrade to 3.3.1 or 3.3.2?

[ShawnSimpson]

Hi all - I hope I haven't overlooked the answer; however, I am having issues querying a field that participates in a table join. From what I can tell, it seems to be supported considering the user guides speak about using the full join field name? I could be wrong...

My code is similar to what is shown below below:

<expression alias="Valve ID" textsearchlabel="Search Valves by ID">
  <values>
    <value prompt="Example: 40361 (use % for wildcard)">wStreetValve.ValveID like '[value]'</value>
  </values>
</expression>

All fields are referenced using their full joined name. Is this not supported?

Thanks!
I appreciate any help that is offered.

I should add that the web app is built using Flex Viewer 2.5 and we are using version 2.9.0 for the Enhanced Search Widget.