Update error headings

JimDaly · JimDaly · commit 64331e737f6e · 2024-05-10T13:04:50.000-07:00
diff --git a/powerapps-docs/developer/data-platform/restore-deleted-records.md b/powerapps-docs/developer/data-platform/restore-deleted-records.md
@@ -11,6 +11,7 @@ search.audienceType:
   - developer
 contributors:
  - JimDaly
+ - shahzorkhan123
  - TakeN0
 ms.custom: bap-template
 ---
@@ -293,7 +294,7 @@ function Restore-AccountRecord {
 
 The following errors might occur when restoring records.
 
-#### RefCannotBeRestoredRecycleBinNotFound
+#### Restore related records before restoring primary record
 
 If some related records whose reference were removed as part of Cascade relationship, no longer exist, the restore operation will fail. To avoid this, always restore the related records not deleted as part of current record, before trying to restore the primary record.
 
@@ -303,27 +304,27 @@ If some related records whose reference were removed as part of Cascade relation
 > Message: `Entity with id '<Guid Value>' and logical name '<Entity.LogicalName>' does not exist. We cannot restore the reference '<Referred Primary Key Name>' that must be restored as part of this Restore call. ValueToBeRestored: <Guid Value>, ReferencedEntityName: <Referenced Entity Name>, AttributeName: <Referred Attribute Name>`
 
 
-#### DuplicateExceptionRestoreRecycleBin
+#### Don't specify primary key values when creating records
 
-Donot create records with specific primary keys, otherwise, if the previous record was in deleted state, the new record will prevent the deleted record to be restored.
+It is generally a good practice to always let Dataverse set the primary key when creating a record. If you create a new record that has the same primary key value as a deleted record, the deleted record can't be restored. If you do, you must delete the new record before you can restore the deleted one.
 
 > Name: `DuplicateExceptionRestoreRecycleBin`<br />
 > Code: `0x80044a02`<br />
 > Number: `-2147182279`<br />
 > Message: `Please delete the existing conflicting record '<Entity Platform Name>' with primary key '<Primary Key Name>' and primary key value '<Primary Key Value>' before attempting restore.`
 
-#### DuplicateExceptionEntityKeyRestoreRecycleBin
+#### Records with matching alternate key values will block restore
 
-Donot create records with similar Alternate Keys that were already deleted, this will prevent previous record was in deleted state to be restored. The new record will need to be deleted before previous record is restored.
+If you create a record that has the same alternate key column values as a deleted record, you can't restore it. If you do, you must delete the new record before you can restore the deleted one.
 
 > Name: `DuplicateExceptionEntityKeyRestoreRecycleBin`<br />
 > Code: `0x80049929`<br />
 > Number: `-2147182295`<br />
 > Message: `Duplicate entity key preventing restore of record '<Entity Platform Name>' with primary key '<Primary Key Name>' and primary key value '<Primary Key Value>'. See inner exception for entity key details.`
 
-#### PicklistValueOutOfRangeRecycleBin
+#### Records using removed Choice options can't restored
 
-Do not delete Picklist or Option Set values directly, instead rename them with (deprecated) tag, because it will prevent the records deleted at the time to be restored.
+If you delete an optionset option, and that option was used in a deleted record, you can't restore it because the option is now invalid. Before deleting an option set option, check that no records use that option, including deleted records.
 
 > Name: `PicklistValueOutOfRangeRecycleBin`<br />
 > Code: `0x80049949`<br />
@@ -1011,141 +1012,4 @@ The following tables are the result of the query found in [Detect which tables d
       `workflowcardconnections`<br />
       `workqueue`<br />
    :::column-end:::
-:::row-end:::
-
-
-
-
-
-
-## REMOVE BEFORE PUBLISHING: Markdown examples to delete when we are done
-
-Each `##` section has a navigation link at the top of the page. Introduce key capabilities with a section. You may want to use this when you link between articles.
-
-### Sub section
-
-Each sub section provides a 'link-able' section of the doc. You may want to use this when you link between articles.
-
-#### Sub-sub section
-
-You can divide your sub sections with linkable headings. You shouldn't go deeper than `####` if you can avoid it.
-
-## Tables
-
-Please use markdown tables. HTML tables will render, but are not preferred. Try not to use more than three columns.
-
-
-|Column1  |Column2  |Column3  |
-|---------|---------|---------|
-|Row1-1|Row2-1|Row2-1: When adding content to a row, all the content must be in a single line. <br /> If you need to add a break, use `<br />`.|
-|Row1-2|Row2-2|Row2-2|
-|Row1-3|Row2-3|Row2-3|
-|Row1-4|Row2-4|Row2-4|
-|Row1-5|Row2-5|Row2-5|
-
-## Images
-
-Put all your images in the media folder at the same level as the file.
-
-:::image type="content" source="media/dev-resources-menu.png" alt-text="A screenshot of the developer resources menu in Power Apps.":::
-
-## Code
-
-When you include multiple lines of code, use this:
-
-```csharp
-// Hello world
-```
-
-If you use a word in a sentence to refer to a specific term that shouldn't be localized, surround it with backtick characters: `IObservable`.
-
-
-
-## Links
-
-There are several types of links you can use:
-
-### Local links
-
-You can link to other articles in the same repo with relative paths: [Search for Dataverse records](search/overview.md) , or [Update and delete table rows using the Web API](webapi/update-delete-entities-using-web-api.md), or [Update and delete table rows using the SDK for .NET](org-service/entity-operations-update-delete.md).
-
-### Links to sections
-
-You can add links to headings of other sections of the same document: [Detect which tables do not have recycle bin enabled](#detect-which-tables-do-not-have-recycle-bin-enabled)
-
-You can link to headings of other sections of a different document: [DeleteMultiple Availability](deletemultiple.md#availability)
-
-You can link to a section of another document on Microsoft Learn: [Power Platform CLI](/power-platform/developer/cli/introduction)
-
-> [!NOTE]
-> If you change the heading (or someone else changes the heading), the link will break. You (or they) will get a build warning when that happens.
-
-### Other Microsoft Learn articles
-
-You can link to other articles in different repos by removing `https://learn.microsoft.com/en-us` from the URL. For example: [Microsoft Power Platform developer documentation](/power-platform/developer/).
-
-### Links to reference articles
-
-If you want to link to a reference topic for a property, use this pattern: <xref:System.String.Length>, or [String.Length Property](xref:System.String.Length), or [String.IndexOf Method](xref:System.String.IndexOf%2A). After you have added one link, subsequent mentions can just use back ticks: `IndexOf` method.
-
-The [Learn Authoring Pack](https://marketplace.visualstudio.com/items?itemName=docsmsft.docs-authoring-pack) provides a tool to make adding these easier when you are using a local clone of the repo.
-
-> [!NOTE]
-> I strongly recommend using VS Code with a local clone of the repo. Happy to give you a demo and help you get set up. [Learn more about using Visual Studio Code to work with our content](/bacx/make-major-changes?branch=main)
-
-Different ways to link to a class name:
-
-<!-- I prefer this  -->
-- [RecalcEngine class](xref:Microsoft.PowerFx.RecalcEngine)
-- <xref:Microsoft.PowerFx.RecalcEngine>
-- <xref:Microsoft.PowerFx.RecalcEngine?displayProperty=nameWithType>
-- <xref:Microsoft.PowerFx.RecalcEngine?displayProperty=fullName>
-
-## Numbering
-
-With markdown, don't set explicit numbers. Always use `1` and markdown will order them for you.
-
-1. First
-1. Second
-1. Third
-1. Fourth
-
-To add instructions within a list, add a new line and three characters:
-
-1. First
-   
-   1. First One
-   1. First Two
-   1. First Three
-
-1. Second
-1. Third
-   
-   1. Third One
-   1. Third Two
-   1. Third Three
-
-1. Fourth
-
-
-## Alerts
-
-There are several types of alerts you can use, but use them sparingly.
-
-> [!NOTE]
-> Information the user should notice even if skimming
-
-> [!TIP]
-> Optional information to help a user be more successful
-
-> [!IMPORTANT]
-> Essential information required for user success
-
-> [!CAUTION]
-> Negative potential consequences of an action
-
-> [!WARNING]
-> Dangerous certain consequences of an action
-
-
-
+:::row-end:::
