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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / What can cause field t...
Microsoft Dynamics CRM (Archived)

What can cause field to be marked dirty?

(0) ShareShare
ReportReport
Posted on by awalters 3,079

I have an instance where a field is getting marked as dirty again after first save, even though the data hasn't changed.  I checked every dependency (business rules, javascript, etc...) the field and entity has, and nothing is touching the value.  Is there any other reason a field would be included in a save, other than it changing or being marked as always save?

*This post is locked for comments

I have the same question (0)
  • awalters Profile Picture
    awalters 3,079 on at

    To give some further info - we have a field that has field level security on it that allows read/create only - we don't want it changing after first save.  However, immediately after first save, that field gets marked as dirty, and so on the subsequent save, there's a field security permissions error.

    I tried completely disabling all workflows, business rules, and javascript - same error.  I tried doing this same permission setting on a new field that was definitely not getting referenced anywhere else - still the same error, just now regarding this other field.  :-(  How/why are these fields getting marked for save, and how do I stop it?

  • gdas Profile Picture
    gdas 50,091 Moderator on at

    Hi Allison,

    This is expected behavior ,field level security also validate and set the field value in onchange/onload event of the secured fields . If you remove the read access of user field security profile  you can see the result what exactly is happening in the on change of the fields.

    Am pretty much sure if you remove field level security you wont get any dirty fields .

  • awalters Profile Picture
    awalters 3,079 on at

    ?  If this is expected behaviour how  could it possibly ever work to give someone create but not modify permission?  You'd run into this error every time.

  • gdas Profile Picture
    gdas 50,091 Moderator on at

    If I am not wrong ,  write access will be applicable only when after saved /create the record .

  • gdas Profile Picture
    gdas 50,091 Moderator on at

    Hi Allison ,

     I did a test with following scenario , please have a look -

    Field having Only Create Access and does not have Update/Read access:

    In the create form you can type value but you cant see the value , each time after typed the value convert to  ***  as there is no Read access. Which means that every time you typed the value set to ***  and make your forms dirty. 

    When you saved the records or after creates in the edit forms fields is completely disabled and value will be ***.

    In summary in the field level security when you remove update access which means  it is applicable for update form and not for  create form. But every time when you changed value having field level security enabled is making forms dirty.

    Hope this helps.

    Please close the thread if you got your answers.

  • awalters Profile Picture
    awalters 3,079 on at

    That's not the situation.  I'll clarify.

    The field has create and read permissions, just not update.  So when they're creating a record, they can type it in, and continue to see it.  This is as it should be.  If they leave the record and come back, they cannot change it.  Also as desired.

    The issue is this - they're creating the record, so they enter the value.  They hit save.  It saves, but it immediately marks the field as dirty so the user sees "unsaved changes" at the bottom.  If they hit save again, they get the error that they cannot update that field (even though they have not changed it).  I have verified that no code or process is touching the field, as well as tried it on a brand new field to be sure.  Same behaviour.

  • gdas Profile Picture
    gdas 50,091 Moderator on at

    Okay I will verify this tomorrow and will update you .

  • awalters Profile Picture
    awalters 3,079 on at

    Thank you!

  • awalters Profile Picture
    awalters 3,079 on at

    Also - when I added a new field, it was not getting marked dirty after the first save, until I added the field security to it.  It looks like the field security itself is causing this, which is confusing to me since it results in this error after first save every time.  (Note: it doesn't happen if you go out and back in...then everything works as expected.)

  • awalters Profile Picture
    awalters 3,079 on at

    Hi Goutam - did you (or anyone else) ever get the chance to try this?  Still haven't found a solution and I'm not sure how to proceed.  Hoping to confirm at least whether this is the behaviour for anyone else...

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

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