create_view Does not work if layer ids are not ordered sequentially

Question

Views created programmatically from services that have non-sequential layer ids are unusable. I created a view from this code:

source_search = gis.content.search("test_20240608_unique_ids_assigned_all_around")[0]
source_flc = FeatureLayerCollection.fromitem(source_search)

new_view = source_flc.manager.create_view(name="unid_all_around_view")

Source-Service layer ids:

View layer ids:

When the view is opened in the map viewer, the layers are messed up. The Route line layer has become a point layer and one of the point layers (the one with the very long name!) has become a line. A complete mess.

This happens consistently, on more than one platform. It does not happen when views are created manually. Also, create_view works fine when the layers are ordered sequentially 0 to N, top-down.

mikaël · Answer

As an alternative @RandyMcGregor_Home, you could always create your view by calling create_service(is_view=True) and then add_to_definition() to populate it.

It's what AGOL does when you create a view through the web page and it's what I've been doing because create_view() wasn't working for me.
I can share my code if it's something that interests you.

mikaël · Answer

Putting preserve_layer_ids to False solved it for me. The layer ids are not that important I guess because they're not hard-coded in my scripts, just my memory!
I'll have to change that! 😉
Thanks.

RandyMcGregor_Home · Answer

Thanks. I'll check that out. There is a 'preserve_layer_ids' property in the create_view method, but I haven't gotten it to accept True

create_view(name = viewName, preserve_layer_ids = True) throws an error. Replace True with False and it works but that's the default and not what I want for this.