Hotfix til kontrol og aktion ID tildeling til NAV 2009
Overview
Language Modules
In Microsoft Dynamics NAV 2009, language modules support the new three-tier architecture.
When you change the language in the RoleTailored client, messages from the Microsoft
Dynamics NAV Server service, Microsoft Office Outlook integration, and Employee
Portal are displayed in the same language.
The readme file, which is included with the language module, has been updated
to describe how to import new files for the RoleTailored client, Microsoft Dynamics
NAV Server service, Outlook integration, and Employee Portal. Because the caption
IDs are changed by the control and action ID assignment hotfix, you must install
the hotfix first and then install language modules so that the language modules
work correctly.
IMPORTANT NOTICE TO CUSTOMERS
We recommend that you contact your Microsoft Dynamics Partner before installing
service packs or hot fixes. It is important to verify that your environment is
compatible with the service pack(s), hot fix(es), or download(s) being installed.
A service pack, hot fix, or download may cause interoperability issues with customizations,
and third-party products that work with your Microsoft Dynamics solution.
Problem
When converting a form object to a page object, the transformation tool generally
applies one-to-one ID mappings between the form and page controls and actions.
A control on a transformed page has the same ID as its corresponding control on
the source form.
However, in some cases, the controls will be assigned a new ID by the transformation
tool:
- If one-to-one mapping of controls is not possible.
- If new controls have been added to the page and do not originate from the source
form.
- If controls exist on the source form but are going to be moved onto another form
or page.
The automatically generated IDs are assigned consecutive IDs in a range from
1,900,000,000 and higher. For example, if a partner adds a tab to a tab control
in a page or adds an info part, the subsequent control IDs are offset by 1. The
partner would then need to manually update the captions for those controls.
Cause
Page translation into a non-ENU language is based on translating strings that
are associated with control IDs. If the source form is transformed so that controls
or actions on the resulting page have different IDs, then the translation file,
which is based on the old control IDs, is not correctly applied to the new page.
Partners may need to implement their solution on top of a transformed customer
installation. In this case, the source forms that were used in the transformation
may be different. Because the pages did not come from the same source, controls
on the same page may have different control IDs. This significantly complicates
the page merge process and requires manually updating the captions for those controls.
Example:
Form ID=10, PageNames=General,Invoicing,Shipping is transformed to three controls
of Type=Group (FastTabs), with control IDs of 1, 1900000001, and 1900000002 on
the page.
If you modify the source form to include an additional FastTab, such as PageNames=General,OTHER,Invoicing,Shipping,
and retransform the form to a page, then the FastTab controls on the resulting
page do not get IDs 1, 1900000001, 1900000002, and 1900000003 as expected. Instead,
the IDs for the Invoicing and Shipping FastTabs were changed by incrementing them
by 1.
Resolution
The hotfix contains updated transformation Tool and databases with new control
IDs for pages and reports (request pages) and updated language modules.
The updated transformation tool will generate predictable and reproducible IDs
based on the control’s caption by using a hash function. Because many autogenerated
controls will get new IDs, the language packs have also been updated.
In addition to the new way of generating IDs, you can also manually assign control
IDs with the transformation input.
After applying this hotfix, use the following steps when transforming forms to
pages:
- Export language modules for all pages.
- Export forms.
- Transform all forms.
- Import pages.
- Import language modules for pages.
Example
A customized page ID=10, which is produced by transforming the source form ID=10,
with FastTabs=General, OTHER, Invoicing, Shipping, must be merged with the core
page ID=10, where FastTabs=General, Invoicing, Shipping have the IDs 1, 1900000001,
and 1900000002, respectively.
In the input file, you can specify an ID, such as 3000000001, for the Group control,
which is the Other FastTab. When you transform the form to a page, the FastTabs
on the resulting page receive the IDs 1, 3000000001, 1900000001, and 1900000002,
respectively.
If you do not specify an ID in the input file, then the tool behaves in the same
way as described in the previous section.
Dato: November 2009
Dette link er flyttet til vores nye udgave af navisionguider (www.dnav.dk) som du finder her: http://dnav.dk/content/hotfix-til-kontrol-og-aktion-id-tildeling-til-nav-2009
Denne artikel vil dog kunne benyttes et stykke tid endnu.
Til toppen af sidenGuldmedlemsskab påkrævet
Denne artikel kræver et guldmedlemsskab
For at læse resten af denne artikel skal du være guldmedlem!
Som guld medlem får du adgang til flere artikler, tips og guider end almindelige
medlemmer. Samtidigt støtter du det store arbejde vi lægger i hjemmesiden.
Guld medlemskabet giver dig mulighed for at se
vores videoer fra én computer i abonnementsperioden.
Læs mere om guldmedlemsskabet her.
Du skal være logget ind før du kan se eller skrive kommentarer til de forskellige indlæg. Klik her for at logge ind, eller oprette en bruger.
