on ‎2021 Sep 24 7:46 AM
From our experience, it seems that the behavior is different for various fields when updating in pre action. Some get updated, while others are not. We are not sure about the root cause. In general, is it necessary to call Quote.Save() in custom actions / global scripts if a custom field already enables "Save quote on change"? Thanks.
Request clarification before answering.
Hi Yogananda Muthaiah,
Thank you for the quick answer. The option is enabled in our environment. However, we faced issue with following setup:
1. There are some pre-actions for "Generate Document For E-Sign" action
2. In one of the pre action, we populate some custom fields, e.g. Quote.GetCustomField('Customer_Field_1').Content = "test"
3. As these custom fields have "Save quote on change" enabled, we didn't use Quote.Save() in the pre action
4. In the generated contract document, we notice that some field is changed while some is not.
May we know the standard practice for this scenario?
Best regards,
Hulei
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 11 | |
| 6 | |
| 4 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.