I have a series of OneBox Dev/Test environments within an LCS project, with a couple used as Dev boxes to work on D365F&O extensions, and a couple used as Test and Config environments. These latter two only have the extensions deployed via an all-in-one deployable package, built using a hosted build agent, to include some ISV solutions alongside the extension solution the Devs are working on. In the Test environment, the labels from the ISV solutions are showing the @ABC:LabelId text in the web interface, where the Config environment (with the same all-in-one package deployed, same PU applied) is correctly showing the label text. The label file definitely includes text for the language of the accessing user, and the custom label text for our solution under development are displayed without issue.
I suspect that the Test environment had an early version of the deployable package applied when the ISV binaries hadn't been checked in to source control, so it feels possible that some kind of hangover effect has led to the labels not being visible, but there have been multiple machine restarts & a couple of subsequent package deployments (with label text consistently displaying in Config, which has only ever seen full deployable packages applied) since then without the label text showing up. Having found a thread describing similar behaviour, whilst the AX 2012 upgrade described there isn't relevant to my situation, I tried deleting the K:\AosService\PackagesLocalDirectory model folders for the ISV solution before deploying the latest package, but the behaviour persists. Could anyone please suggest what else I can do to refresh/resolve labels?
