|1226 day(s) ago||#250|
Date: 2017-01-15 19:34:16
FAQ - Frequently Asked Questions on Form Design Aid (FDA) in JDE E1Q1 - How can I determine what tables are updated by a specific form?
In order to determine what tables are updated by a specific form, you must determine the business view being used by the form. In order to do this, double click on the form within Form Design Aid. The description of the business view will display on the section properties form. Then within Object Management Workbench, you can search for the business view based on its description. Once you locate the business view, add it to a project and select design. Then select the option for the BUSINESS VIEW Design Aid. Within Business View Design Aid you can determine the table(s) that are included in the business view. This shows what tables will be updated by the form using that business view.
Q2 - How do you use a Combo Box?
The Combo Box has limited functionality within the software. It was originally designed for web use only, but can be used on a Window`s client also. To use a combo box, it needs to be associated to a DATA DICTIONARY item that points to a User Defined Code table. Then the combo box will display a list of the User Define Code values in the pull down window.
The steps to accomplish this within Form Design Aid are:
Q3 - How do you make Radio Buttons mutually exclusive?
Associating two or more Radio Buttons to the same data dictionary or database item makes the Radio Buttons mutually EXCLUSIVE.
Q4 - What determines the value that is returned from a Search and Select Form?
The value that is returned from a Search and Select Form is based on the DATA STRUCTURE that is assigned to that form. Generally the data structure associated with a Search and Select Form should only contain one item in the data structure and that is the value that you wish to return from the form.
Q5 - Can you modify a version of an Interactive Application within Form Design Aid?
NO. Versions of interactive applications do not have specifications. All design changes to an interactive application must be made at the template level. Multiple versions of Interactive Applications are used only to establish different processing option values for the application.
Q6 - How does a form that allows for adds and updates determine whether it is in Add mode or Update mode?
Upon initially opening a form, a SQL select occurs based on the KEY VALUES of the form. If a record is retrieved from that select statement, then the form is in Update mode. This generally occurs when data is passed to the form within the form interconnect. If no record is retrieved, then the form is in Add mode. This generally occurs when calling the form without passing data into the form interconnect.
If a corrupt record exists in the table with all blanks/nulls in the key fields, the application will select it upon initially opening the form and put the form into update mode. It will not go into add mode unless no record is found when doing the select. Removing the corrupt record will resolve this potential issue.
Q7 - How do I indicate that a field is a required field on a form and have an error result if the field is left blank?
Within the Control Options for a field, there is a check box for "Required Entry Field". Selecting this check box indicates that a field is required and will provide an automatic error at runtime if the field is left blank. This option is accessed by selecting the OPTIONS button within the Control properties.
Q8 - When attempting to change the font on a field in FDA, I am not seeing the change?
The runtime engine has NEVER supported changing the font using the font option on the individual fields on a form even though this option does exist within FDA. Edit controls can be changed by using the "SetEditControlFont" system function. Generally this should be done on an event such as “Post Dialog is Initialized”. When you need to change font on static text, development has recommended the use of a text block control rather than static text. Font can be changed within FDA on a text block control. Fonts cannot be changed on static text. Therefore, with the combination of the “SetEditControlFont” system function and using text block controls rather than static text, you should be able to achieve the desired font changes on the fields on the form.
Q9 - I have created a new Row/Form Exit on my Application within FDA, however, when I run the application, I do not see the newly created Exit?
If any existing "HC" type USER OVERRIDES exist for the application, these user overrides are read and used when displaying the menu-bar and toolbar options for the application. In order to see any new exits created within design, locate any existing "HC" type user overrides for the application in the User Overrides application (P98950). Delete these user overrides. Then when running the application, the new exit created will display.
Q10 - When accessing my application, the sequence button on the toolbar and the sequence grid option are disabled? How do I enable this sequence option?
There is a grid property within FDA for "Hide Query by Example". When this option is selected, it not only HIDES the QBE line for the grid, but also DISABLES the grid sequence option. In order to enable this grid sequence option, the QBE line must be displayed by not selecting the option to "Hide Query by Example".
Q11 - How do I define a grid within a form in an application to work with Multiple Select?
The steps to setup a grid to allow for multiple select are to mark the Multiple Select grid property for the grid and select the "Repeat for Grid" setting under the Options pull down within the event rules defined for the menu/toolbar exit. Multiple select will ONLY work when the “interconnect” is not defined as modeless.
Q12 - How can I add a Bitmap to a Row or Form Exit?
A bitmap strip can be assigned to the BEGINNING category of menu/toolbar exits. Then all exits within that category will have the bitmap strip available and individual bitmaps can be selected for each exit.
Q13 - Is there a way to prevent a Header Detail form from exiting upon pressing the OK button?
If the interconnect that is used to call the Header Detail is defined as a MODELESS interconnect, the form will not exit upon pressing the OK button. If the Header Detail has been defined as the entry point, there is currently no way to prevent the form from exiting when the OK button is pressed.
Q14 - How do I get a Header Detail to automatically load the grid with the appropriate information when the form is opened through a Form Interconnect?
Create the appropriate key fields as filter fields in the HEADER portion of the Header Detail form. Select the grid property option of "Automatically Find on Entry" to preload the grid upon entry into the form based on the key values populated in the header through the form interconnect.
Q15 - When making modifications to a standard EnterpriseOne application such as Sales Order Entry (P4210), even though I add a new business view field to the grid, the field is not being populated to the table when records are added or updated in the application?
Many of the large transaction entry applications within the EnterpriseOne software use Master Business Functions to add and update records to the tables rather than using the business view. The forms are defined to update using these Master Business Functions rather than using the business view, so adding a new business view field will NOT update the table. In order to update the table, the new field must be passed to the appropriate parameter within the data structure of the Master Business Function (assuming the field is available within this data structure). This is true of numerous standard EnterpriseOne applications including Purchase Order Entry (P4310), Sales Order Entry (P4210), Voucher Entry (P0411), Invoice Entry (P03B11) and Journal Entries (P0911).
Q16 - I have made some changes to my custom table and added some additional fields. I have added these to the Business View and Form, however, I am not seeing the new fields on my selects and they are not being updated to the table on inserts or updates? AS400 Specific
On the AS400, SQL packages are created when doing selects and updates. If changes are made to a table, prior to being able to see the new fields on selects or update the new fields on inserts or updates, the SQL packages on the AS400 must be DELETED. This requires that all users be off the system, the services stopped, and then ALL SQL packages created by EnterpriseOne Software deleted. Once this has been done and services restarted, the new fields added to the table will display on selects and update on inserts and updates.
Q17 - How can I determine within Form Design Aid if Vocabulary Overrides exist for any fields on the form?
Any controls on a form that have had the text overridden and a vocabulary override exists will display with a GREEN triangle in the lower right hand corner of the control. Whenever a field has a text override, the description of the field at runtime will come from the text vocabulary override rather than from the description of the field within the Data Dictionary.
Q18 - When performing an add or update on my custom form, the information is not being updated appropriately to my tables.
Turning ON logging within the jde.ini will produce logging messages in the jdedebug.log that will show the SQL statements that are a result of pressing the Find button or performing an Add or Update within a form. These SQL statements will show what data and tables the system is attempting to update. Reviewing these SQL statements can provide important information as to why an update is not successful.
Q19 - How can I specify a default radio button on a form?
The STEPS to accomplish this within Form Design Aid are:
1. Create two or more radio buttons.
2. Highlight one of the radio buttons and select the menu exit for Edit.
3. Select Associate | Data dictionary item
4. Find your data item by entering it into the QBE line and clicking the find button (or Alt - I)
5. Select the data item and drag it onto the top of the selected radio button.
6. Highlight the next radio button and then repeat number 5
7. Follow these steps until the added radio buttons are associated with the same data dictionary or database item. This makes the radio buttons mutually exclusive (only one can be selected).
8. At this point, if nothing else is done, the first radio button created will be the default radio button, no matter what order the buttons are in. This means that a simple way of setting the default radio button is to create the default radio button first. Note: Starting with release Xe, the last radio button created will be set as the default.
To change the default, do the following steps.
9. Associate each of the radio buttons with a data dictionary item that edits against a User Defined Code (UDC) table.
10. Go into the properties of each of the radio buttons and set the title. (Starting in release Xe, when the title is changed the lower right corner label box will turn green to indicate it has been changed.) Also in the properties, set each radio button to a different UDC value
11. In the event rules for the form, in the "Post Dialog is Initialized" event, set one of the radio button variables, to the value of the radio button that is to be the default radio button, when the form displays.
Q20 - How is QBE Functionality set in FDA? What causes a QBE Column to be disabled or greyed-out?
Grid columns within an application NEED to be Business View columns, rather than Data Dictionary columns in order to have an enabled QBE column at run-time. You can check the column properties to see if the data item has an associated table name to determine if the data item is from the business view. Also, a blue triangle in the corner of a grid column indicates it is a business view field. A yellow triangle indicates a data dictionary field. The QBE column will always be disabled for data dictionary or variable columns that are not part of the business view.
QBE can also be disabled within Object Configuration Manager (OCM). Go to the OCM record and check to see if the table is set up as not allowing QBE. This can be done by following these steps:
|Disclaimer:||Most of the posts in this blog cater solutions/suggestions/workaround to issues for specific tools release or JDE E1 version and are just information only. Please be carefule while applying it in your environment. JDEthread will not be responsible for any data loss or spec corruption (if any).|
Copyright © 2010 - 2020 JDEthread.in