tag:blogger.com,1999:blog-2980270584042445525.post4573049620007568985..comments2024-03-22T07:31:45.686-04:00Comments on Breaking Windows!: Exporting Labels with .XPO's in Dynamics AX 2009Anonymoushttp://www.blogger.com/profile/02941261036544906869noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2980270584042445525.post-49979688331341956752011-07-15T14:29:22.665-04:002011-07-15T14:29:22.665-04:00It may be worth noting also, that if the correspon...It may be worth noting also, that if the corresponding label file (.ald) for the labels is set to read-only, AX will deceptively allow you to make changes to the labels, or import them through the client. <br /><br />This initially behaves correctly, until you shut down the AOS. Since the AOS was never able to save the changes to the label file, they are lost, and will be missing when the AOS comes back online. <br /><br />I have not noticed any error messages related to this. So it can be hard to realize what is happening when labels keep disappearing. The base AX layers (such as sys and syp), appear to be writeable, so these can be modified and saved. But be mindful if you receive label files from an outside source, they may not mention that they've set them read-only.Vince Pertahttps://www.blogger.com/profile/17357880337075060704noreply@blogger.comtag:blogger.com,1999:blog-2980270584042445525.post-31835144012785295102011-05-09T09:10:44.666-04:002011-05-09T09:10:44.666-04:00It is worth noting that during the import, if you ...It is worth noting that during the import, if you do not check the "Show details" checkbox, all new labels which are imported get placed into the label file specified in "Create labels in the label file".<br /><br />I recommend always looking at details of the import, you would be surprised how often more, or less, of what you expect to be different actually is.<br /><br />Also, when reviewing the label tab, since there can potentially be many labels to review, sorting by the Action column, or filtering to exclude "Do not import label," is useful to since those can usually be safely ignore. Others should be checked to ensure they are as you expect. The "Import label" action indicates that the label will be brought in at the same label identifier as in the environment it was exported from. This is usually the desired result. But based on what labels already exist in the environment being imported into, it may decide to "Make a new label" or "Use an existing label." I often switch these to Import label in order to ensure that the import environment matches the export environment's labels as closely as possible.Vince Pertahttps://www.blogger.com/profile/17357880337075060704noreply@blogger.com