We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why is JourneyPart_VersionStructure extended to DataManagedObjectStructure instead of VersionedChildStructure?
The text was updated successfully, but these errors were encountered:
probably to benefit the possible Branding (and more recently PrivateCodes)
Sorry, something went wrong.
I think it places it in the wrong part of the object hierarchy, there are more examples like this.
Aurige
No branches or pull requests
Why is JourneyPart_VersionStructure extended to DataManagedObjectStructure instead of VersionedChildStructure?
The text was updated successfully, but these errors were encountered: