Label file problem under Microsoft Visual Source Safe in AX 2012

(0) Share

Report

Posted on by Community Member

in our AX 2012 development environment we use Microsoft Visual Source Safe as the version control. let's called it as development server. each developer has their own isolate development environment and microsoft visual source safe client installed.

in development server, we imported an existing label file and created a new label file. then we add and check-in all objects including label files into version control. everything works as expected beside labels. they can be shown correctly in screens in development servers. but when developers synchronize with development server, not all labels synchronized to their environment.

in our case, there are over 1000 labels in the imported label file and over 100 labels in the newly created label file. but only about 100 labels in the imported label file synchronized to developers' machine and some labels in the newly created label files are missing after synchronization, meaning only label code and no text. when I exported label files in AOT in development server, same result as developer gets. if we check-out label file in development server, system prompts label @xxxx removed.

any idea what's wrong with it? thanks in advance.

*This post is locked for comments

I have the same question (0)

All responses (9)

Answers (0)

Suggested answer

Joris dG 17,775 on at

Like (0)

Report

Hi Jeff,

have you read this blog post by Martin Drab to see if this is somehow related to your issues?

dev.goshoom.net/.../label-ids-in-dynamics-ax-2012

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Joris

thanks for your responses.

yes, I did read Martin's blog before. but it doesn't relate with my issue. currently, we can check-in, check-out lable file. also system will asign temp label id like '@$AA1' and once check-in, it would be replaced with correct label Id.

my issue is if try to export label file in AOT->label files node, not all labels exported to xxx.ald and if developer syn label from development server, also not all labels synchronized to developers' environment.

I didn't find the table ModelElementLabel in AOT but there was a table named SysModelElementLabel under system documentations->tables. after synchronization is done in developers' environment, only a few records shown in that table. in my case, I got over 1000 labels in one label file, it should shown over 1000 records. but now it has only about 100 records.

Was this reply helpful? Yes No
Martin Dráb 237,880 Most Valuable Professional on at

Like (0)

Report

Hi Jeff, I'm not still sure what's the situation looks like in your environment. If you look into label files in VSS repository, do you see all expected labels? And do all environments use the same language?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Martin

thanks for your responses.

I checked label file in repository in both developers' environment and development server. label files exist in both environments. but if I checked labels with text editor like notepad. only a few labels included in the file. the label file which I imported is about 270KB in file size. but in the label files folder in respository is 1KB only.

yes, all environment are using the same language.

I also tried to delete all ali file in server folder and restart AOS service. but it doesn't help.

since labels are shown correctly in user screens in development server. so is it due to labels which saved in model store doesn't be flush to label files? if so, any way to flush manually?

Was this reply helpful? Yes No
Suggested answer

Bill 'Luther' Thompson on at

Like (0)

Report

Hello,

Label files can be "tricky" to work with. One thing you could try, is to create your labels on the Development system. Then, close the Dev environment, and restart the AOS. This should force everything to flush into the modelstore. Once that is done, restart the AOS, log in, and check the label changes into version control system.

Then, on the other environments, do the synchronize, stop the AOS, clear out the labels from (make a backup of this folder first) C:\Program Files\Microsoft Dynamics AX\60\Server\MicrosoftDynamicsAX\bin\Application\Appl\Standard. Then restart the AOS. This should force the update of all the label files that exist in the modelstore on the AOS. Then see if your labels are showing up in the system.

Best Regards,

Bill Thompson

Dynamics AX - Dynamics SureStep Online Support Engineer - Online Support Engineer

============================================================

When responding to posts, please 'Reply to Group' via your newsreader so that

others may learn and benefit from your issue.

============================================================

This posting is provided 'AS IS' with no warranties, and confers no rights.

============================================================

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Bill

thanks for your responeses.

I'm a little bit confused on your solution. since the label file already added into version control. do you mean I should try

1) check out the label file in label editor screen in development system

2) create new label. at this time, system assigns a temp label ID like '@$AA1' to new label

3) logout ax

4) restart AOS service in development system

5) login ax again

6) check in the label which checked out in 2). at this time system would assign a formal label ID

7) synchronize developers' environment with development system in order to retrieve new labels

8) stop AOS service in developers' environment

9) delete ald files in standard folder under server bin

10) restart AOS service in developers' environment

11) check if label is ok in developers' environment or not

is it?

Was this reply helpful? Yes No
Bill 'Luther' Thompson on at

Like (0)

Report

Hello,

Based on the previous posts, I was not sure if the label file that was checked into version control was correct or not (all entries in it). If you examined the label file that is stored in version control, and all label content does exist in that file, at that point, I would do a forced synchronized on a developer machine. After that, stop the Developer AOS, go out and clean out the application folder I gave you previously, and then start the AOS again. That should force all label files to be pulled from metadata by the AOS, and the "AOS specific version of the label files" to be recreated. Then, if you are not seeing anything, restart the AOS again, and log back in to see if everything now works.

Best Regards,

Bill Thompson

Dynamics AX - Dynamics SureStep Online Support Engineer - Online Support Engineer

============================================================

When responding to posts, please 'Reply to Group' via your newsreader so that

others may learn and benefit from your issue.

============================================================

This posting is provided 'AS IS' with no warranties, and confers no rights.

============================================================

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi, currently labels under version control are working as expected. although in some case, we have to synchronize labels several time in order get correct copy. so far, I still didn't find out the root cause.

thanks everyone

Was this reply helpful? Yes No
Suggested answer

Bill 'Luther' Thompson on at

Like (0)

Report

Hello,

Here is something to consider. Remember how label files work. When the labels are created, they are stored in temporary files. The labels are only committed to the actual label data file when the AOS has 'exclusive access' to the label file. This tends to occur only at the time of the AOS being shut down. What you may want to consider doing is prior to the commitment of the label data to your version control system, shut down, and then start the AOS service on the Developer machine. This should allow the labels that are stored in the temporary file to be committed to the main label file. Once that has been done, add the labels into Version Control and see if they 'take'.

It may not hurt to repeat the process on a different machine after a synchronize is done with Version Control when labels are involved. Do the synch, log out, and stop/start the AOS and see if that helps stabilize the label system for you.

Best Regards,

Bill Thompson

Dynamics AX - Dynamics Sure Step - Online Support Engineer

============================================================

When responding to posts, please 'Reply to Group' via your newsreader so that

others may learn and benefit from your issue.

============================================================

This posting is provided 'AS IS' with no warranties, and confers no rights.

============================================================

Was this reply helpful? Yes No