Customer experience | Sales, Customer Insights,...

OData v2.0 Service removal

(0) Share

Report

Posted on by MaciejR

Hi guys,

I'm having a solution/plugin that's still using OData v2 and is deployed to both on-premise (multiple versions) and online CRMs. I'd like to understand:

1. Are on-premise CRMs affected by OData v2.0 removal or that applies to online only? If applies to on-premise how is it released to customers? Do this kind of breaking changes come with major version upgrade that you manually need to approve?

2. When migrating your code away from OData v2, how do you test the code to make sure it actually is not using OData anymore? I'd like to be 100% confident I covered all the code. Is there any way to block ODatav2 so I can simulate lack of its support?

Thanks.

All responses (2)

Answers (0)

Shaun W Harvey 240 on at

Like (0)

Report

RE: OData v2.0 Service removal

If your code is in a solution in an Online Environment.

You can run "Solution Checker" From the Maker Portal.

Details of how to do it are in the deprecation notice.

It has a specific OData v2 check.

OData v2.0 Service removal date announcement | Microsoft Power Apps

So, you could develop your code online and solution check as you go.
Suggested answer

Guido Preite 54,075 Moderator on at

Like (0)

Report

RE: OData v2.0 Service removal

the removal affects online customers, if Microsoft releases an onpremise update then you will need to check if it removes the OData 2.0 endpoint or not.

regarding the migration, server side code should not be affected (if you use the official SDK, if you are using some custom SDK to interact it may use OData 2.0 endpoint) client side you check the endpoint that is called in your calls (using the browser tools)