Answered by:
force save field in a form

Question
-
Hi,
I copy the value of a system attribute in a field of a form for which I created a new attribute.
So I can see this value in the form
but when I try to copy the new attribute in an other entity through a workflow,
that doesnt work. does that mean that my attribute was not updated ? in which case
is there a way to force update of the attribute after getting the system value in the field ?Monday, January 18, 2010 7:31 PM
Answers
-
Hi.
If this created field is disabled add following code after value of this field is changed:
crmForm.all.<field>.ForceSubmit = true;
Truth is opened the prepared mind
My blog (english)
Мой блог (русскоязычный)- Proposed as answer by Andrii ButenkoMVP, Moderator Tuesday, January 19, 2010 8:46 AM
- Marked as answer by DavidJennawayMVP, Moderator Thursday, February 25, 2010 10:40 PM
Monday, January 18, 2010 7:46 PMModerator
All replies
-
Hi.
If this created field is disabled add following code after value of this field is changed:
crmForm.all.<field>.ForceSubmit = true;
Truth is opened the prepared mind
My blog (english)
Мой блог (русскоязычный)- Proposed as answer by Andrii ButenkoMVP, Moderator Tuesday, January 19, 2010 8:46 AM
- Marked as answer by DavidJennawayMVP, Moderator Thursday, February 25, 2010 10:40 PM
Monday, January 18, 2010 7:46 PMModerator -
very useful again Andriy.
and I set the condition of my workflow on update of this attribute :)Tuesday, January 19, 2010 8:44 AM -
Hi,
Alas, if I do a save of the form and then a save and quit everything works fine, the system attribute (salesorderdetailid) pass its value correctly
but if I do a direct save and quit of my form the sytem attribute is null, the new attributes value stays null and so the workflow doesnt run !
is the a solution to prevent that to happen ?
thanks for your answersWednesday, January 20, 2010 6:04 PM