Latest Contributions by DongxingMa

Ok, I will do that. Thanks, Jonathan! ... View more

Thank you for your quick reply! Should I submit a help ticket for my problem or just wait for a ESRI support to contact me?  ... View more

The problem I get is similar, but it occurs when opening the feature class's attribute table, the table cannot even be loaded. ... View more

Dongxing, This is strange as I get error 400 when using the standard esri search widget when using a joined layer that has a subtype. Actually That is the test case I shared with esri when reporting this bug. Also strange that you say  esris search widget does handle subtype fine as long as there is no join as well. Whether you leave the Subtype field out of your eSearchWidget.xml field list or not does not matter as esri adds the subtype field automatically in the API when a query is done on a layer that has a subtype defined in its REST end point. The only way to get past that is to hide the Subtype field in the MXD before you publish the map service. Once you hide the SubType field in the MXD and republish the service (with the Join), then version 3.5.3 works just fine as well as older versions of the eSearch. Why?.. In 3.5.3 Subtypes works and joined tables has worked way back since the 2.x version of the widget. Hi Robert, This is really interesting, we have some different findings and test results: 1>I have been using ESRI's regular search widget, it does handle joined table/fields well, and at the same time, I mean while the joined table exists, it can display and even search by subtype field, won't give error or stop search process, the only issue for me is: it doesn't display subtype's description, it just directly returns the code number. (seems different with your finding!) 2>for your eSearch widget 3.5.3, I found when no joined table exists, it handles subtype field well, returns the description; but if a joined table and a subtype field both exist (change field names in the configuration accordingly, of course), then the esearch process crushes, gives the "400" error. (are you seeing different result when both subtype field and joined table existing in the search layer?) 3>I thought eSearch 3.5.3 cannot handle joined table even subtype field turned off in the mxd, so I said that I may have to go back to use 3.5 version. This is a mistake. I found the subtype field wasn't turned off yesterday when testing. Now I am sure as long as subtype field turned off, eSearch 3.5.3 handles joined table/fields well, so I will use the latest version eSearch. 4>I still hope you make a version that can have subtype field and joined table/fields co-existing in the search layer, won't give error, can finish search, just treat subtype field as a regular field, directly return the code number. This way, we can use a domain table join to the subtype field, and search by subtype field but return the joined domain table's description field. This is what I have done using the OTB search widget. Hope I have made my points clearer now. Please advise me if you see any better solution. Thanks! Dongxing ... View more

Dongxing,    Well I have some bad news. It turns out that this is a documented ArcGIS Server issue. There was a bug logged NIM083086 and the Bug was rejected by the server development team "Known Limitation On Server End". The other user that had this same situation was told to remove the join or the Subtype field (not much of a resolution). I have added my name to the nimbus bug for this issue to see if it can be reopened and possibly get fixed without out a lame response from the development team, to just remove the join or the subtype field. I would recommend that you report the bug as well (make sure that you duplicate the issue using the OTB Search widget and not the eSearch, or they will just blame it on the custom widget). This is really too bad! I have spent quite a lot of time trying to make it work, didn't find the bug info until you told me. Now I understand why even you couldn't make it work. I definitely will report the bug to ESRI. I think my case is a very common case, why they don't want to fix the bug? Come back to the eSearch widget, I think joined table and fields are much more important than subtype field(which I can create a specific version of map services for eSearch to use, in this map service turn subtype field off) for us, so I may have to use the 3.5 version eSearch instead of the latest version 3.5.3.  By the way, is the "OTB Search widget" just ESRI's regular search widget? We have been using it for two years, I knew it only directly displays subtype value as number (code), can't automatically transfer code into description and display it, but it doesn't give a error, doesn't crush the search. So, I created domain tables for all our subtype and domain fields, and related them together, in identify and search widgets configuration files, make them display the description fields while searching by the code fields. I wonder if you have a similar version of eSearch, that it can handle joined table and fields well, and just treat subtype field as a regular field to read and display the code numbers, but won't give error message, won't crush the search process? If you do have such a version, or you can easily create such a version, that would still be a very good news for users like me (please consider about  it if it won't cost you too much time). Anyway, we need push ESRI develop team to fix their bug! Thank you very much for your information, your widgets and all the work you are sharing with the community! Dongxing ... View more

Dongxing,    Is it possible for you to provide a sample of your data in a File GDB for testing? Thank you, Robert! I have uploaded our sample data, it's OtaySewertest.gdb.zip. The widget layer box width issue is not a problem anymore, and the widget works for subtypes field and domain now, but--it's only when without joined tables associate with the layer! The new problem is like: if the layer has a joined table with it (the fields in my map service is like: ----------------------------------------------------------------------------------------------------- ssGravityMain.OBJECTID ( type: esriFieldTypeOID , alias: OBJECTID ) ssGravityMain.Subtype ( type: esriFieldTypeInteger , alias: Subtype ) ssGravityMain.FacilityID ( type: esriFieldTypeString , alias: FacilityID , length: 30 ) ...... otaypub.dbo.vw_wASBUILTS_URL.SID ( type: esriFieldTypeInteger , alias: SID ) otaypub.dbo.vw_wASBUILTS_URL.AsBuiltNo ( type: esriFieldTypeString , alias: AsBuiltNo , length: 50 ) otaypub.dbo.vw_wASBUILTS_URL.ASBUILTURL ( type: esriFieldTypeString , alias: ASBUILTURL , length: 87 ) ----------------------------------------------------------------------------------------------------- then it can't search the layer anymore, even when the subtype field turned off (before it worked when subtype field turned off). The error is still the "400" error, same as before. Here I attached our sample sewer datasets, please test the three layers and join the table: asbuiltTab to the layers by "asbuiltno" fields. I really want to use the wonderful widget in our flex viewer, hope it won't cost you too much time to make it works for both subtype field (with domain), and the joined table and its fields. Please let me know if you need anything else for testing. Really appreciate your help! Dongxing ... View more

Julie and Dongxing,   I found several issue with SubTypes when using Julies test data and those have been addressed in version 3.5.3 with will be available 10/22/13 or 10/23/13. Thank you very much for your help! But I still don't have the luck to enjoy the beauty of the widget yet. I still get the same error message when the subtype field is turned on, and one new issue comes up: The Select Layer: pulldown listbox and field pulldown list box widths are both zero, and in the right side (supposed to be in left side), can't see the layer names or the field names. Could you please tell me how can I fix the issues, or you have to change your source code! Thanks, Dongxing ... View more

Dongxing,   Actually I was wanting to see your layer configuration in the eSearchWidget.xml. Sorry, simply followed the previous user who put the REST services directory info there, my bad. Below are the configurations of layer wPressurizedMain and wMeter. I don't think there is any syntax error there,I feel it's just subtype field can't be handled by the widget. because once the subtype field is turned off in the map mxd, the same configuration works very well, but never worked when the subtype field turned on. Please let me know if you need anything else. Thanks, Dongxing -----------------------------------------------------------------------------------------------   <layer>    <token/>    <definitionexpression></definitionexpression>    <enableexport>true</enableexport>    <enableprintgrid>true</enableprintgrid>    <name>PressurizedMain</name>    <url>http://owd-gis1/arcserver101/rest/services/OtayDashBoard/FacilityQuery_Test2/MapServer/6</url>    <expressions>     <expression alias="OBJECTID" textsearchlabel="Search by OBJECTID:">      <values>       <value prompt="Example: 1,2,3">OtayMaint.OTAYDATA.wPressurizedMain.OBJECTID = [value]</value>      </values>     </expression>     <expression alias="FacilityID" textsearchlabel="Search by FacilityID:">      <values>       <value prompt="Example: S-055-0003">OtayMaint.OTAYDATA.wPressurizedMain.FacilityID LIKE '[value]%'</value>      </values>     </expression>    </expressions>    <graphicalsearchlabel>Use one of the graphical search tools to select a pressurizedmain line</graphicalsearchlabel>    <spatialsearchlayer>true</spatialsearchlayer>    <titlefield>OtayMaint.OTAYDATA.wPressurizedMain.FacilityID</titlefield>    <fields all="false">     <field name="OtayMaint.OTAYDATA.wPressurizedMain.FacilityID" gridfield="true" alias="FacilityID" />     <field name="OtayMaint.OTAYDATA.wPressurizedMain.OBJECTID" gridfield="true" alias="OBJECTID" />     <field name="OtayMaint.OTAYDATA.wPressurizedMain.InstallDate" gridfield="true" alias="InstallDate"/>     <field name="OtayMaint.OTAYDATA.wPressurizedMain.Diameter" gridfield="true" alias="Diameter"/>     <field name="OtayMaint.OTAYDATA.wPressurizedMain.PressureRating" gridfield="true" alias="PressureRating"/>     <field name="otaypub.dbo.vw_wASBUILTS_URL.AsBuiltNo" gridfield="true" alias="AsBuiltNo" />     <field name="otaypub.dbo.vw_wASBUILTS_URL.ASBUILTURL" gridfield="false" alias="ASBUILTURL" hyperlinkgridfield="true" hyperlinkaliastext="{otaypub.dbo.vw_wASBUILTS_URL.ASBUILTURL}" hyperlinkgridicon="assets/images/i_lego.png" />    </fields>    <links>     <link alias="ASBUILTURL" disablelinksifnull="true" disableinpopups="true">      <![CDATA[{otaypub.dbo.vw_wASBUILTS_URL.ASBUILTURL}]]>      <icon><![CDATA[assets/images/i_biomass.png]]></icon>     </link>    </links>    <zoomscale usegeometry="true" zoompercent="1.6" />    <autoopendatagrid>true</autoopendatagrid>    <queryattachments>false</queryattachments>   </layer>   <layer>    <token/>    <definitionexpression></definitionexpression>    <enableexport>true</enableexport>    <enableprintgrid>true</enableprintgrid>    <name>Potable Meters</name>    <url>http://owd-gis1/arcserver101/rest/services/OtayDashBoard/FacilityQuery_Test2/MapServer/1</url>    <expressions>     <expression alias="FacilityID" textsearchlabel="Search by FacilityID:">      <values>       <value prompt="Example: M-065-1140">OtayMaint.OTAYDATA.wMeter.FacilityID LIKE '[value]%'</value>      </values>     </expression>     <expression alias="MeterNumber" textsearchlabel="Search by MeterNumber:">      <values>       <value prompt="Example: 99100287">GoldStandard.dbo.Meter_Account.METER_NUMBER LIKE '[value]%'</value>      </values>     </expression>     <expression alias="SERVICELOCID" textsearchlabel="Search by SERVICELOCID:">      <values>       <value prompt="Example: 12625">GoldStandard.dbo.Meter_Account.SERVICELOCID LIKE '[value]%'</value>      </values>     </expression>     <expression alias="ACCT_NO" textsearchlabel="Search by ACCT_NO:">      <values>       <value prompt="Example: 206-0052-60">GoldStandard.dbo.Meter_Account.ACCT_NO LIKE '[value]%'</value>      </values>     </expression>    </expressions>    <graphicalsearchlabel>Use one of the graphical search tools to select a Meter</graphicalsearchlabel>    <spatialsearchlayer>true</spatialsearchlayer>    <titlefield>OtayMaint.OTAYDATA.wMeter.FacilityID</titlefield>    <fields all="false">     <field name="GoldStandard.dbo.Meter_Account.METER_NUMBER" gridfield="true" alias="MeterNumber" />     <field name="GoldStandard.dbo.Meter_Account.SERVICELOCID" gridfield="true" alias="SERVICELOCID" />     <field name="GoldStandard.dbo.Meter_Account.ACCT_NO" gridfield="true" alias="ACCOUNT NUMBER" />     <field name="OtayMaint.OTAYDATA.wMeter.AsBuiltNo" gridfield="true" alias="AsBuiltNo" />     <field name="otaypub.dbo.vw_wASBUILTS_URL.ASBUILTURL" gridfield="false" alias="ASBUILTURL" hyperlinkgridfield="true" hyperlinkaliastext="{otaypub.dbo.vw_wASBUILTS_URL.ASBUILTURL}" hyperlinkgridicon="assets/images/i_lego.png" />    </fields>    <links>     <link alias="ASBUILTURL" disablelinksifnull="true" disableinpopups="true">      <![CDATA[{otaypub.dbo.vw_wASBUILTS_URL.ASBUILTURL}]]>      <icon><![CDATA[assets/images/i_biomass.png]]></icon>     </link>    </links>    <zoomscale usegeometry="true" zoompercent="1.6" />    <autoopendatagrid>true</autoopendatagrid>    <queryattachments>false</queryattachments>   </layer> ----------------------------------------------------------------------------------------------- ... View more

Thanks for the quick responses! Actually all feature classes that have a true subtype field (with code # and domain) have this issue, not only one layer. Not sure what info you need exactly, hope below map service info helps: ============================================================= Layer: Potable Pressurized Mains (ID: 12) Name: Potable Pressurized Mains Display Field: otaypub.OTAYDATA.wPressurizedMain.AdministrativeArea Type: Feature Layer Geometry Type: esriGeometryPolyline Description: Definition Expression: Copyright Text: Default Visibility: true MaxRecordCount: 1000 Supported Query Formats: JSON, AMF Min Scale: 50000 Max Scale: 0 Supports Advanced Queries: false Supports Statistics: false Has Labels: false Can Modify Layer: false Can Scale Symbols: false Extent: XMin: 6314450.807010651 YMin: 1779630.322790414 XMax: 6381950.007841527 YMax: 1868933.5962175876 Spatial Reference: 102646  (2230) Drawing Info: Renderer: Unique Value Renderer: Field 1: otaypub.OTAYDATA.wPressurizedMain.Subtype Field 2: otaypub.OTAYDATA.wPressurizedMain.LifecycleStatus Field 3: null Field Delimiter: , Default Symbol: Style: esriSLSSolid Color: [0, 92, 230, 255] Width: 1 Default Label: UniqueValueInfos: Value: 7, Existing Label: TransmissionMain Description: Symbol: Style: esriSLSSolid Color: [0, 0, 0, 255] Width: 3 Value: 2, Existing Label: Existing Description: Symbol: Style: esriSLSSolid Color: [0, 92, 230, 255] Width: 1 Value: 1, Existing Label: Existing Description: Symbol: Style: esriSLSSolid Color: [0, 92, 230, 255] Width: 1 Value: 9, Existing Label: Existing Description: Symbol: Style: esriSLSSolid Color: [0, 92, 230, 255] Width: 1 Value: 3, Existing Label: Existing Description: Symbol: Style: esriSLSSolid Color: [0, 92, 230, 255] Width: 1 Value: 4, Existing Label: Existing Description: Symbol: Style: esriSLSSolid Color: [0, 92, 230, 255] Width: 1 Value: 8, Existing Label: Existing Description: Symbol: Style: esriSLSSolid Color: [0, 92, 230, 255] Width: 1 Value: 6, Existing Label: Existing Description: Symbol: Style: esriSLSSolid Color: [0, 92, 230, 255] Width: 1 Value: 2, Abandoned Label: Abondoned; Removed Description: Symbol: Style: esriSLSDash Color: [0, 92, 230, 255] Width: 1 Value: 2, Removed Label: Abondoned; Removed ...... ...... Labeling Info: HasZ: false HasM: true Has Attachments: false HTML Popup Type: esriServerHTMLPopupTypeNone Type ID Field: Subtype Fields: otaypub.OTAYDATA.wPressurizedMain.OBJECTID ( type: esriFieldTypeOID , alias: OBJECTID ) otaypub.OTAYDATA.wPressurizedMain.Enabled ( type: esriFieldTypeSmallInteger , alias: Enabled , Coded Values: [0: False] , [1: True] ) otaypub.OTAYDATA.wPressurizedMain.Subtype ( type: esriFieldTypeInteger , alias: Subtype ) otaypub.OTAYDATA.wPressurizedMain.AdministrativeArea ( type: esriFieldTypeString , alias: AdministrativeArea , length: 7 , Coded Values: , , , ...2 more... ) otaypub.OTAYDATA.wPressurizedMain.FacilityID ( type: esriFieldTypeString , alias: FacilityID , length: 25 ) otaypub.OTAYDATA.wPressurizedMain.InstallDate ( type: esriFieldTypeInteger , alias: InstallDate ) otaypub.OTAYDATA.wPressurizedMain.LifecycleStatus ( type: esriFieldTypeString , alias: LifecycleStatus , length: 20 , Coded Values: [Abandoned: Abandoned] , [Existing: Existing] , [Proposed: Proposed] , ...2 more... ) otaypub.OTAYDATA.wPressurizedMain.WorkorderID ( type: esriFieldTypeString , alias: WorkorderID , length: 20 ) otaypub.OTAYDATA.wPressurizedMain.WaterType ( type: esriFieldTypeString , alias: WaterType , length: 15 , Coded Values: [Potable: Potable Water] , [Recycled: Recycled Water] , [FutureRecycle: Future Recycle] ) otaypub.OTAYDATA.wPressurizedMain.Material ( type: esriFieldTypeString , alias: Material , length: 30 , Coded Values: [DIP: Ductile Iron] , [CIP: Cast Iron] , [PVC: Poly Vinyl Chloride] , ...10 more... ) otaypub.OTAYDATA.wPressurizedMain.Otayrecord ( type: esriFieldTypeString , alias: Otayrecord , length: 20 ) otaypub.OTAYDATA.wPressurizedMain.Facilitypage ( type: esriFieldTypeString , alias: Facilitypage , length: 10 ) otaypub.OTAYDATA.wPressurizedMain.Encase ( type: esriFieldTypeString , alias: Encase , length: 7 , Coded Values: [Yes: Yes] , [No: No] ) otaypub.OTAYDATA.wPressurizedMain.FTC ( type: esriFieldTypeString , alias: FTC , length: 50 ) otaypub.OTAYDATA.wPressurizedMain.Pipeclass ( type: esriFieldTypeString , alias: Pipeclass , length: 20 ) otaypub.OTAYDATA.wPressurizedMain.Remarks ( type: esriFieldTypeString , alias: Remarks , length: 150 ) otaypub.OTAYDATA.wPressurizedMain.ExteriorCoating ( type: esriFieldTypeString , alias: ExteriorCoating , length: 20 ) otaypub.OTAYDATA.wPressurizedMain.JointType1 ( type: esriFieldTypeString , alias: JointType1 , length: 20 , Coded Values: [Flange: Flange] , [Weld: Weld] , [Bond: Bond] , ...2 more... ) otaypub.OTAYDATA.wPressurizedMain.JointType2 ( type: esriFieldTypeString , alias: JointType2 , length: 20 , Coded Values: [Flange: Flange] , [Weld: Weld] , [Bond: Bond] , ...2 more... ) otaypub.OTAYDATA.wPressurizedMain.LiningType ( type: esriFieldTypeString , alias: LiningType , length: 20 ) otaypub.OTAYDATA.wPressurizedMain.Roughness ( type: esriFieldTypeDouble , alias: Roughness ) otaypub.OTAYDATA.wPressurizedMain.Imagelink ( type: esriFieldTypeString , alias: Imagelink , length: 150 ) otaypub.OTAYDATA.wPressurizedMain.old_Diameter ( type: esriFieldTypeDouble , alias: old_Diameter ) otaypub.OTAYDATA.wPressurizedMain.PZone ( type: esriFieldTypeString , alias: PZone , length: 50 ) otaypub.OTAYDATA.wPressurizedMain.Depth ( type: esriFieldTypeDouble , alias: Depth ) otaypub.OTAYDATA.wPressurizedMain.Diameter ( type: esriFieldTypeDouble , alias: Diameter , Coded Values: [1: 1 inch] , [2: 2 inch] , [4: 4 inch] , ...23 more... ) otaypub.OTAYDATA.wPressurizedMain.GroundSurfaceType ( type: esriFieldTypeString , alias: GroundSurfaceType , length: 20 ) otaypub.OTAYDATA.wPressurizedMain.PressureRating ( type: esriFieldTypeString , alias: PressureRating , length: 20 ) otaypub.OTAYDATA.wPressurizedMain.Set_ID ( type: esriFieldTypeString , alias: Set_ID , length: 50 ) otaypub.OTAYDATA.wPressurizedMain.INGBAMS ( type: esriFieldTypeSmallInteger , alias: INGBAMS ) otaypub.OTAYDATA.wPressurizedMain.GBALINK ( type: esriFieldTypeInteger , alias: GBALINK ) otaypub.OTAYDATA.wPressurizedMain.TempID ( type: esriFieldTypeInteger , alias: TempID ) otaypub.OTAYDATA.wPressurizedMain.ASBUILTNO ( type: esriFieldTypeString , alias: ASBUILTNO , length: 10 ) otaypub.OTAYDATA.wPressurizedMain.GlobalID ( type: esriFieldTypeGlobalID , alias: GlobalID , length: 38 ) otaypub.OTAYDATA.wPressurizedMain.MODEL ( type: esriFieldTypeString , alias: MODEL , length: 10 ) otaypub.OTAYDATA.wPressurizedMain.MODEL_ID ( type: esriFieldTypeString , alias: MODEL_ID , length: 50 ) otaypub.OTAYDATA.wPressurizedMain.RuleID ( type: esriFieldTypeInteger , alias: RuleID , Coded Values: [1: Air/Vac, Abandoned, ; Air/Vac, Abandoned, ; Air/Vac, Removed, ] , [2: Air/Vac, Existing, ; Air/Vac, Existing, 1050; Air/Vac, Existing, 711; Air/Vac, Existing, 805; Air/Vac, Existing, 978; Air/Vac, Existing, 980; Air/Vac, Existing, ; Air/Vac, Existing, null] , [3: Air/Vac, Proposed, ; Air/Vac, Proposed, 7; Air/Vac, Proposed, ] , ...72 more... ) otaypub.OTAYDATA.wPressurizedMain.Override ( type: esriFieldTypeBlob , alias: Override ) otaypub.OTAYDATA.wPressurizedMain.Shape ( type: esriFieldTypeGeometry , alias: Shape ) OtayPub.dbo.vw_wASBUILTS_URL.AsBuiltNo ( type: esriFieldTypeString , alias: AsBuiltNo , length: 50 ) OtayPub.dbo.vw_wASBUILTS_URL.ASBUILTURL ( type: esriFieldTypeString , alias: ASBUILTURL , length: 87 ) OtayPub.dbo.vw_wASBUILTS_URL.SID ( type: esriFieldTypeInteger , alias: SID ) Types: ID: 1 Name: BlowOff Domains: otaypub.OTAYDATA.wPressurizedMain.Enabled: Inherited otaypub.OTAYDATA.wPressurizedMain.AdministrativeArea: Inherited otaypub.OTAYDATA.wPressurizedMain.LifecycleStatus: Inherited otaypub.OTAYDATA.wPressurizedMain.WaterType: Inherited otaypub.OTAYDATA.wPressurizedMain.Material: Inherited otaypub.OTAYDATA.wPressurizedMain.Encase: Inherited otaypub.OTAYDATA.wPressurizedMain.JointType1: Inherited otaypub.OTAYDATA.wPressurizedMain.JointType2: Inherited otaypub.OTAYDATA.wPressurizedMain.Diameter: Inherited -------------------------------------------------------------------------------- ID: 3 Name: Chemical ...... -------------------------------------------------------------------------------- ID: 6 Name: WaterTestStation ...... ...... ============================================================= ... View more

Robert, First of all, thank you for the great widget! My strange problem is, the eSearch widget always gives me the "400" error: [RPF Fault faultString="Invalid or missing input parameters."faultCode="400" faultDetail=""] if the searched feature class has a subtype field. For any of the layers in our map services, as long as subtype field is included (in map service REST: it shows: Type ID Field: Subtype),I never ever made eSearch work; but once I hide the subtype field, recreate the map service (then in REST it shows: Type ID Field: null), then the same query will work well for the layer. This happens even the search query doesn't tough subtype field at all. I checked online, looks nobody else has this same problem, could you please give me a clue, where should I go to find and fix the problem? I am using arcgis server 10.1, flash builder 4.7, and arcgis flex viewer/arcgis api for flex 3.5. Thanks in advance for helping me out! Dongxing ... View more