Finance | Project Operations, Human Resources, ...

Label wizard is not initiating

(4) Share

Report

Posted on by Ahmed Alam

Hi Experts,

Recently I have upgraded the VS from 2019 to 2022 for D365 F&O customization.

The problem is while I am trying to add Label file into project, system popup the item window but when click Add upon Dynamics 365 Items > Label File. System won’t initiate the Label wizard. It was working fine when I have 2019.

Any solution for this.

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (5)

Answers (0)

André Arnaud de Cal... 303,679 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Ahmed,

Can you tell us if you are using Visual Studio 2022 locally on your machine connected to a UDE environment or using a pre-built CHE or OneBox?

Was this reply helpful? Yes No
Navneeth Nagrajan 2,538 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

HI @Ahmed,

A few questions:

1. Have you upgraded VS using the DevToolsService(using the Platform Service Updates -> DevTools Service) or have you manually setup VS 2022?

2. Have you removed the D365 F&O Developer add-ins first and then installed the D365 Fo DevTools on top of VS2022?

3. Based on the question and understanding you are able to add new labels from the label editor but unable to open Find Labels from Dynamics 365 menu. Is this understanding correct?

Was this reply helpful? Yes No
Ahmed Alam 64 on at

Like (0)

Report
Copy link

Link copied!

Hi @André Arnaud de Calavon,

I have downloaded the VHD from LCS > Shared Asset Library which comes with VS 2019. As per the pop-up message to upgrade the VS, I have proceeded the upgrade, and the rest is Infront of you.

Was this reply helpful? Yes No
Ahmed Alam 64 on at

Like (1)

Report
Copy link

Link copied!

Hi @Navneeth Nagrajan,

1- I have upgraded the environment as pop-up message appear.
2- No.
3- I have following options available as standard VS ribbon and Find Label is working fine. The only problem till date is the Label wizard not initiated while I tried to add a Label File into my project.

Was this reply helpful? Yes No
Suggested answer

Navneeth Nagrajan 2,538 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @Ahmed,

Two last questions:

1. Are you able to open an existing label editor from your VS 2022 project? For example, something like this window are you able to open for existing labels?

2. Under the bin folder in PackagesLocalDirectory, have you compared the older and the newer versions of the label files under LabelC.exe.config?

A few suggestions:

1. Manually, one can't install the D365 FO tools manually on top of VS2022 with an existing Dev Tools setup on top of VS 2019. This will break some of the existing and working development tools.

2. The D365 FO Tools needs to be removed first and then one needs to setup the D365 Fo Tools from the DevTools Service available under the Service Update package (In case of manual upgrades of Dev Tools and Visual Studio). Related to DevTools Service, if you have upgraded your VM to a specific version then the DevTools should be automatically upgraded and should be a part of the VS2022 setup.

3. Try compiling your label files by running the LabelC.exe command. You should get an error message. If you get an error message then check your label file with <LabelId>. There must be some kind of duplicate entries in there. Post this step, synchronise the label files from version control like Azure DevOps Git or TFS and then create those label captions manually.
Compile command:
<%systemDirectory%>\AosService\PackagesLocalDirectory\bin\LabelC.exe -metadata="<%systemdirectory%>\AosService\PackagesLocalDirectory" -modelname="<modelname>" -output="<%systemdirectory%>\AosService\PackagesLocalDirectory\<modelname>\Resources" -outputlog="<%systemdirectory%>\AosService\PackagesLocalDirectory\<modelname>\<foldername> Ax.CompileLabels.log" -errlog="<%systemdirectory%>\AosService\PackagesLocalDirectory\<modelname>\<foldername> Ax.CompileLabels.xml"

This will generate the compiled files as .dll files in the location specified in the output parameter.

Hope this helps. Happy to answer questions, if any.

Was this reply helpful? Yes No