Network Analyst - Directions' description is missing when default configuration is altered

[Rajkaran_Beans]

Hey Team, 

We recently started using ArcGIS Indoors Model and found a weird situation where directions' description leave elements when default configuration is altered.

For example, 

Situation 1 -  Once Network Dataset is cretaed and a route is solved which includes a transision, description is "take the elevatio up to LEVEL #"

Situation 2 - When any part of this description is altered from Network Dataset > Properties > Description (It doesn't matter what you change, any slight change from default) will miss the LEVEL element from description. Descripton from Altered configuration is "take the elevatio up"

Attaching a side by side image for comparision:



@sri_krishnahari 
 

[AryamanBhattacharya_BeansAI]

Hey @MelindaMorang , 

Greetings! Hope you are well and thank you for addressing BUG-000169839 which we reported through this community post. We have upgraded to ArcGIS Pro 3.4 and no longer experience the issue. 

However, we have observed the same behavior when consuming the dataset as a Network Analysis service to solve routes on ArcGIS Enterprise 11.1. Is this expected ? 

Regards,

Aryaman

Cc: @Rajkaran_Beans @sri_krishnahari 

[MelindaMorang]

Yes, unfortunately, this makes sense to me.  Enterprise is based on the ArcGIS Pro codebase, and Enterprise 11.1 used the Pro 3.1 codebase (I think).  At any rate, your version of Enterprise is older and doesn't have the fix we made in Pro 3.4.  You would have to update to Enterprise 11.4.

[AryamanBhattacharya_BeansAI]

Makes sense to me too. Let me try testing on a 11.4 version of ArcGIS Enterprise and see if the defect is fixed there. 

Thank you for the information! 

Regards,

Aryaman

[MelindaMorang]

I had posted a potential workaround, but then one of the developers on my team advised me that it may lead to other issues, so we don't recommend trying it after all.  I deleted my comment.  Sorry for the confusion.

[MelindaMorang]

Hi, just wanted to give an update.  We have fixed the issue, and the fix will be available in the upcoming Pro 3.4 release.  Unfortunately, although the updated network will work properly in Pro 3.4+, it will still have the same problems in older versions of Pro.  We have flagged the issue as a candidate for future patches of older Pro versions.