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 :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Unable to migrate Service Orders and Lines - Entity 'IsReadOnly'

(0) ShareShare
ReportReport
Posted on by 204

Service Order and Service Order Lines entities are marked as 'IsReadOnly'.  How are you supposed to migrate service order to D365 F&O?

8666.image002.png

I have the same question (0)
  • Suggested answer
    GirishS Profile Picture
    27,833 Moderator on at

    Hi Tim Ott,

    I think you need to duplicate that entity and use it. After duplicating you can change IsReadyOnly property to No.

    Thanks,

    Girish S.

  • Suggested answer
    Mohit Rampal Profile Picture
    12,565 Moderator on at

    Read only Data entities are only for export, if you need to import then you have to duplicate the Data entity, staging table and security privileges. Update the IsReadOnly property value to 'No' in the duplicated date entity as Girish mentioned.

  • cowboyott Profile Picture
    204 on at

    I tried duplicating the entities and was able to get service order headers to migrate fine, however, the service order lines are still failing.  I changed all fields to allow edit and allow edit on create, and I unchecked all validate options available on the data entity before import. Still getting 'Error(s) occurred while writing entity record.

    Any ideas?

  • cowboyott Profile Picture
    204 on at

    The error is thrown when _target.insert() is called from the DMFEntityBase.insertUpdate() method.  I am unable to debug any further...

  • André Arnaud de Calavon Profile Picture
    303,365 Super User 2026 Season 1 on at

    Hi Tim,

    There might be a reason why Microsoft made the entity read-only. What are the exact errors you get from your custom entity?

  • cowboyott Profile Picture
    204 on at

    Hi Andre, I had the same thought that there was a reason they made it read-only, but I was hoping someone could shed some light on that reason.  I imagine my client is not the first customer to migrate open service orders.

    The exact error I was getting is ''Error(s) occurred while writing entity record.".  

    Interestingly, I followed it through the tracer parser to a point where microsoft writes the error to telemetry (not sure exactly how to view these), but it does not write the error out to the infolog, or DMF.   The error that writes out to telemetry is 'ExceptionWhileSettingField'  on SysDataEntityPersistor.DoMapEntityFieldToDataSourceField().

    I was finally able to export some test service lines and re import with my duplicated data entity, but only with all validations and business logic turned off.  I am still having a hard time importing records from the legacy system, but I should be able to figure it out from this point.  Once I have it all working, I will update this post with everything I did.

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!

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

#1
André Arnaud de Calavon Profile Picture

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

#2
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 390

#3
Adis Profile Picture

Adis 266 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans