web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Problem with calculated field forces double saving...

(0) ShareShare
ReportReport
Posted on by 1,030

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

*This post is locked for comments

I have the same question (0)

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans