- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-26-2015 05:09 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-26-2015 09:36 AM
Naga,
try to change the max length to 256 first and then try to put it to a bigger value after. It seems that if you don't put it to 256 first, the change will not occur as at a database end (one you cannot change yourself) there is a change in the field data type.
Let us know if that works for you.
Kind regards,
Alexandra
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-28-2015 07:39 AM
that's the changes i made in my instance and it showing to 256 characters i don't know why it is not changing in your instance
Thanks
sandeep
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-28-2015 07:44 AM
Thanks for your help, I will create a ticket in Hi.
Thanks,
Patrick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-28-2015 07:49 AM
no problem, when u hear from hi support please let me know ,actually i also need to know exactly whats the issue behind it...
Thanks
sandeep
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-15-2015 11:49 PM
Hi Sandeep,
The answer from HI is:
This is a known issue, the problem is defined in PRB575555.
A workaround is to increase also the max length of the sys_email* tables as well.
ex. yourinstance/sys_dictionary_list.do?sysparm_query=nameSTARTSWITHsys_email%5EelementSTARTSWITHsubject
Regards,
Patric