Default metadata properties not getting set on uploading a new asset

Avatar

Avatar
Validate 1
Level 2
akshat_jain09
Level 2

Likes

6 likes

Total Posts

14 posts

Correct reply

1 solution
Top badges earned
Validate 1
Ignite 1
Give Back
Boost 5
Boost 3
View profile

Avatar
Validate 1
Level 2
akshat_jain09
Level 2

Likes

6 likes

Total Posts

14 posts

Correct reply

1 solution
Top badges earned
Validate 1
Ignite 1
Give Back
Boost 5
Boost 3
View profile
akshat_jain09
Level 2

14-05-2019

Hi All

I am facing an issue that the default metadata properties such as "cq:name" and "dam:baseVersion" are not getting set automatically on uploading a new asset.

Earlier this was working fine but now have stopped working. I am not sure what customization have lead to this.

Can someone please suggest what drives these values to the DAM?

I believed that some step in the DAM Update Asset Workflow drives this but now I am not sure on this part.

Thanks in Advance.

Regards

Akshat Jain

Replies

Avatar

Avatar
Give Back 50
Employee
berliant
Employee

Likes

207 likes

Total Posts

315 posts

Correct reply

98 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile

Avatar
Give Back 50
Employee
berliant
Employee

Likes

207 likes

Total Posts

315 posts

Correct reply

98 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile
berliant
Employee

14-05-2019

Did you apply a custom metadata schema or did you edit DAM update workflow?

What error if any do you see in an error.log?

Avatar

Avatar
Validate 1
Level 2
lovepreetk75597
Level 2

Likes

3 likes

Total Posts

24 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 1
Give Back 3
View profile

Avatar
Validate 1
Level 2
lovepreetk75597
Level 2

Likes

3 likes

Total Posts

24 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 1
Give Back 3
View profile
lovepreetk75597
Level 2

14-05-2019

Hi berliant​,

We have implemented a custom metadata schema also and customized the workflow as well.

There is no such log in the error.log related to this.

Can you suggest what drives these fields?

Avatar

Avatar
Give Back 50
Employee
Vish_dhaliwal
Employee

Likes

189 likes

Total Posts

356 posts

Correct reply

123 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile

Avatar
Give Back 50
Employee
Vish_dhaliwal
Employee

Likes

189 likes

Total Posts

356 posts

Correct reply

123 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile
Vish_dhaliwal
Employee

14-05-2019

Hello,

cq:name (the asset node name) property is only available when the "Title" metadata field is set. Go to properties of any asset and enter any title in the metadata. Refresh the asset in crxde and you will see that the cq:name becomes the node name of the asset and the title becomes the dc:title.

Avatar

Avatar
Validate 1
Level 2
lovepreetk75597
Level 2

Likes

3 likes

Total Posts

24 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 1
Give Back 3
View profile

Avatar
Validate 1
Level 2
lovepreetk75597
Level 2

Likes

3 likes

Total Posts

24 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 1
Give Back 3
View profile
lovepreetk75597
Level 2

14-05-2019

Hey Vish.dhaliwal

Thanks for your answer.

However we have already known this part.

The issue is that these properties are not populating even after filling the dc:title.

My understanding is some customization might have overridden this function, but to debug this we need to know what drives this action of populating cq:name on filling dc:title.

I have tried with the workflows but could not find any launcher for this.

Please suggest if you have any idea on this.

Avatar

Avatar
Give Back 50
Employee
Vish_dhaliwal
Employee

Likes

189 likes

Total Posts

356 posts

Correct reply

123 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile

Avatar
Give Back 50
Employee
Vish_dhaliwal
Employee

Likes

189 likes

Total Posts

356 posts

Correct reply

123 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile
Vish_dhaliwal
Employee

14-05-2019

Did you try with OOTB asset update workflow?

launcher for which workflow?