- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2024 03:21 AM
Hi Experts,
I need urgent help here!
I have a field with a max length of 255. The record producer mapped it to this field. Once the user submitted a request, that field was mapped.
After that, I opened that field dictionary and changed the max length to 500. But that field's data (value) is now truncated (reduced). I want that old value of that field back.
How do you think I could do this?
Thanks in advance,
Amol
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2024 04:29 AM
You can try finding your record producer variable value in question_answer table.
If you still have the truncated data there then there is no possibility of getting it.
Regards,
Sumanth
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2024 03:47 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2024 04:23 AM
Hi @Ravi Chandra_K,
Thank you for your reply.
So when the user submitted the request, the field's max length was 255 and the value was more than that. Then I changed the max length to 500, and then the value is truncated.
This is what I'm trying to understand.
Regards,
Amol

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2024 04:29 AM
You can try finding your record producer variable value in question_answer table.
If you still have the truncated data there then there is no possibility of getting it.
Regards,
Sumanth
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2024 05:38 AM
Hi @SumanthDosapati,
Thank you for your reply. Yes, I was able to check the data on the "question_answer" table. After updating the max length of the field length, I can use the data.
Thank you,
Amol