Latest Contributions by JamesCrandall

I believe we're going to just implement a simple map viewer JavaScript app to embed.  I had hoped to utilize the WAB framework so that we don't have to re-invent functionality, but will just have to try to keep things as simple as possible in order to reduce code that has to be managed. ... View more

Has anyone attempted cross-domain control through an iFrame with easyXDM?  https://github.com/oyvindkinsey/easyXDM#readme ... View more

Katie, You are showing two different ways url parameters are setup and defined.  That is exactly the problem!    Your first link shows the clean approach "parcel=<some value", then you show that wonky "&feature=FireHydrants_3792;<search column>;<search value>". I understand both of these but I need to standardize this url parameter search for the embedded map product.  Because the Minimalist app can only configure ONE custom url search parameter in one format, then switch to using "&feature=" as another format completely defeats the purpose of considering embedding the Minimalist app.  I would rather just have an embedded web map and use a single url search parameter format because the page that this is embedded is setting the values to search on. Also consider we have dev/test/production embedded products that are managed, so just sticking with embedded web maps rather than an additional wab will reduce items that need to be managed by half. Is that what you are looking for or is that what you are saying breaks across environments? Consider this: FireHydrants_3792 will be different across dev/test/prod items that will be embedded. FireHydrants_0001, FireHydrants_0002, FireHydrants_0003 Multiple search layers will be configured not just FireHydrants_3792.  Layer2_0001, Layer3_0001, Layer4_0001, Layer5_0001 You can see how messy this can get as all of those url parameters and then have non-GIS developers who are embedding this item and dynamically setting parameter search values.  This is why I hoped to use the minimalist WAB app to simplify because the url parameter is simple: &<layername>=<somevalue> I'll likely just go back to a web map product instead because it will reduce the number of items that will need to be managed. ... View more

Is your intent to embed a link in your website that will open the app zoomed in to a specific feature?  Yes but the entire app is embedded into the website, not just a link.  As that page loads, the embedded Web AppBuilder app should zoom to the specific feature onLoad and is the reason why I need to setup a Custom Url Parameter.  This works just fine with a single url parameter search configured!  My question in the OP is if I can configure an additional url parameter search on a different layer/map service.  I can do this if I embed a regular web map viewer with multiple search layers configured, but the way you must configure the url parameter is strange and prone to break across dev/test/production products (see Kelly's reply in THIS thread) Or do you want the end users to be able to type a value into the search box that could be in any layer and get a result? No, the search is performed onLoad of the map using url parameters. Thanks! ... View more

Yes, I'm describing the Minimalist template for the hosted web Web AppBuilder. If you are using the minimalist template you can configure multiple search layers under the search tab Yes, I understand but we're not using that type of search function.  We are embedding this app into another page and performing the search via url parameter when it opens using the "Custom Url Parameters" setup. My question is, how can I setup multiple search parameters for the different search layers configured on the web map source to this WAB. ... View more

Interesting.  I'll take another look before bothering. ... View more

Correct.  It seems that the feature service downloads the data with the query applied, but all of the attachments are being pulled down rather than only the related ones. ... View more

Oh, I think my problem was an incorrect WKID value on the spatial reference set for one of the stops I had listed. ... View more

Could you post your solution?  I'm struggling with this same issue. ... View more

What do you recommend to do if the hosted FS has over 1gb of attachments? We'd like to only pull down after a specific "CreateDate" but any modifications to the .py source we've attempted has failed due to issues with GlobalId values between the parent feature and child attachment. ... View more

I had a similarly "fuzzy" response when I got the question, I had a hunch that [0] is an index position but not exactly sure to what. Note!  there is no ….. blah = CreateFeatureclass I am able to reference facFC var on the next line in order to add a field: facFC = arcpy.CreateFeatureclass_management("in_memory", "facFC", "POINT")[0] arcpy.AddField_management(facFC, "NAME", "TEXT", None, None, 40, "", "NULLABLE", "NON_REQUIRED")‍‍ Thank you for the response! ... View more

I was close, you nailed the complete solution --- I was not correctly setting the "data" variable and get it under the "junctionMatrix" attribute.  Pretty simple misunderstanding on my part!  Thanks again. ... View more