Latest Contributions by RobertScheitlin__GISP

@JoseSanchez  If you are taking about the "About" widget then you look in your apps configs folder and About folder and edit the config__#.json file. ... View more

@LixinHuang  No it does not. ... View more

@JasonLee9  This is a bug in WAB since 2.13 or earlier. The Fix is noted in this thread. https://community.esri.com/t5/web-appbuilder-custom-widgets-documents/enhanced-locate-widget-version-2-16-08-21-2020/tac-p/909841/highlight/true#M1564   ... View more

@john_cartwright_noaa  I am not really sure how you are resolving "props.stateProps.queryString" in your widget. I don't see "stateProps" in the widgets props object.   This is how I am doing it (not saying that this is necessary better). Sending Widget : this.props.dispatch(appActions.widgetStatePropChange(this.props.id, 'pSearchData', cTextElements));   Receiving Widget: interface ExtraProps{ pSearchData: any } .... export default class Widget extends React.PureComponent<AllWidgetProps<IMConfig> & ExtraProps, State>{ static mapExtraStateProps = (state: IMState, ownProps: AllWidgetProps<IMConfig>): ExtraProps => { let wId: string; for (const [key, value] of Object.entries(state.widgetsState)) { if(value.pSearchData){ wId = key; } } return { pSearchData: state.widgetsState[wId]?.pSearchData } } .... //Then else where in the widget code I use the extra prop this.props.pSearchData   ... View more

Not have not looked into that yet ... View more

@JeffPace   No I will not be adding that to the Identify Widget because the Identify task can identify layers in the map that are not configured in the widget and thus I don't have the proper field information. Also the Identify task is very different from the queryTask that the eSearch uses. ... View more

@_____  Try this: function zoomToServicePoint(results) { var feature = results.features[0]; feature.popupTemplate = { title: '<b>Layer: </b>Service Point', content: '<ul><li><b>Service Status: </b>{gs_service_status}</li>' + '<li><b>Meter Number: </b>{gs_meter_number}</li>' + '<li><b>Access Note: </b>{AccessNotes}</li><ul>' } view.popup.open({ features: feature, fetchFeatures: true }); } ... View more

@T_Syaherah  Can you reproduce this issue in the Live Preview Site? Just stating that the widget gives and error and not posting the details of the error is not going to help. ... View more

@NicoKroes  The filter and group filter widgets are very difficult to follow in code. Each parameter of the filter gets a jimu/dijit/FilterParameter and that module uses _SingleFilterParameter. If you attempt to follow the code then the FilterParameter module has a _spObj that holds all the _SingleFilterParameter objects. The _SingleFilterParameter has a method called getValueObject. ... View more

@TaniaH  The live preview site is using a point feature class. So I am not sure why you are experiencing any problems. https://gis.calhouncounty.org/wab/v2.12/widgets/FLHover/   ... View more

@AlejandroMari1    You can always change IIS limits for that. https://www.mytecbits.com/microsoft/iis/iis-changing-maxquerystring-and-maxurl   ... View more

There is a custom print widget available here: https://community.esri.com/t5/experience-builder-custom-widgets/print-widget-eb-1-4-1/ta-p/1058721   ... View more

@AlejandroMari1  I can not explain why you are getting this error as I can use paste this code into my widget and it functions fine. You must have other issues in your widgets code. ... View more