Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

"jcr:mixinTypes" property getting removed from child nodes

Avatar

Avatar
Validate 1
Level 1
KhanIshaq
Level 1

Likes

0 likes

Total Posts

7 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
KhanIshaq
Level 1

Likes

0 likes

Total Posts

7 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile
KhanIshaq
Level 1

10-03-2019

Hi All,

We have a custom component, that have child node with "multifield". When we performing any authoring on component, "jcr:mixinTypes" property is getting removed.

Screenshot 2019-03-11 at 10.23.28 AM.png

If we opening authoring dialog and saving it back, "jcr:mixinTypes" property is getting removed.

Screenshot 2019-03-11 at 10.24.21 AM.png

This is happening on all component with similar structure.

Any suggestion for this scenario will be very helpful.

Thanks

Replies

Avatar

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile
smacdonald2008
Level 10

11-03-2019

What AEM version are you using. Also what multifield granite type are you using.

Avatar

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,118 likes

Total Posts

3,149 posts

Correct Reply

1,073 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,118 likes

Total Posts

3,149 posts

Correct Reply

1,073 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile
Jörg_Hoh
Employee

11-03-2019

I can only imagine the case that you have a strange MSM rollout config, which is triggered by any change. Do this happen only on MSM livecopies? What happens if you author MSM blueprints?

Jörg

Avatar

Avatar
Validate 1
Level 1
KhanIshaq
Level 1

Likes

0 likes

Total Posts

7 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
KhanIshaq
Level 1

Likes

0 likes

Total Posts

7 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile
KhanIshaq
Level 1

11-03-2019

Hi smacdonald2008

We are using Adobe Experience Manager (6.2.0.SP1) and granite/ui/components/foundation/form/multifield

Thanks

Ishaq

Avatar

Avatar
Validate 1
Level 1
KhanIshaq
Level 1

Likes

0 likes

Total Posts

7 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
KhanIshaq
Level 1

Likes

0 likes

Total Posts

7 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile
KhanIshaq
Level 1

11-03-2019

These properties are populating after rollout, so blueprint page it self do not have these properties.

Thanks

Ishaq

Avatar

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,118 likes

Total Posts

3,149 posts

Correct Reply

1,073 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,118 likes

Total Posts

3,149 posts

Correct Reply

1,073 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile
Jörg_Hoh
Employee

12-03-2019

ok, this behavior is affecting only the livecopies? Have you broken the MSM inheritance to perform changes via UI? Or are you just doing the changes via CRXDE?

Avatar

Avatar
Establish
MVP
Veena_Vikram
MVP

Likes

471 likes

Total Posts

1,039 posts

Correct Reply

121 solutions
Top badges earned
Establish
Coach
Contributor 2
Seeker
Ignite 5
View profile

Avatar
Establish
MVP
Veena_Vikram
MVP

Likes

471 likes

Total Posts

1,039 posts

Correct Reply

121 solutions
Top badges earned
Establish
Coach
Contributor 2
Seeker
Ignite 5
View profile
Veena_Vikram
MVP

12-03-2019

I agree with Jorg. I also feel this is caused due to something in the MSM configurations. Do you have any custom roll out configs which might be affecting this ?

Avatar

Avatar
Validate 1
Level 1
KhanIshaq
Level 1

Likes

0 likes

Total Posts

7 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
KhanIshaq
Level 1

Likes

0 likes

Total Posts

7 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile
KhanIshaq
Level 1

12-03-2019

Hey @Jörg Hoh

We have hierarchy like Blueprint > Source Pages > LiveCopies , and this behaviour is for both source pages and livecopies. As "jcr:mixinTypes" property is getting added after rollout from blueprint to source pages or from source pages to livecopies, so "jcr:mixinTypes" only exist on source pages or livecopies, not on  blueprint page.

Yes we are broking the msm inheritance to perform changes via UI.

Avatar

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,118 likes

Total Posts

3,149 posts

Correct Reply

1,073 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,118 likes

Total Posts

3,149 posts

Correct Reply

1,073 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile
Jörg_Hoh
Employee

13-03-2019

Do I understand you right that you have a 2-level MSM Inheritance

Level 1: blueprint 1 -> Livecopy 1 (you call it "source pages")

Level 2: Livecopy 1 -> Livecopy 2

Is that correct? Can you reproduce this behavior on both Level 1 and Level 2? Or only on a single one of them?

I experienced some weirdness when you use multiple inheritance levels and combine it with "unusal" rollout actions and triggers (maybe even custom ones). There might be assumptions made in an rollout action which cannot handle the case that a livecopy is also a blueprint.

For this case I would be good if you check the triggers and rollout actions on both Level 1 and Level 2 (see above).

Avatar

Avatar
Validate 1
Level 1
KhanIshaq
Level 1

Likes

0 likes

Total Posts

7 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
KhanIshaq
Level 1

Likes

0 likes

Total Posts

7 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile
KhanIshaq
Level 1

26-03-2019

Yes correct, we have two level of inheritance. And we are facing issue on both level 1 and level 2.

But the rollout action on both are same.