The UDR File Editor allows the user to view and edit the content of UDR files.
The UDR file may be of any format as long as it has an associated decoder. The Open dialog enables decoder selection. Correspondingly, the Save dialog includes a selection of encoders to use.
Since UDRs often contain a large number of fields, it is possible to create a UDR View to select fields and be viewed directly as columns in the UDR list (select in the menu). Each UDR can also be opened in a separate dialog where all fields are available.
Note!
The UDR File Editor will by default only support input files up to size 3MB. If the file size exceeds this limit, the UDR File Editor will only read up to 3MB of the file and then stop, showing only the read records.
To support decoding of files larger than 3MB, the Desktop property mz.gui.udreditor.limit
must be set for the corresponding Desktop. See /wiki/spaces/MD/pages/2956946 in the System Administrator's Guide. Setting the property to yes
means the 3MB limit applies. Setting the property to no
will bypass the limitation mechanism, which may potentially cause out of memory errors in the Desktop.
Several UDR file editors can be used simultaneously, however avoid editing the same UDR from several different editors, since there is no functionality to handle real-time co-authoring.
To open the UDR File Editor, click the
button in the upper left part of the Desktop window, and then select from the menu.Setting | Description |
---|---|
UDR View | A list from which a UDR view may be selected. A UDR view is a user defined filter which displays additional columns containing UDR field data. If(None) is selected, the list will consist of two columns only: Pos and Type. However, if a file is opened, a third column Orig Pos will become visible as well. For further information, see UDR Views. |
Orig Pos | Shows the original position of the UDR. New indicates that the UDR did not exist prior to the last Save. |
Pos | The current position of the UDR. The order applies upon saving. |
Type | The UDR types |
| All columns following the Type column, will list the field names of the UDR type according to the UDR view selection. If there is no field with the defined name, No such field is stated. |
Ultra File Editor Menu
The main menu changes depending on which Configuration type that has been opened in the currently active tab. There is a set of standard menu items that are visible for all configurations and these are described in /wiki/spaces/MD/pages/3210150 in the /wiki/spaces/MD/pages/3214541.
The menu items that are specific for UDR File Editor are described in the following sections:
File Menu
Item | Description |
---|---|
Displays a dialog where the local file system can be browsed for files to open. The Decoder used for reading the file is also configured here. Full Decode is enabled by default, which ensures that any decoding errors are detected when the file is read. If this option is disabled, decoding errors may not be detected until the UDR fields are accessed. | |
Save As | Saves the selected UDRs with an option to encode in the available formats. |
Saves the selected UDRs in an ASCII file, which may be opened in any text editor. All UDRs are displayed as rows, where the fields are separated by any of the following:
Non-existing fields are marked | |
Prints a summary table based on the current UDR selection (the Table option). It is also possible to get a detailed printout (the Details option). In the latter case the UDRs will be presented the way they appear when you click on the button. |
Edit Menu
Item | Description |
---|---|
Bulk Edit... | Opens a new dialog from which a group of selected UDRs can be edited simultaneously. For further information, see Editing a Bulk of UDRs(3.0). |
UDR View | A list from which a UDR view may be selected. A UDR view is a user defined filter which displays additional columns containing UDR field data. If(None) is selected, the list will consist of two columns only: Pos and Type. However, if a file is opened, a third column Orig Pos will become visible as well. For further information, see UDR Views. |
This chapter includes the following sections:
Add Comment