Deprecations - Revision history

CarinaMClaesson at 20:48, 27 June 2022

2022-06-27T20:48:18Z

CarinaMClaesson at 11:56, 13 May 2022

2022-05-13T11:56:13Z

CarinaMClaesson at 11:47, 13 May 2022

2022-05-13T11:47:58Z

CarinaMClaesson at 11:47, 13 May 2022

2022-05-13T11:47:09Z

CarinaMClaesson at 11:46, 13 May 2022

2022-05-13T11:46:54Z

CarinaMClaesson at 11:45, 13 May 2022

2022-05-13T11:45:13Z

CarinaMClaesson at 11:40, 13 May 2022

2022-05-13T11:40:34Z

CarinaMClaesson at 11:40, 13 May 2022

2022-05-13T11:40:22Z

CarinaMClaesson at 11:39, 13 May 2022

2022-05-13T11:39:55Z

CarinaMClaesson at 11:38, 13 May 2022

2022-05-13T11:38:07Z

@@ Line 17: / Line 17: @@
 == Microsoft Resources ==
 * [https://docs.microsoft.com/en-us/power-platform/important-changes-coming/?WT.mc_id=DX-MVP-5003780 Important changes (deprecations) coming in Power Apps, Power Automate, and customer engagement apps]
 * [https://powerapps.microsoft.com/en-us/blog/deprecation-of-the-regional-discovery-service/ Deprecation of the regional Discovery Service and its replacement with the global Discovery Service]

@@ Line 1: / Line 1: @@
-A deprecation means that Microsoft intends to remove the feature or capability from a future major release. This means that you need to have a future plan which includes taking care of those parts in your solutions that uses features or capabilities which are being deprecated.
+A deprecation means that Microsoft intends to remove the feature or capability from a future major release. This means that you need to have a future plan which includes taking care of those parts in your solutions that uses features or capabilities which are being deprecated. A good rule of thumb is of course NOT to use deprecated features, functionality etc. in new projects. For existing projects, depending from situation to situation a good rule of thumb might be if it works, don't fix it. Whenever you create something new though, it is a good idea to keep technical debth in mind and some old parts might needs to be renewed.
 {{Quote
@@ Line 6: / Line 6: @@
 }}
-However it is important to have a strategic plan for how to deal with deprecations. Sometimes dates are announced for when something will stop working. It might be the removal of an important endpoint which you use in your code. You need to keep an eye open for such dates and as soon as you have a date that means something will stop working, then you really need a plan to replace it.
+It is important though to have a strategic plan for how to deal with deprecations. Sometimes <b> dates are announced </b> for when something will stop working. It might be the removal of an important endpoint which you use in your code. You need to keep an eye open for such dates and as soon as you have a date that means something will stop working, then you really need a plan to replace it.
 {{

@@ Line 1: / Line 1: @@
 A deprecation means that Microsoft intends to remove the feature or capability from a future major release. This means that you need to have a future plan which includes taking care of those parts in your solutions that uses features or capabilities which are being deprecated.
-{{quote | "If it works, don't touch it!"}}
+{{Quote
 However it is important to have a strategic plan for how to deal with deprecations. Sometimes dates are announced for when something will stop working. It might be the removal of an important endpoint which you use in your code. You need to keep an eye open for such dates and as soon as you have a date that means something will stop working, then you really need a plan to replace it.

@@ Line 1: / Line 1: @@
 A deprecation means that Microsoft intends to remove the feature or capability from a future major release. This means that you need to have a future plan which includes taking care of those parts in your solutions that uses features or capabilities which are being deprecated.
-{{quote | If it works, don't touch it!}}
+{{quote | "If it works, don't touch it!"}}
 However it is important to have a strategic plan for how to deal with deprecations. Sometimes dates are announced for when something will stop working. It might be the removal of an important endpoint which you use in your code. You need to keep an eye open for such dates and as soon as you have a date that means something will stop working, then you really need a plan to replace it.

@@ Line 1: / Line 1: @@
 A deprecation means that Microsoft intends to remove the feature or capability from a future major release. This means that you need to have a future plan which includes taking care of those parts in your solutions that uses features or capabilities which are being deprecated.
-"If it works, don't touch it!" :) But it is important to have a strategic plan for how to deal with deprecations. Sometimes dates are announced for when something will stop working. It might be the removal of an important endpoint which you use in your code. You need to keep an eye open for such dates and as soon as you have a date that means something will stop working, then you really need a plan to replace it.
+{{quote | If it works, don't touch it!}}
 {{

← Older revision		Revision as of 11:45, 13 May 2022
Line 1:		Line 1:
	A deprecation means that Microsoft intends to remove the feature or capability from a future major release. This means that you need to have a future plan which includes taking care of those parts in your solutions that uses features or capabilities which are being deprecated.		A deprecation means that Microsoft intends to remove the feature or capability from a future major release. This means that you need to have a future plan which includes taking care of those parts in your solutions that uses features or capabilities which are being deprecated.
		+
		+	"If it works, don't touch it!" :) But it is important to have a strategic plan for how to deal with deprecations. Sometimes dates are announced for when something will stop working. It might be the removal of an important endpoint which you use in your code. You need to keep an eye open for such dates and as soon as you have a date that means something will stop working, then you really need a plan to replace it.

	{{		{{

@@ Line 4: / Line 4: @@
 PWBoxWarning
 | title = OData v2.0 Service removal date: November 11, 2022
-| text = Make sure to check your JavaScript web resource code in good time before November 2022! Use the solution checker or visit your repositories and look for "/xrmservices/2011/organizationdata.svc" Read more: [https://powerapps.microsoft.com/en-us/blog/odata-v2-0-service-removal-date-announcement/ OData v2.0 Service removal date announcement]
+| text = Make sure to check your JavaScript web resource code in good time before November 2022! Use the solution checker or visit your repositories and look for "/xrmservices/2011/organizationdata.svc"
 }}

@@ Line 3: / Line 3: @@
 {{
 PWBoxWarning
-| title = Deprecations are coming to [[model-driven apps]] 2021
+| title = OData v2.0 Service removal date: November 11, 2022
-| text = Form footers won't be supported [https://docs.microsoft.com/en-us/power-platform/important-changes-coming#form-footers-in-model-driven-app-wont-be-supported-with-the-2021-release-wave-2 Form footers deprecation] and low-density form headers won't be supported [https://docs.microsoft.com/en-us/power-platform/important-changes-coming#low-density-headers-in-model-driven-apps-wont-be-supported-with-the-2021-release-wave-2 Low-density form headers deprecation]. These two deprecations will apply with the 2021 Release Wave 2 (October 2021).
+| text = make sure to check your JavaScript Web Resource code in good time before November! Read more about it here: [https://powerapps.microsoft.com/en-us/blog/odata-v2-0-service-removal-date-announcement/ OData v2.0 Service removal date announcement]
 }}