Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.

Getting error when trying to save any page property

Avatar

Level 2

Hello,Using Aem 6.4.8, when trying to modify/save/add any page property it is throwing following error org.apache.sling.api.resource PersistanceException :Invalid Date.

Anyone faced similar issue before?  -Thanks in advance

7 Replies

Avatar

Community Advisor

@Kavya6875 Can you check the permission- give rights to group everyone .

Can you try and save as admin and see if that works?

Avatar

Employee Advisor

Hi,

>The reason if this exception was in given rights to users. Try removing and giving rights to group , will surely fix the issue.

 

Regards,

Manvi Sharma

Avatar

Community Advisor

@Kavya6875 

Did you recently update the AEM version to 6.4? I am expecting that there should be some date format issue on the page after the update. You might need to find that custom date and change the format accordingly

Avatar

Community Advisor

It looks like some property on the page is not having a valid date format. Please confirm if its happening after upgrade of AEM?

Just for testing purpose, remove existing date type properties and then try to update title of page in CRXDE. If it saves without any error then issue is with the format of the date type property which is already present on the page.

 

Link of similar issue with different Exception :
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/granite-datepicker-s-value...

Avatar

Level 2

@Sachin_Arora_ 

Tried by deleting existing date property and checked.. It is not getting saved.. And still shows same error.

 

There was no version upgrade recently.

Avatar

Community Advisor

Please share stack trace. It will help in checking from where PersistanceExceptionInvalid Date is getting initiated. 

Avatar

Community Advisor

Hi @Kavya6875 ,

It could be the reason that your upgraded project uses classic dialogs in touch UI.