What is the logic behind attributes saved in target

(0) Share

Report

Posted on by sahara

645

I am using phoneCall entity, first I used my logic in phoneCallSetState and got all the data I needed, for exampeI have a costume field which called category, and I changed it when I created a new record and then I could get the category value (in c# code side) but later I took the same code and added it to my phoneCallPostUpdate and after I changed the same field - category (but now under postupdate msg) I got NULL from the same field. I used postImage to get the data eventually but I need an explanation why I could get the data from the same field I changed in SetState but got NULL in PostUpdate?

Thanks

*This post is locked for comments

All responses (2)

Answers (2)

Verified answer

Mahendar Pal 45,095 on at

Like (0)

Report

RE: What is the logic behind attributes saved in target

If your field is dirty you will get under entity's input parameter.
Verified answer

Alex Fun Wei Jie 33,626 on at

Like (0)

Report

RE: What is the logic behind attributes saved in target

Hi,

Normally, the Target entity that is present in the InputParameters collection is not returned by querying the system, but represents the user's input.

in your case you stated, you were changing the same field but you got a null, are you changing the value to null?

if it is no, share your code or some screen shot here.