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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Restrict metadata schema for excel type assets in AEM

Avatar

Level 6

I have created a custom  metadataschema for applying to assets in a project specific folder.

But default , this is what it will get applied to

P_V_Nair_0-1672780280354.png

And inside the image

 

P_V_Nair_1-1672780297699.png

 

 

But I can see , this schema which has certain mandatory properties are being applied to excel files with extension xlsx as well.

How can I restrict this schema getting applied for excel type assets?

1 Accepted Solution

Avatar

Correct answer by
Employee

I would suggest to remove these mandatory properties that you need only for image type from main custom schema and instead add them  under 'image metadata schema'  only.

 

 

View solution in original post

10 Replies

Avatar

Level 6

Hello @P_V_Nair 

 

I duplicated the OOTB default schema and applied it to a folder.

Uploaded CSV and XLSX, but I am not getting mandatory fields. Can you please share, what the fields are appearing as mandatory?

 

Also, for excel files, you should look under application schema.

Avatar

Level 6

@aanchal-sikka  As I have mentioned in my post, I created a custom schema wit custom fields and made the fields mandatory. When i apply it to folder , that shows as mandatory fields for excel files. Please find the application schema inside it where only pdf is specified and not excel.

P_V_Nair_0-1672844517232.png

 

Avatar

Employee

Excel type mime type is 

Screenshot 2023-01-04 at 11.26.52 AM.png

 so schema applied  for excel is the application schema which intern extends from the default schema. I see you have overridden the application schema. Please recheck your application and default schema and see if it has those mandatory properties. If you still wish to have field properties specific to excel mime type you can create another schema under application schema.

Avatar

Level 6

@digarg This is the screenshot of the application schema inside my custom schema

P_V_Nair_1-1672847057175.png

I don't have excel in there. Are you saying to creating a custom application schema inside my custom schema for excel?

Avatar

Employee

The custom application metadata schema will be applied by default  on your excel. If you dont want application metadata schema to be applied then you can add an excel metadata schema under application similar to psf  or use any existing schem and apply them 

Avatar

Level 6

@digarg  I think i am not quite following you.

I have a custom metadataschema with some properties as mandatory fields and that is applied to a folder.

I have not defined any cutom application schema inside this metadata schema. pdf just came by default and omce you click on pdf, it is actually empty.

P_V_Nair_0-1672854908919.png

But like you said, i tried to create a new application schema excel.

 

P_V_Nair_1-1672855005441.png

When i open , it is empty and when i edit it

P_V_Nair_2-1672855039607.png

 

 

 i can see the custom metadata properties are all in there and it is in locked state.

So what i assume is, the main metadataschema is cascaded to application schema. My question is how can i make sure my custom metadata is not applied to excel files in that folder.

Avatar

Employee

I meant , check your application schema , the metadata properties in excel are cascaded from there. Do you see mandatory metadata properties there , can you remove them from there?

 

There is no need to create another excel schema if there are no metadata properties specific to excel.

Avatar

Level 6

@digarg  There are no metadata properties specific to excel and it is defaulting to the main custom schema and images, application are all inside that schema.

I don't want excel to default to my custom schema since it is picking the mandatory properties i added for images. So my ask is how i can remove excel from defaulting to the main custom schema.

 

Avatar

Correct answer by
Employee

I would suggest to remove these mandatory properties that you need only for image type from main custom schema and instead add them  under 'image metadata schema'  only.