Currently, TransformationScenarios and TransformJobs import without accounting for the fact that TransformationScenario primary keys/ids and filepaths change, which leads to transforms not working with a mysterious message like 'NoneType has no attribute transform', and also leads to includes failing to be included, causing nonexistent-namespace issues.
Okay, turns out that for the primary keys, the issue is that the 'transformations' section of the job details dictionary just has a different format than the one the code assumes.
Currently, TransformationScenarios and TransformJobs import without accounting for the fact that TransformationScenario primary keys/ids and filepaths change, which leads to transforms not working with a mysterious message like 'NoneType has no attribute transform', and also leads to includes failing to be included, causing nonexistent-namespace issues.