Ftrack: Fix occational double parents issue #4153
Merged
+8
−14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Brief description
Fix issue when asset has doubled last parent.
Description
The issue happens when mongo id is not filled in ftrack but entity exists in mongo. Source of issue is because of loggins path of entity which adds parent's name to parens to log it's path but did not create copy of parents list.
Additional information
The issue happened in most of cases during editorial publishing where both ftrack and mongo entities are created and ftrack did not fill mongo id in custom attributes.
Testing notes:
ftrackIdfrom assets data in mongoNOTE: Second sync form ftrack would fix the issue so make sure you sync only once after values removement.