---
# required metadata
title: [Topic name]
description: [Full description that appears in the search results. Often the first paragraph of your topic.]
author: [author's GitHub alias]
manager: AnnBe
ms.date: 06/20/2017
ms.topic: article
ms.prod:
ms.service: dynamics-ax-applications
ms.technology:
# optional metadata
# ms.search.form: [Operations AOT form name to tie this topic to]
audience: [Pick one: Application User/Developer/IT Pro]
# ms.devlang:
ms.reviewer: [Content Strategist microsoft alias]
ms.search.scope: [Which Operations client to show this topic as help for, to be set by content strategist, see list here: https://microsoft.sharepoint.com/teams/DynDoc/_layouts/15/WopiFrame.aspx?sourcedoc={23419e1c-eb64-42e9-aa9b-79875b428718}&action=edit&wd=target%28Core%20Dynamics%20AX%20CP%20requirements%2Eone%7C4CC185C0%2DEFAA%2D42CD%2D94B9%2D8F2A45E7F61A%2FVersions%20list%20for%20docs%20topics%7CC14BE630%2D5151%2D49D6%2D8305%2D554B5084593C%2F%29]
# ms.tgt_pltfrm:
# ms.custom: [used by loc for topics migrated from the wiki]
ms.search.region: [Global for most topics. Set Country/Region name for localizations]
# ms.search.industry: [leave blank for most, retail, public sector]
ms.author: [author's Microsoft alias]
ms.search.validFrom: [month/year of release that feature was introduced in, in format yyyy-mm-dd]
ms.dyn365.ops.version: [name of release that feature was introduced in, see list here: https://microsoft.sharepoint.com/teams/DynDoc/_layouts/15/WopiFrame.aspx?sourcedoc={23419e1c-eb64-42e9-aa9b-79875b428718}&action=edit&wd=target%28Core%20Dynamics%20AX%20CP%20requirements%2Eone%7C4CC185C0%2DEFAA%2D42CD%2D94B9%2D8F2A45E7F61A%2FVersions%20list%20for%20docs%20topics%7CC14BE630%2D5151%2D49D6%2D8305%2D554B5084593C%2F%29]
---
[!includebanner]
This Finance and Operations template contains examples of Markdown syntax, as well as guidance on setting the metadata. To get the most of it, you must view both the raw Markdown and the rendered view (for instance, the raw Markdown shows the metadata block, while the rendered view does not).
When creating a Markdown file, you should copy this template to a new file, fill out the metadata as specified below, set the H1 heading above to the title of the article, and delete the content.
The full metadata block is above (in the raw Markdown), divided into required fields and optional fields. DO NOT use a colon (:) in any of the metadata elements.
Here are some key things to note about metadata.
-
Required metadata
- title - The title will appear in search engine results. You can also add a pipe (|) followed by the product name (for example,
title: Action search). The title doesn't need be identical to the title in your H1 heading and it should contain 65 characters or less (including | PRODUCT NAME). - description - This is the full description that appears in the search results. Usually this is the first paragraph of your topic.
- author - This is your GitHub alias, which is required for ownership and sorting in GitHub.
- manager - Use "annbe" in this field.
- ms.date - This should be the first proposed publication date.
- ms.topic - Enter "article" here.
- ms.prod
- ms.service - Always use "Dynamics365Operations".
- ms.technology
- title - The title will appear in search engine results. You can also add a pipe (|) followed by the product name (for example,
-
Optional metadata
- audience - Use of these values: Application User, Developer, or IT Pro.
- ms.reviewer - This is the Microsoft alias of your Content Strategist.
- ms.custom
- ms.assetid - This is the GUID of the article that is used for internal tracking purposes. When creating a new Markdown file, get a GUID from https://www.guidgenerator.com.
- ms.search.region - Use "global" or enter a country-region value.
- ms.author - Use your Microsoft alias.
All basic and GitHub Flavored Markdown (GFM) is supported. For more information, see:
Markdown uses special characters such as *, `, and # for formatting. If you wish to include one of these characters in your content, you must do one of two things:
- Put a backslash before the special character to "escape" it (for example,
\*for a *) - Use the HTML entity code for the character (for example,
*for a *).
File names use the following rules:
- Contain only lowercase letters, numbers, and hyphens.
- No spaces or punctuation characters. Use the hyphens to separate words and numbers in the file name.
- Use action verbs that are specific, such as develop, buy, build, troubleshoot. No -ing words.
- No small words - don't include a, and, the, in, or, etc.
- Must be in Markdown and use the .md file extension.
- Keep file names short. They are part of the URL for your articles.
Use sentence-style capitalization. Do not overcapitalize.
Headings should use atx-style, that is, use 1-6 hash characters (#) at the start of the line to indicate a heading, corresponding to HTML headings levels H1 through H6. Examples of first- and second-level headers are used above.
There must be only one first-level heading (H1) in your topic, which will be displayed as the on-page title.
If your heading finishes with a # character, you need to add an extra # character in the end in order for the title to render correctly. For example, # Define a data method in C# #.
Second-level headings will generate the on-page TOC that appears in the "In this article" section under the on-page title.
Italics Use for files, folders, paths (for long items, split onto their own line) - new terms - URLs (unless rendered as links, which is the default).
Bold Use for UI elements.
To link to a header in the same Markdown file (also known as anchor links), you'll need to find the ID of the header that you're trying to link to. To confirm the ID, view the source of the rendered article, find the ID of the header (for example, id="blockquote"), and link using # + id (for example, #blockquote).
Note: You need to follow the casing of the header ID. In the following examples, the README.md file is all caps, so that's how this needs to be written in Markdown. Most IDs are lowercase.
The ID is auto-generated based on the header text. So, for example, given a unique section named ## Step 2, the ID would look like this id="step-2".
- Example: Chapter 1
To link to a Markdown file in the same repo, use relative links, including the ".md" at the end of the filename.
- Example: Readme
To link to a header in a Markdown file in the same repo, use relative linking + hashtag linking.
- Example: Links
To link to an external file, use the full URL as the link.
- Example: GitHub
If a URL appears in a Markdown file, it will be transformed into a clickable link.
- Example: http://www.github.com
- This
- Is
- An
- Ordered
- List
- Here
- comes
- an
- embedded
- Miss Scarlett
- Professor Plum
- ordered
- list
- This
- is
- a
- bulleted
- list
- This
- bulleted
- list
- Mrs. Peacock
- Mr. Green
- contains
- other
- Colonel Mustard
- Mrs. White
- lists
| Tables | Are | Cool |
|---|---|---|
| col 3 is | right-aligned | $1600 |
| col 2 is | centered | $12 |
| col 1 is default | left-aligned | $1 |
You can use a Markdown table generator tool to help creating them more easily.
Use three backticks (```) to begin and end a code example block . You an also indent a line to have it rendered as a code example.
function fancyAlert(arg) {
if(arg) {
$.docs({div:'#foo'})
}
}
Use backticks (`) for inline code. Use inline code for command-line commands, database table and column names, and language keywords.
The drought had lasted now for ten million years, and the reign of the terrible lizards had long since ended. Here on the Equator, in the continent which would one day be known as Africa, the battle for existence had reached a new climax of ferocity, and the victor was not yet in sight. In this barren and desiccated land, only the small or the swift or the fierce could flourish, or even hope to survive.
docs.microsoft provides a few additional extensions to GitHub Flavored Markdown.
It's important to use the following alert styles so they render with the proper style in the documentation site. However, the rendering engine on GitHub doesn't diferentiate them.
Note
This is a NOTE
Warning
This is a WARNING
Tip
This is a TIP
Important
This is IMPORTANT
And they'll render like this:
