Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.


Symptoms

You may experience the problem with draft versions of GER configurations when working with the Electronic reporting (GER) framework. When you have a configuration that contains the version A (e.g. 1) of the residing in it component (model or format), and then consistently imported configurations containing the component’s version A+2 (3) and A+1 (2), you expect that the draft version of the residing component equals to the highest imported version A+2 (3).  Really, it equals to the version of the last imported configuration A+1 (2). You must select the version A+2 (3) and use the GET THIS VERSION function for it to get the highest version of the imported components in your draft version to apply new changes.

↑ Back to the top


Resolution

The changes in the hotfix contain the code modifications that resolve the described above issue. The logic of the draft version’s creation during a GER configuration’s import has been fixed to update the draft version only when the imported configuration contains a residing component version that is higher than the current one.

↑ Back to the top


More information

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained here in is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

↑ Back to the top


Article Info
Article ID : 4100259
Revision : 1
Created on : 3/27/2018
Published on : 3/27/2018
Exists online : False
Views : 157