topic Re: Loss of renderer with runtime-created data source in ArcGIS Experience Builder Questions

Loss of renderer with runtime-created data source

jwilner_amica — Wed, 18 Sep 2024 13:36:24 GMT

Following this post, I created a DataSource from a programmatically generated FeatureLayer.

https://community.esri.com/t5/arcgis-experience-builder-questions/making-runtime-featurelayers-register-as/m-p/1473175#M12641

However, when that DataSource is added to map, it loses its renderer that was defined before. The renderer being used displays some color never used in my UniqueValueRenderer. The code is as follows:

let layer = new FeatureLayer({

source: featureset, // autocast as a Collection of new Graphic()

objectIdField: "OBJECTID",

geometryType: "polygon",

popupTemplate: template,

fields: swath.value.fields,

title: 'Hail Swath ' + dt,

opacity: 0.8

})

layer.renderer = {

type: "unique-value", // autocasts as new UniqueValueRenderer()

// @ts-ignore

field: "diameter_in_label",

defaultSymbol: {

type: "simple-fill",

outline: line,

color: [209, 0, 152, 1.0]

uniqueValueInfos: [{

value: '0.75"',

symbol: {

type: "simple-fill", // autocasts as new SimpleFillSymbol()

color: [255, 255, 190, 1.0],

outline: line

}

}, ... ** Omitted long renderer **

}]

}

const data: DataSourceJson = {

id: 'Hail Swath ' + dt,

layerId: layer.id,

type: DataSourceTypes.FeatureLayer,

label: layer.title,

}

const dataJson = Immutable(data)

const dataSourceOptions = {

id: 'Hail Swath ' + dt,

layer: layer,

dataSourceJson: dataJson,

}

dsManager.current.createDataSource(dataSourceOptions).then((source) => {

const sourceId = source.id

const addMapData = {

jimuMapViewId: map.current.id,

dataSourceId: sourceId,

dataChangeType: DataChangeType.Create,

dataChangeStatus: DataChangeStatus.Fulfilled

}

let mapDatas = { sourceId: addMapData }

map.current.addOrRemoveDataOnMap(mapDatas)

}).catch((error) => {

console.error('Error creating DataSource:', error);

});

Any help would be appreciated, thank you!

Re: Loss of renderer with runtime-created data source

jwilner_amica — Wed, 18 Sep 2024 13:49:51 GMT

When logging my DataSourceManager (dsManager) immediately after the 'addOrRemoveDataOnMap(mapDatas)' line, I get the renderer displayed as such:

So it does seem to be there, but not taking any effect.

Re: Loss of renderer with runtime-created data source

JeffreyThompson2 — Wed, 18 Sep 2024 13:58:52 GMT

I think that because your render is not defined within the DataSourceJson, it is triggering the layer to load with the default renderer. Try moving the layer.renderer = {...} below adding it to the map, so it will first load with the default renderer and then get the unique values.

Re: Loss of renderer with runtime-created data source

jwilner_amica — Wed, 18 Sep 2024 14:18:11 GMT

Unfortunately,

map.current.addOrRemoveDataOnMap(mapDatas)

layer.renderer = {**Omitted renderer**}

did not seem to solve the issue. I also tried putting both lines into a timeout, as you did in the original post, as well as putting the layer.renderer overwrite alone into a timeout, to ensure that the update occurred after the add to map, but neither seemed to have any effect. Is there a way to specify the renderer directly in the DataSourceJson? I couldn't seem to find one, but it is possible I overlooked something. Thank you for your help, you have quite a wealth of knowledge with the ExB developer system!

Re: Loss of renderer with runtime-created data source

jwilner_amica — Wed, 18 Sep 2024 19:03:16 GMT

Re: Loss of renderer with runtime-created data source

JeffreyThompson2 — Wed, 18 Sep 2024 14:38:25 GMT

I am currently working on an update to my add/remove layers widget that will register the layers as datasources. I should have it out later today.

https://community.esri.com/t5/experience-builder-custom-widgets/add-remove-layers-by-group/m-p/1295061#M70

While working on the problem linked to in your original question, I found an issue in that code that adding the datasource causes an additional datasource enabled layer to be added to the map and there were issues with conflicting ids. I think your code could have a similar problem. My widget works by adding the layer (not as a datasource) to the map, using that layer to make a datasource with a different id and then deleting the original layer.

Re: Loss of renderer with runtime-created data source

jwilner_amica — Wed, 18 Sep 2024 14:41:54 GMT

I will look through that, thank you!

Re: Loss of renderer with runtime-created data source

jwilner_amica — Wed, 25 Sep 2024 18:35:48 GMT

Got a functional result. Rather than adding DataSource to map, add the FeatureLayer, then add that FeatureLayer to a JimuLayerView, specifying creation during runtime ('true' flag in constructor). Use the DataSource id created earlier in the JimuLayerView constructor as well. Symbology transfers and has datasource functionality:

dsManager.current.createDataSource(dataSourceOptions).then((source) => {

const sourceId = source.id

const addMapData = {

jimuMapViewId: map.current.id,

dataSourceId: sourceId,

dataChangeType: DataChangeType.Create,

dataChangeStatus: DataChangeStatus.Fulfilled

}

map.current.view.map.add(layer)

map.current.createJimuLayerView(layer, map.current.id, 0, source, true)

}).catch((error) => {

console.error('Error creating DataSource:', error);

});

ExB 1.15 Bug:

Layer loses DataSource functionality upon reorder

https://community.esri.com/t5/arcgis-experience-builder-questions/loss-of-runtime-created-datasource-functionality/m-p/1541505#M15032

Re: Loss of renderer with runtime-created data source

jwilner_amica — Wed, 18 Sep 2024 18:37:05 GMT

@JeffreyThompson2 Got a functional datasource add, may make your widget a bit cleaner than add-remove, but could still use some testing. Hope this can help!

Re: Loss of renderer with runtime-created data source

YueyangLi — Tue, 24 Sep 2024 06:26:02 GMT

Hi @jwilner_amica,

The addOrRemoveDataOnMap method should be private. It creates a graphic layer based on the records from the data source, which explains why the renderer isn't functioning properly. We will update the code accordingly.

If you'd prefer to create the data source first and then add it to the map, you can use jimuMapView.addLayerToMap(dsId, customLayerId).

I hope this helps.

Re: Loss of renderer with runtime-created data source

MohammedHilal_K — Wed, 16 Oct 2024 03:29:42 GMT

When I use jimuMapView.addLayerToMap(dsId, customLayerId) inside a loop, the DataAction ("Add to Table") works only for the last item in the array. If I add a single layer, the data action works perfectly. I've noticed this behavior in both Experience Builder versions 1.14 and 1.15.

However, when using addOrRemoveDataOnMap, I don't encounter this issue, but the layer ordering doesn't follow the intended sequence. In contrast, with addLayerToMap(), I can use await since it returns a promise.
Any help?

Re: Loss of renderer with runtime-created data source

QunSun — Wed, 16 Oct 2024 07:07:56 GMT

@MohammedHilal_K Can you try calling jimuMapView.addLayerToMap() serially to solve this problem? Similar to the following code

async function addMultipleLayersToMapOneByOne(items) { for (const item of items) { const { dataSourceId, targetLayerId } = item; await jimuMapView.addLayerToMap(dataSourceId, targetLayerId); } }

Re: Loss of renderer with runtime-created data source

MohammedHilal_K — Wed, 16 Oct 2024 09:15:15 GMT

@QunSun @jwilner_amica
still Not working. Also in targetLayerId, what Id it actually required? I'm using 'Wolrd Hillshade' as basemap with no predefined layers.
Also below code works for me for MapImageLayer and FeatureLayer. but what about FeatureService? how can we pass the FeatureService to createJimuLayerView?

jimuMapView.view.map.add(featureService)
jimuMapView.createJimuLayerView(featureService, jimuMapView.id, index, dataSource, true)

am creating feature service using below code, but after added to the map, data action(add to table ) is not available.

await Layer.fromArcGISServerUrl({

url: url

})

Any help?

Re: Loss of renderer with runtime-created data source

YueyangLi — Fri, 18 Oct 2024 07:10:11 GMT

@MohammedHilal_K

targetLayerId is a custom ID you want to set to the layer, as long as you ensure that the ID does not conflict with other layer IDs.

The data action (add to table) is available only for the data sources supporting the query. Layer.fromArcGISServerUrl(featureServiceUrl) will return a Maps SDK group layer, that doesn't support query. The workaround is adding the layers/tables under the feature service individually.