Service Order and Service Order Lines entities are marked as 'IsReadOnly'. How are you supposed to migrate service order to D365 F&O?
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.
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?
The error is thrown when _target.insert() is called from the DMFEntityBase.insertUpdate() method. I am unable to debug any further...
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?
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.
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.
André Arnaud de Cal...
291,969
Super User 2025 Season 1
Martin Dráb
230,842
Most Valuable Professional
nmaenpaa
101,156