Map from Layout Template (.pagx) Correct Source, Broken Path(s)

ZacharyUhlmann1

As the title suggests, when I load a template created from another project into a new project (as is probably always the protocol) and open the map, all the Data Sources are broken.  However when I inspect the properties (Properties --> Source), the paths are displayed correctly.  To fix this, I go and "Change Data Source" or  click the Broken Source red exclamation point and...provide the exact same source (?).

It's systemic, but for information, these are either feature classes from FGDB or shapefiles.

I recently upgraded from 3.0.2 to 3.3.4, and this is new behavior. Has anybody experienced this?  Guessing it's a bug.

EDITED - this was a pagx file NOT lyrx...

thanks,

Zach

 

ZacharyUhlmann1

I submitted a help ticket to ESRI and was grateful for a response and help.  Turns out it's not the line endings, it's a case-sensitivity thing either introduced in Python or the ESRI Python Toolbox.  I suspect the latter for reasons discussed at end, but ultimately I deviated from the Template  at some point in the past and proceeded to cut and paste into most of my Python Toolboxes.  Therefore my problem is probably unlikely to affect anybody else.  I constructed the Toolbox class spelled "ToolBox" and it should be "Toolbox" (notice camel casing in former).

Here is the problematic line that broke my Toolbox:

# Notice the CamelCasing in ToolBox
class ToolBox(object):
    def __init__(self):

According to documentation / template, it should be this:

# Notice no camel casing - just Toolbox
class Toolbox(object):
    def __init__(self):
update_map_series]

 The reason I suspect it's not caused directly by Python updates between minor versions is because 1) PEP8 specifications recommend CamelCasing for Class Names, and 2) my Python Toolboxes functioned when employing Camel Casing to other Python Toolboxes in testing.  

Note that simply changing the spelling to Toolbox fixed all my Toolboxes.