Latest Contributions by mpboyle

@BernSzukalski  Whether it's a feature service published from ArcGIS Server or a hosted feature layer on AGO, the fields list popup defaults to showing attributes in alphabetical order, rather than respecting the order of the service. Below are examples.  The second example is for a commercial building hosted feature layer.  All the fields at the beginning (top) of the service order have to do with the associated parcel (parcel identifier, address, owner, class, etc...).  Those fields are scattered throughout the default fields list popup and I have to manually re-order the attributes to get them back in the desired order. ArcGIS Server (feature layer service) --- service field order on left, default fields list popup on right.   ArcGIS Online (hosted feature layer) --- service field order on left, default fields list popup on right. ... View more

@BernSzukalski  I'm all for creating popups that are enjoyable to lookup by using custom text, but that's not going to be used in all cases, maybe not even the majority.  There are several times where I want a simple list of attributes that flow in a logical order, which has already been done at the feature layer or service level. Having to scroll up and down the fields list to re-order attributes back to that logical order is a waste of time, not to mention frustrating when I've already taken the time to do it and then have that order ignored. ... View more

I completely agree with @Heather_Hegi  ... the desktop environment is where the schema considerations are done. Do once, apply many times. At the minimum, provide an option/checkbox for displaying the field list in the default schema order. ... View more

4 years later...please, for the love of God, remove alphabetical ordering by default ... View more

Maybe this is because it's the draft version...?  If I view the published version, it seems to work as expected. ... View more

In case anyone else comes across this issue, what we found was that NULL values in the vector tile style JSON seemed to be causing the issue.  Once the NULL values were removed, we were able to successfully print from the map viewer or ExB. Below is an example of what seemed to be causing our issue: ... View more

We just noticed a similar issue.  After the February 2026 update, printing in the Map Viewer or ExB using the default print service does NOT work if the map contains one of our own hosted vector tile layers. If I turn off the vector tile layer or switch to an Esri provided base map, printing works. If I replace our existing hosted vector tile layer, printing still doesn't work. If I add a vector tile package, publish, and add the resulting hosted vector tile layer, printing works.   This seems less than ideal.  We use AGO hosted vector tiles for many of our basemaps.  It seems to get them working again, we may need to re-create all our styles, and then update all the web maps used as our base maps?!?  That is assuming newly created styles work with printing. Esri support has been able to duplicate our issue on their end. ... View more

Did some quick testing... If I follow our existing workflow of: adding a new vector tile package, publishing it, and then replacing our existing vector tile layer used for our base maps, I still get an error. If I publish the same updated vector tile package, and add the resulting hosted vector tile layer to a web map, printing works.   This is less than ideal.  It seems to get printing working we may need to re-create all our styles, and then update the web maps used as our base maps?!?  This is assuming creating a new style works when printing. ... View more

Below is a a Python script that will overwrite the configuration of the "target" experience using the configuration from the "source" experience. In my testing, I created a very basic experience as my "target", and overwrote it using the config from one of our developed experiences as the "source".  After running the script, the "target" experience looked, behaved, and had all the components of the "source" experience. This may be a way of easily updating one experience with another and not having to move URLs around.   Note: This does not update the "target" experience title, summary, description or any of its item properties.   !!! USE CAUTION AND BACKUP ANY ITEMS BEFORE TESTING !!!   In the code below, the following lines will need to be updated: 6, 7, 8, 11, 13, 15 (optional) import arcgis import json from pathlib import Path # portal variables PORTAL_URL = r'...url...' PORTAL_USER = '...user name...' PORTAL_PASSWORD = '...user password...' # source experience item id (load from) ITEM_ID_SOURCE = '...item id...' # target experience item id (load into) ITEM_ID_TARGET = '...item id...' # optional --- writes source experience config to file WRITE_SOURCE_CONFIG = True if __name__ == '__main__': # connect to portal portal = arcgis.GIS(url=PORTAL_URL, username=PORTAL_USER, password=PORTAL_PASSWORD) # get source experience item item_source = portal.content.get(itemid=ITEM_ID_SOURCE) # get target experience item item_target = portal.content.get(itemid=ITEM_ID_TARGET) # get source config config_source = item_source.get_data() # write source config? if WRITE_SOURCE_CONFIG: # construct config file path root_dir = Path(Path(__file__).parent).resolve() config_path = root_dir / f'config__{ITEM_ID_SOURCE}.json' # write source config with open(file=config_path, mode='w') as f: print(f'Attempting to write item "{ITEM_ID_SOURCE}" config') json.dump(obj=config_source, fp=f, indent=4) print(f'Successfully created "{config_path}"') print('-' * 50) # update target item config print(f'Attempting to update item "{ITEM_ID_TARGET}" config') item_target.update(data=config_source) print(f'Successfully updated item "{ITEM_ID_TARGET}" config') print('-' * 50)   ... View more

@DougBrowning  Yep, I could see that being an issue, one of which the idea hopes to resolve...have a somewhat static URL for an app, but be able to import/load/swap a configuration from another experience. ... View more

@Zach-Williams  This is more for the hosted AGO version of ExB.  With Developer Edition, it's a lot easier to manipulate or copy/paste/replace the downloaded app with an existing one. ... View more