Latest Contributions by ChrisWhitmore

Hi Erik, we have a patch going out tonight to resolve this issue. Sorry for the trouble. Thanks, Chris ... View more

Hi Malcom - answers inline below:  I don't actually need to display all the field attributes, but if I cut it down to just one attribute field configured in the pop-up, then I still get no information returned.  It looks like all fields are included in the query request even if only one field is configured...looking into this to see if this expected (and why). Would it help if I used shortened field aliases for the feature class, in the mxd underpinning the service? (and re-published) Or renamed the feature class in the mxd to a shorter name? I don't think either of these changes would help in this case. You could look at setting a definition expression to hide fields you wouldn't want in the popup (Shape_length, Shape_area for ex). Also how do you obtain the query code thats being sent to the server (that you've included in your reply above)? I used the browser's developer tools to capture the network traffic between the browser and the service. In my case, I used Chrome - you can access the developer tools by pressing CTRL+ SHIFT + i at the same time. There will be a series of tabs..click the network tab and then click on a feature in the map - you should then see the query request being made to the server. It will look something like this: Cheers Chris ... View more

Hi Alessandro, this is a bug in the 4x JSAPI. Should be fixed with the next release (planned for Sept). thanks, Chris ... View more

Hi Devin, the editing types can be updated separately - in the edit dialog, you should see see a button in the lower right titled "Manage". That will open a panel for managing editing types and templates. From there, click the dropdown for each type you want to remove. Once the types are removed, you should see the editing experience reflect which types are available. Thanks, Chris ... View more

Hi Matt, it looks like there is an issue with parsing certain characters in the layer's style - the '<' and '>' characters aren't being handled correctly when copying the layer (it appears the layer names used to create the vector tile layer have the greater than / less than symbols: "source-layer": "Background, >9k" for ex). This is ultimately what's causing the issue. The workaround is to upload the style json file directly. That will bypass the systems handling of the style json (and subsequently the parsing issue when copying the layer). Attached is the "copied" json you can use to upload on the copied layer (and can be customized however you need first). It'll be easier to use this json rather than downloading directly from the hosted layer. The hosted layer's style has relative urls which won't resolve correctly if directly copied to a different layer (when copying in the map viewer, the viewer handles the updating of the urls to point to the correct resources. the json i posted has the updated urls). I was able to check out the initial layer you posted before it was deleted - it looks like this was the issue for that layer (relative url could not resolve correctly so the layer did not load at all). We'll look into fixing the parsing issue for < and > for the next release. If you need this same fix for other hosted layers (would think so since this one is a test), check out the urls in the attached json. There are three urls that will need to be updated to point to to the original source vector tile layer (effectively hardcoding the urls rather than persisting the relative urls), which hosts all the resources used for copies. Sorry for the hassle. Let me know if you run into issues or if this doesn't make any sense Chris ... View more