215
Hi all,
I have plugin on creation of entity and based on some option set it updates positive value to negative value , (eg: value = 1800 on creation from UI and plugin triggers and updates it to negative value = -1800 , this is logic for this
But in one case it updated from 1800 to -1800 and again updated back to postive 1800 so by logic it should not happen
Any assistance on this is much appreciated
*This post is locked for comments
You could add a flag field, could call it some thing like new_milagevalueset and set this to YES when you do Service.Update. And in you first condition, you can include a check for this flag. You only need to update if the flag is No. Try this and see if this makes any difference.
Hi,
Can you check are you updating this field any where else in the workflow.
This may happen because, suppose you are triggering the plugin on change of that field some workflow is updating this field value.
This field is changed now which makes the plugin to trigger again.
Thank you
Soundharya
If found useful, please mark the answer as verified
Hi,
If it is already a whole number then don't convert it again. below code should work for you.
Share
Report
All responses (
Answers (
int value = target.Contains("new_value") ? target.GetAttributeValue<int>("new_value") : 0;
if(value==0) return;
else
target["new_value"] = value > 0 ? -(value) : value;
Yes Goutam, its a simple whole number and it looks fine with min/max values and my query was even if it is executing twice/trice , value should not be changed as per the code , will use the context depth for this but not sure how the value moved from negative to positive because as per code it shouldn't .
Hi ,
I can see your code is correct. What is the field type of "new_value" , Just to make sure that your field type is capable to store negative value , go to field properties and take a look once whether you have set any min, max value. Try to put some trace log inside the if condition so that you could understand your code fall in loop or not in that case you should check context depth.
In addition you can also enable audit log for the field to see how many updates has done for particular operation.
Thanks for the response Kokulan,
01. I do have other plugin steps on this entity but not for the same plugin.
02. Yes, there other workflows and plugin on this entity but their functionality is completely different to this.
03. Yes checked the audit history of this and Same User has modified the record twice on same time infact same minute pls look at the audit history
1st time shows
2nd update on this record
bit surprised with this issue and it is not reproducible as last time it was produced was 2 months back and now it again
Check the trace log , if it is executing twice .
handle with depth in case
Hi
Your code seems to work fine even if its called more than once
I would check the following
01. Do you have more than one plugin step registered for the same plugin
02. Are there any workflows executing on this entity on create or update
03. You could enable auditing and see the user of the update and see both updates are done by same user. You could try and change the plugin RUN as to different user and see if that makes any difference in the audit history.
Any assistance on this is much appreciated ?
gdas can you pls suggest on this?
Thanks for the response Daryl but i have to run in post operation as it is associating the target to other entity.
#1
André Arnaud de Cal...
292,865
Super User 2025 Season 1
#2
Martin Dráb
231,723
Most Valuable Professional
#3
nmaenpaa
101,156
Moderator
