Dynamics Community Forum Thread Details

Problem with calculated field forces double saving...

I tried to build a calculated field to generate the record name by concatenating other field values. The first component is to be the name of its Discount List lookup. Of course, Microsoft failed to provide the dot operator functionality for the discounttype entity. Hence, to complete the requirement I built all the rest and finished the concatenation in a synchronous workflow -- {Discount List(customentity)}-{Name Builder(customentity)}.

So, what's my problem? The workflow "comes back" after Save (create) leaving the Name field dirty and the user has to hit save again. What particular magical step or setting am I missing to cause this problem? Shouldn't the form refresh after the name has been updated by the workflow and be done with it?

PS- I do everything I can to avoid infusing javascript.

thanks in advance for looking

Quick Links