Create Product by code using Data Entities D365

(0) Share

Report

Posted on by Sepideh Azad

Dear AX developers,

I tried using "EcoResReleasedProductCreationV2Entity" data entity in my code to create and release products. It worked fine but I noticed there was a difference in one of it's data sources compared to an older version which caused the build fail on that server.

My question is that, is it a good idea and is this entity reliable to use in code to create products or there is a risk that later on it may fail due to upgrades.

Thanks

I have the same question (0)

All responses (7)

Answers (3)

Blue Wang on at

Like (1)

Report

HI Sepideh Azad,

You mentioned "which caused the build fail on that server.", can you share the error message?

Regarding EcoResReleasedProductCreationV2Entity, it is feasible to use it to create Item or released product.

https://community.dynamics.com/365/financeandoperations/f/dynamics-365-for-finance-and-operations-forum/381552/x-code-to-create-item-or-released-product-in-d365-fo

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 301,035 Super User 2025 Season 2 on at

Like (1)

Report

Hi Sepideh,

The data entities can indeed change. Sometimes there can be an enhancement or bugfix. In some cases, there will be a complete new entity version. There might be a chance that in future a V3 version will be released and the V2 will then be deprecated. Note that also the data model itself could be changed in future.

For sure, you have to review the impact on all updates. For that reason you first install a service update on a non-production and DEV environment to see if everything is still working or need some attention.

Can you provide the details what was changed by Microsoft and what made it fail on your coding?

Was this reply helpful? Yes No
Sepideh Azad 15 on at

Like (0)

Report

Hi Blue Wang,

Thanks for your reply. On that server, the second data source of the EcoResReleasedProductCreationV2Entity was EcoResProductEntity, whereas on my vm it is EcoResProductV2Entity, so it didn't support our custom fields added to the EcoResProductV2Entity extension.

Was this reply helpful? Yes No
Sepideh Azad 15 on at

Like (0)

Report

Hi André,

Thank you for your explanation.

Yes, as I just mentioned one of the data sources of the EcoResReleasedProductCreationV2Entity has changed from EcoResProductEntity to EcoResProductV2Entity. So it didn't include the EcoResProductV2Entity extended fields. What if I duplicate these entities and use my own?

Was this reply helpful? Yes No
Verified answer

vinitgoyal2005 6,332 on at

Like (0)

Report

Hi Sepideh,

Yes, you can duplicate the OOB entities add your custom fields as well if any, and use it to create a Product.

Was this reply helpful? Yes No
Verified answer

Sukrut Parab 71,710 Moderator on at

Like (0)

Report

You should update your other server to the same version you have where you have done modification to avoid your issue.

You can duplicate entity and use your own but every time you apply new update make sure to test your duplicate entity and make sure everything works. I have see some times entities change a lot and some of the things you might have done as a customization comes as a part of standard entity with more improvement which you might miss. Not saying its a wrong path but something you have to keep in mind when you apply new updates.

Was this reply helpful? Yes No
Verified answer

André Arnaud de Cal... 301,035 Super User 2025 Season 2 on at

Like (0)

Report

Hi Sepideh,

In addition, what if the data model changes? In that case, you have to change the entity anyway. Microsoft will ad just their data entities in that case. You have to adjust it when you have an own custom entity.

Note that there are not that much changes expected.

Was this reply helpful? Yes No