Timeline for Sitecore serialization package installation removes custom roles
Current License: CC BY-SA 4.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Nov 17 at 17:39 | comment | added | Marcel Gruber |
Additional note: as @ChetCheeto mentioned, when a package is generated, SCS packages the items in the serialization folder. However, SCS leaves roles in the path specified in defaultModuleRelativeSerializationPath . When you install the package, SCS only uploads from the serialization folder and therefore ignores the roles, but since they are defined in the module.json file(s), it deletes them from Sitecore. The takeaway is that you should use the default path settings if you want to serialize roles.
|
|
Nov 16, 2023 at 22:04 | comment | added | Chet Cheeto |
I've also documented similar behavior when the defaultModuleRelativeSerializationPath is set to something like "items" . When I created the item package, all of the standard content ended up in a folder named serialization regardless of the sitecore.json configuration. The roles, however, respected this configuration and were put into a folder named items . When I changed the the defaultModuleRelativeSerializationPath to "serialization" , this allowed the roles to be installed within the content package.
|
|
Apr 7, 2023 at 17:39 | vote | accept | Serhii Shushliapin | ||
S Apr 7, 2023 at 14:14 | review | First answers | |||
Apr 7, 2023 at 14:42 | |||||
S Apr 7, 2023 at 14:14 | history | edited | Mathijs Bannink | CC BY-SA 4.0 |
deleted 19 characters in body
|
Apr 7, 2023 at 14:12 | review | Late answers | |||
Apr 7, 2023 at 14:42 | |||||
Apr 7, 2023 at 14:12 | history | edited | Anna Bastron | CC BY-SA 4.0 |
code formatting
|
Apr 7, 2023 at 14:04 | history | edited | Sumit Helaiya | CC BY-SA 4.0 |
Fixed grammer and improved formatting.
|
S Apr 7, 2023 at 13:55 | review | First answers | |||
Apr 7, 2023 at 14:12 | |||||
S Apr 7, 2023 at 13:55 | history | answered | Mathijs Bannink | CC BY-SA 4.0 |