Finance | Project Operations, Human Resources, ...

How to modify the ReadOnly property by creating extension?

(1) Share

Report

Posted on by FB-08050748-0

Hello Community,

I'm working on enabling POST operations for SalesInvoiceHeadersV2 and SalesInvoiceV3Lines to create invoice journals using the OData API. These entities are part of the Application Suite model. To allow POST operations, I need to duplicate the entities and change the ReadOnly field in the properties section to No.

However, I've hit a roadblock. After creating a project in Visual Studio and duplicating the entity, I can't save the project because Application Suite isn't authorized for modification. Through further research, I learned that I can modify the entities if I create a new model based on Application Suite and extend them.

My main confusion lies in how to modify the ReadOnly field to allow POST operations. Could you please point me in the right direction or share any helpful documentation?

I've already checked these documents, but they haven't provided much help:

I've also gathered information from posts in this forum. Any assistance would be greatly appreciated.

Thank you in advance!

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Suggested answer

Mohamed Amine Mahmoudi 26,811 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi,

first, you need to create a model for standard element specifications and extensions.

for the subject of data entities, I suggest you duplicate the entity STD and then you can set Is read only to no.

Best regards,

Mohamed Amine MAHMOUDI

Was this reply helpful? Yes No
Suggested answer

Waed Ayyad 9,212 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi,

First of all, you should duplicate the entity on custom model, you can't duplicate it on standard model.

You can follow the below link to create a new model or use a custom model if you have one:

https://dynamics365musings.com/create-a-model-in-d365/

This is the first step.

Thanks,
Waed Ayyad

If this helped, please mark it as "Verified" for others facing the same issue

Was this reply helpful? Yes No
Suggested answer

Bharani Preetham Pe... 3,634 Moderator on at

Like (0)

Report
Copy link

Link copied!

I think you are not duplicating entity in your custom model. By this time, you should have already created a model. In that custom model you need to duplicate. When you duplicate it, then you will get full control of that entity. So, you can simply make the readonly field to No.

Was this reply helpful? Yes No
Raj Borad 1,578 on at

Like (0)

Report
Copy link

Link copied!

Hi,

Can you please check below document.

https://dynamics365musings.com/create-a-d365-data-entity/

Was this reply helpful? Yes No
Suggested answer

Layan Jwei 8,282 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi FB,

When you create a new model, make sure your newly created project also points to this new model (by right clicking on the project and changing the model property)

After that, search for the entity in AOT, right click on it then click duplicate in project

now this new entity will appear in your project, where you can modify the properties you need. You also need to duplicate the staging table. Make sure you give both the entity and staging table a new name and new label

Also modify the following properties in the new entity:
PublicCollectionName: change it to a new unique name

PublicCollectionEntity: change it to a new unique name

DataManagement Staging table: make sure this points to the new staging table you created

Thanks,
Layan Jweihan
Please mark this answer as "Verified" if it solved your issue. In order to help others who will face a similar issue in the future

Was this reply helpful? Yes No
Layan Jwei 8,282 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi,

Is your question answered? is yes, then please verify the answers that helped

Thanks,
Layan Jweihan

Was this reply helpful? Yes No