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 :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / DMF Field '' does not ...
Finance | Project Operations, Human Resources, ...
Answered

DMF Field '' does not allow editing

(0) ShareShare
ReportReport
Posted on by b_radlyjames 3,157
I have a custom Data Entity for the Service Order Table.  My primary key is my ServiceOrderNumber field.
When I import a file with an existing ServiceOrderNumber it updates the record as expected.
However, if I want it to create a new record I can't use the 'Auto Generate' on my primary key as that would break the 'update'.
 
So, I decided to follow what had been done in the CustCustomerV3Entity.
I set my 'ServiceOrderNumber' 'Allow Edit' field properties on the Entity and Staging table to 'Yes'.
 
In looking through all the setup and code for the customer entity, this seems to be it.  However, I still get:
 
 
The second error is a result of the first error and may not matter (I believe).
 
 
I have the same question (0)
  • b_radlyjames Profile Picture
    b_radlyjames 3,157 on at
    UPDATE:
     
    In doing more research, I found that the label from this error was this:
     
     
    This label is referenced in 4 classes. Only 1 of which would be used by DMF.  
     
    That led me to the NumberSequenceTable and the 'numAllowEdit' method.
    That method says that unless one of 3 fields is set to 'Yes', the field using the number sequence is NOT editable:
     
     
    Once I set 'To a Higher Number' to yes (Seemed like the safest change for my purposes) the '... does not allow editing.' error went away.
    The other error remains.  It looks like it isn't generating a new Service Order Number like it should.  Based on the CustCustomerV3Entity, I did the following in the 'initvalue' method of my data entity:
     
     
    This is similar to what I see on the CustCustomerV3Entity and other Data Entities that allow Write operations.
    I believe this is supposed to tell the field to use the Number Sequence specified in 'SMAParameters'.
  • Verified answer
    b_radlyjames Profile Picture
    b_radlyjames 3,157 on at
    UPDATE:
     
    I was able to get this to go through by removing the 'SERVICEORDERNUMBER' field from my import file.
    Previously I had it in there but with no value.  Once I removed it, it created the record and the used the number sequence for the service order number.
     
     This does, potentially, pose an issue as I believe Dual-Write will be sending this data entity a value to be used for an update or no value to cause a new record to be created.

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!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 659

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 465 Super User 2026 Season 1

#3
Syed Haris Shah Profile Picture

Syed Haris Shah 304 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP
License usage reporting (in-app and PPAC) with Entra dynamic groups

Product updates

Dynamics 365 release plans