nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Utility Network Shape Length and ArcGIS Dashboards

TheRrrr42

Hello all!
We noticed that one of our dashboards using a query layer was giving us trouble after moving to the UN. This was due to query layers of Branch Versioned Features including all of the edits that had been done against the database inflating some of our milage numbers. We are now looking at reworking the dashboard using some other services based off of our UN Features. However, we have noticed that we are experiencing BUG-000147447:

In ArcGIS Dashboards, attempting to use an indicator to sum the Shape_Length field of a service published from a feature class participating in a utility network fails with the error message, "Cannot access data." returned.

I was curious if anyone else has a solution or work around to getting a UN Shape_Length to play nice inside of a dashboard?

Best,

Ricardo

Najděte více příspěvků označených jako

Accepted answers

RobertKrisher

As discussed in the Water User Group meeting, some users are working around this limitation using the measuredlength field in their model. Because this is a bug this will be fixed, check the support page for the bug to see what version includes the fix and where it has been patched.

All comments

TheRrrr42

Thanks James! We ended up doing the same, not the most performant but it should let us bridge the gap until this works natively in 12.1.

JamesRains

Instead of creating a separate field for the length, we used Arcade to create an array that sums the Shape_Length fields and included any other necessary fields for our dashboard.

// Write an expression that returns a FeatureSet.

var fs = FeatureSetByPortalItem(

Portal('<insert portal address>'),

'27a5912865834591bbddbf97066f9c56',

39,

['SHAPE.STLength()', 'LIFECYCLESTATUS', 'FEEDERID', 'ASSETTYPE'],

false

);

// Build an array of new features

var features = [];

for (var f in fs) {

var lifestatus = f["LIFECYCLESTATUS"];

if (lifestatus == 'ACT'){

var FeederID = f["FEEDERID"];

var AssetType = f["ASSETTYPE"]

var lengthFeet = f["SHAPE.STLength()"];

var lengthMiles = Round(lengthFeet / 5280, 2)

Push(features, {

attributes: {

length_miles: lengthMiles,

length_feet: lengthFeet,

FeederID: FeederID,

AssetType: AssetType,

});}

}

// Define the fields (include the new one for miles)

var convertedValues = {

fields: [

{ name: 'length_miles', type: 'esriFieldTypeDouble' },

{ name: 'length_feet', type: 'esriFieldTypeDouble' },

{ name: 'FeederID', type: 'esriFieldTypeString' },

{ name: 'AssetType', type: 'esriFieldTypeSmallInteger'}

geometryType: '',

features: features

};

return FeatureSet(convertedValues);

RobertKrisher

That's something you'd need to reach out to support on. The original issue that was logged was actually fixed last year, but this separate issue was separate out because there is also a branch versioning specific aspect to this.

NathanWolfe

Is there any sort of estimate of when this might be fixed? It looks like it's been a known bug since March of 2022...

https://support.esri.com/en-us/bug/in-arcgis-dashboards-attempting-to-use-an-indicator-to-bug-000147447

RobertKrisher

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.