Table of status reason in database

(0) Share

Report

Posted on by Albert_

450

Hi there all.
I have got a problem.
In my dev environment I had a status reason in lead entity, that does not exist any more, but it exists in production environment.
Now I have some customization on lead entity status reason and I need that one( in dev environment) , but it does not exist !( as I said)
Note that I do not want to make unmanaged changes on my product environment.
I decided to create a new status reason in the lead entity and change the value of that to the existing one in product environment via sql query.
I can update stringmapbase and statusmapbase table in which the newly added status reason record is, but it does not effect.
In the solution it display the old value.Also when I create new lead record and change the status reason to the new one, it display the old value in the db.
I know that is unsupported and also maybe the most worst solution, But I do not have any other way, Do I?
If yes please give me some advise.
If no please tell me how can I change status reason value in a entity like lead.

thanks

All responses (2)

Answers (0)

Albert_ 450 on at

Like (0)

Report

RE: Table of status reason in database

Thanks for your reply.

Yeah, after reading your answer I go through db and find that table you just pointed.

I already have a backup of the whole system, including db, also the solutions.

I think the key is your answer.

Best regards
Radu Chiribelea 6,667 on at

Like (1)

Report

RE: Table of status reason in database

If I recall correctly i think there are several other tables that handle the OptionSet Values - but i can't remember exactly the names : AttributePicklistValue, OptionSet ? You'd need to go through them and reverse engineer the contents to find out. Yet tampering with the DB not only is unsupported but it could break the database. So I would suggest looking at alternatives.

Do you still have a backup of the solution? You could import that back to the system.

Before being able to provide some additional input, it would help if you can share some images to explain the issue better.