Hi Ahsan, hope you are well, have you looked at the activity code ANGMI and this is active currently please see the attached screen shot

Hi Mothilal, Yeah, all well. Thanks. Appreciate your help. I have checked and found that activity code "ANGMI" is active. As this activity code seems to be related to Sage EM HR. Therefore, I have deactivated it and performing dictionary validation right now. Hopefully, this should resolve the issue. I will keep you posted.

Bests,

Hi Ashan, only a please to try to assist , please let me know once you are able to

Hi Mothilall, After making "ANGMI" activity code deactive, when I am trying to mark my SEED folder as TEST now I am getting the same error for activity code "HRVII". Which is also related to Sage EM HR. Is there any way, I can deactivate all the Activity Codes related to EM HR? Because I assume that even after deactivating "HRVII", I will start getting error for other EM HR related activity codes. Else, how can I add the EM HR license as I have it already? However, I do not want to use EM HR.
See screenshot below:

Thanks,

Good Day, you are able to de-activate the code , should you require , but as stated you will be getting alot of other errors, if you are not making use of EMHR , then a good idea would be to get in touch with our EM support desk , they may be better able to assist you with this query .

Please use the following address to get in touch 

Thanks Mothilall for your help. I just gave it a try after my last message and it happened twice more only. After the above mentioned 2 activity codes, I just had to deactivate "PORP" and "KRU" activity codes and then I was able to mark my SEED folder as "TEST".

So all is well, which ends well. So might contact support for any other issue, if required. You might raise it internally to get fixed in future versions.

Thanks Mothilall for your help. I just gave it a try after my last message and it happened twice more only. After the above mentioned 2 activity codes, I just had to deactivate "PORP" and "KRU" activity codes and then I was able to mark my SEED folder as "TEST".

So all is well, which ends well. So might contact support for any other issue, if required. You might raise it internally to get fixed in future versions.