D365 Finance & Operation Change colour based on the environment

D365  Finance & Operation  Change color based on the environment


Step 1:

1. Log into a D365 F&O environment  as a systems administrator and navigate to your Settings > User options:

The system displays:

Creating a Label file in D365 Finance & Operations

Creating a Label file in D365 Finance & Operations

To create the label file, follow these steps:

1. Right-click on the project and select Add | New item... or use the keyboard

shortcut, Ctrl + Shift + A.

2. Choose Labels and Resources from the Operations Artifacts list.

3. From the list on the left, select Label File.

4. In the Name field, enter a short, but unique label name “Your Own Label Name”

5. Press Add.

6. In the Label file wizard, leave Label file ID as default.

It seems that we can specify a different name in this step, but the

previous only called this wizard with a suggested file name. The Label

file ID field contains both the ID and the file name that will be created.

7. Press Next.

8. In the language selection, move the languages from the left-hand list into the

right-hand list using the buttons. Only leave languages selected that you will

maintain. This involves creating a label in each language file.

This also applies to language with subtle differences, such as English

and Spanish. Even though the label will often be the same, we still

need to manually maintain each language file. Currently this also

means we have to be careful to ensure we give them the correct ID.

9. Press Next.

10. Check that the Summary page is correct, and press Finish.

Creating a new Model and Packages in D365 Finance & Operations

Creating a new Model and Packages in D365 Finance & Operations

1. Under the Dynamics 365 menu, choose Model Management | Create model....

2. The Model name is named as we would in AX 2012, and should be named like a

new type, such as <prefix><area/module><ShortName>.

3. Complete the first steps as follows:

Field Value

Model name  : In our case, our company is called Contoso, so our prefix will be Con,

the area of change is an existing module (WHS) and it is for general

extensions (extending standard objects without the customization).

It is therefore named ConWHSGeneralExtensions. You should use

your own prefix and prefixes, and the name for explained further in

the There's more... section.

Model publisher : Your organization's name.

Layer As follows:

ISV / vertical solution / add-on: ISV

VAR / Partner solution / add-on: VAR

Customer solution / add-on: CUS or USR

Version Leave as 1.0.0.0

You can update this to maintain a version of the model. This does not

auto-increment and is usually left as default.

Model description

A full description of the model for other developers to read.

Starting a New Project

Model display name :

Leave as default, which should be the Model name.

4. Press Next.

5. In the Select package page, choose Create new package.

If you choose Select existing package, it will mean that your model

will be placed under the package and is intended to over-layer the

elements in in that package. You cannot over-layer elements in

extension projects, but unless we absolutely must over-layer, always

choose Create new package.

6. Press Next.

7. We are now offered a list of packages that we can reference, these are listed as

package's name and the models that the package contains, check

ApplicationSuite and press Next.

Most of the elements in Operations are in ApplicationSuite; so,

unless our package doesn't need any standard, type this will always be

selected. The others we would select based on the elements we know

we will use. We can add more package references later, but if we know

which elements we will use, it saves some time..

8. The two check boxes, Create new project and Make this my default model for

new projects, should both be checked.

9. Press Finish.

10. This opens the New Project dialog. The project name is usually the same as the

package and Model name; then, enter the package name in the Name field.

11. The Location field must be changed; it will create the project in the default project

folder, but we linked C:Projects<initials/username> to source control. The

project must be created under this folder. So, in my case, Location must be

C:ProjectsSB.

12. The Solution name field should be left as the project name.

13. Ensure that both Create directory for solution and Add to source control are

checked.

14. Press OK.