POST
|
Eric and Chris, thanks for taking the time to figure this out. Glad to know I wasn't just doing something wrong. I agree that it is very frustrating to have this bug on live solutions being promoted as a super easy way to create a new app. I was able to create another different solution as a test but the one I actually wanted (any of the capitol projects solutions) never worked. Ultimately it took less time to create my own services and app using ArcGIS online tools than I spent chasing what turned out to be a bug. Love the idea of the solutions and I hope you do get this bug sorted.
... View more
07-30-2018
02:31 PM
|
0
|
0
|
233
|
POST
|
I am trying to use the arcgis solutions deployment tool for the first time and I keep getting this error. (none type object has no attribute type) see screen shot. I cant find anything about it. Anyone seen this before?
... View more
06-28-2018
10:46 AM
|
1
|
12
|
2064
|
POST
|
I actually found another forum that seems to have a working solution for this that does not require recreating your features. It appears that this bug is caused by adding new fields to a feature. If there are any fields after the default esri fields ArcGIS online will not behave properly. After I went into my MXD and reordered the fields so all esri fields are the last to appear in the field order and republished the ability to configure the pop-up was restored. I did notice that if I was configuring the popups for my web map and I hit upon a broken layer I could no longer configure popups for any other layers until I closed out of the web map and reopened it so save often. Still not the ideal situation but much easier than rebuilding features entirely.
... View more
03-07-2018
08:36 AM
|
1
|
1
|
905
|
POST
|
I have been having this issue frequently lately. It happens every time we change the layer order in an MXD that is being used in an arcgis online map. It is a pain to have to completely delete and republish and re add everything to the web map and it still doesn't clear reliably. It feels an awful lot to me like the issue that used to exist in the flex viewer where the layers and attributes in the layers had a number assigned to each attribute class and adding anything to the webmap would throw the numbering into chaos. I say this because we have noticed that sometimes if we do not republish it pulls the attribute data from the wrong layer when you click on a feature. It should not be breaking every time you add a new attribute or layer to an mxd that is being used in an online service. I think this is a software bug.
... View more
03-06-2018
07:45 PM
|
0
|
5
|
905
|
POST
|
I am also having this issue. What ended up being the resolution for you?
... View more
09-27-2017
07:16 AM
|
0
|
0
|
475
|
Title | Kudos | Posted |
---|---|---|
1 | 03-07-2018 08:36 AM | |
1 | 06-28-2018 10:46 AM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:25 AM
|