Latest Contributions by BlytheSpendlove

‎01-25-2022

I vote the latter, adding express map functionality to the map viewer, so that the data in the maps can be re-used in different apps.

‎01-25-2022

@OwenGeo Am I correct in assuming though that there is no way to get the spatial data that was created in an express map and move it over into a real map that can be re-used in other applications?

‎07-21-2021

Hi @BillFox It gives the normal red failure message in the dialog box, but in the developers console, I found a CORS error message. I am thinking there might have been an issue with the symbology image the layer was referencing. As in, referencing the symbology image directly in the json gives issues, but having the feature service reference the symbology (as it's default symbology) does not give the same issue. The issue may also be related to a broader, more general problem we have confirmed, where the print service has intermittent to constant (depending on the layer) issues printing external feature services that we have hosted in our portal (no useful error messages in the developers console for this one). We've narrowed down that the issue is limited to just hosted external services (particularly ones that have passwords saved in the item details). The issue also does not happen in AGOL, just in Enterprise. I'll be opening a ticket today with Esri, I'll let you know if they are able to help me pin down the issue any further.

‎07-08-2021

Thanks @BillFox ! I'll mention that idea to my IT counterpart who is helping me troubleshoot this issue.

‎07-08-2021

Thanks @ThomasJones1 I'll look into that and gather more information.

‎06-30-2021

Background: I am in charge of a map for my organization that utilizes a lot of external data. If it is data that requires an ArcGIS Online subscription (like Living Atlas Data) we create a new layer in the portal by going to My Content > Add Item > From a URL > ArcGIS Sever web service. This way, we have a portal content item in our enterprise environment where we can save the ArcGIS Online password, and not require all of our users to sign into ArcGIS Online to use the layer. Problem/Question: Unfortunately, some of these password-protected-external-layers / 'Url-added-feature-layers' (not sure what to call these) have trouble with the print widget in our web apps and I've seen some really weird behavior. I am looking for help with troubleshooting the following situation in particular: For our internal version of the USA_Wildfires_v1 layer I could print one of the layers in the feature service but not the other. Turns out, for the problem causing layer, I needed to go into the JSON of the map and remove the "layerDefinition" - after doing this I could print the layer. (https://services9.arcgis.com/RHVPKKiFTONKtxq3/arcgis/rest/services/USA_Wildfires_v1/FeatureServer) I've been troubleshooting and it seems like, at least for some of the problem layers, removing the "layerDefinition" from the layer in the map's JSON ((and instead having the map and print widget just reference the default feature service symbology) fixes the issue. Why is that? Could an old way that the Web Viewer used to create layer definitions cause problems with the current print service? Or could it be due to the print service not being able to reconcile what the service is saying the layer definition is versus what the map is saying? Follow up Question: Does that (situation above) mean I can't have any "layerDefinitions" on these external layers if I want to be able to print them? Thanks, Blythe Spendlove

‎06-28-2021

Hi Jess I had a similar problem. I am in an Enterprise Environment, and while the print service was working fine with normal internal feature layers, for any external layers (like from Living Atlas) where we entered an ArcGIS Online username to hardcode access (so that individual users of the web app don't have to enter their passwords), the print widget was throwing errors. Sharing our portal items for those external layers 'to the public' fixed the problem for us. It doesn't really share the layers to the public, since we are in an internal environment, just to our organization.

‎06-28-2021

Hi Kevin, I had this same problem. I am in an Enterprise Portal environment, and had to share the living atlas layer with "the public" for the print service to successfully print the layers. I don't know how it works however outside of an Enterprise Portal environment.

‎06-25-2021

Hi Chris, When you say.... "Make sure the service is set to "dynamic" in the flex main config file and not a "feature" service." ...why can't the layer be a feature service? I am trying to add labeling to a feature service and the map service version of it shows the labels but not the feature service. Is there some limitation with the feature services and labeling? Thanks!! Blythe

‎06-23-2021

Thanks Craig!

‎06-23-2021

@CraigGillgrass

‎06-23-2021

I am looking for this type of functionality as well. Until this is possible I don't see Workforce being very useful for my projects, since my organization tries to avoid publishing a bunch of hosted data to our enterprise portal site (versus registering company databases)

‎06-23-2021

Yep. We are seeing this error too. Seems related to and/or the same problem as this: https://community.esri.com/t5/arcgis-online-questions/intermittent-504-gateway-timeouts-with-hosted-feature-layers/m-p/1071472#M40891

‎06-03-2021

Ahh I just saw that this is on ArcGIS Online. You may not be able to change the default colors in ArcGIS Online. I am using the Custom Web App Builder.

‎06-03-2021

Hi @PaulTrimble1 when you change the LaunchpadTheme 'styles' it switches between default, style2, and style3 in the app (\\location of app\custom app name\themes\LaunchpadTheme\styles). The default style color is "default" and has the colored launchpad anchor bar buttons. Either style2 of style3 is what it is switched to when changing the theme to have a custom color. The config that defines the colors shown in the 'colorful' anchor bar is located here: \\app location\app name\themes\LaunchpadTheme\styles\default\css\jimu-theme.css To change the colors/orders in the colorful theme, you change the .icon-item-background0, background1 etc. colors. That css file delineating the .icon-item-background colors for the anchor buttons does NOT change between default, style2, and style3, so I am guessing that instead you will have to search through the default folder for code that references icon-item-background, and then compare that file to what the same file shows for style2/style3. My guess is that at some point along the code, instead of telling it to pick a color based on the color index discussed above, it instead just hardcodes in a grey color.

Online Status	Offline
Date Last Visited	Friday

My Ideas

Latest Contributions by BlytheSpendlove

Re: Ability to include data in Express Maps

Re: ReUse an Express Map in StoryMaps

Re: Unable to Print Password Protected External Layers (url added to Portal as a new item) when using a LayerDefinition

Re: Unable to Print Password Protected External Layers (url added to Portal as a new item) when using a LayerDefinition

Re: Unable to Print Password Protected External Layers (url added to Portal as a new item) when using a LayerDefinition

Unable to Print Password Protected External Layers (url added to Portal as a new item) when using a LayerDefinition

Re: Web App builder - Print widget error message

Re: Unable to print from the Map Viewer if the web map contains the living atlas layer

Re: Labels not appearing in published map service

Re: How can I bring in the data from the Workforce layers into a geodatabase?

Re: How can I bring in the data from the Workforce layers into a geodatabase?

Re: How can I bring in the data from the Workforce layers into a geodatabase?

Re: 504 error (gateway timeout) during ArcGIS Python API query of related records

Re: Theme custom background style settings not applying in AGOnline WAB

Re: Theme custom background style settings not applying in AGOnline WAB

Re: Web App builder - Print widget error message

Re: Invalid url when trying to sign in to Portal

Re: Invalid url when trying to sign in to Portal

Coronavirus disease 2019 (COVID-19)