Replies: 1 comment 2 replies
-
This is a huge architectural change, and can't just be included in a patch version. And for customers with several project portals, how would it work? I don't think we should do this to be honest. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the solution you'd like
Use content type hub instead of having a content type at Portfolio level that is disconnected at Project level.
This will make introducing new fields, renaming, etc... easier for customers as everything will be done through the content type hub.
There are already plenty of customers that has made changes toe content types, and have had to create scripts to introduce them to existing projects.
Alternatively create a greneral script that works like UpgradeAllSitesToLatest that does this job for customers that has made changes to content types or fields.
Beta Was this translation helpful? Give feedback.
All reactions