ArcGIS Pro 2.5 crashes when adding a Territory Design Layer Solution to the map (using arcpy)

237
5
Jump to solution
03-12-2020 04:47 AM
Roxana_ElenaUrdea
New Contributor III

Hi,

I am having an issue related to the Territory Design Solution Layer with ArcGIS Pro 2.5.

ArcGIS Pro crashes (with no error) after I create a Territory Solution and trying to add it on the map. I happens from both python and model builder.

As an example, my arcpy code is the following (I'am using a Python Toolbox):


def getParameterInfo(self😞
out_territory_design_solution = arcpy.Parameter(
displayName="Output Territory Design Solution",
name="out_territory_design_solution",
datatype="GPGroupLayer",
parameterType="Derived",
direction="Output")
-----------------------
def execute(self):
territory_solution = arcpy.CreateTerritorySolution_td(in_features=Feature_Layer,
solution_name=in_territory_solution_name,
id_field="",
name_field="",
territory_level_name="{}".format(territory_level_name),
default_territory_name="{} %Number%".format(
territory_level_name))

out_territory_design_solution.value = territory_solution[0]

ArcGIS crashes when trying to assing the territory_solution layer to my output variable.

Same behavour when creating a mode in model builder and flag the output territory level with AddToDisplay.

Any ideas?

Thank you,

Roxana

Reply
0 Kudos
1 Solution

Accepted Solutions
DanielLee2
New Contributor III

Hi Roxana, we have identify the bug and the fix should be available in the next release of ArcGIS Pro (2.6).

View solution in original post

5 Replies
DanielLee2
New Contributor III

Hi Roxana. Thank you for the post. We are currently looking into the issue. I will post a response as soon I get an answer.

Roxana_ElenaUrdea
New Contributor III

Thank you Daniel, I am wainting forward for your feedback.

DanielLee2
New Contributor III

Hi Roxana. I think we have figured out the problem. There is a bug and we are currently in the process of fixing it. I will let you know when we have a fix.

Roxana_ElenaUrdea
New Contributor III

Good news Daniel, thank you! We are looking forward for the fixing!

Reply
0 Kudos
DanielLee2
New Contributor III

Hi Roxana, we have identify the bug and the fix should be available in the next release of ArcGIS Pro (2.6).

View solution in original post