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

Announcements

No record found.

News and Announcements icon
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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
ScottDurow Profile Picture

ScottDurow 2

#2
GJones Profile Picture

GJones 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans