This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
novo_motion_schema_editor [2021/02/03 21:47] dlm |
novo_motion_schema_editor [2021/06/08 14:16] mah update @variables |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | [[main_page|NovoMotion Outbound Menu]] | ||
====== NovoMotion Schema Editor ====== | ====== NovoMotion Schema Editor ====== | ||
Line 10: | Line 11: | ||
- | {{: | ||
+ | {{: | ||
Line 54: | Line 55: | ||
- | * U2 dictionary is the name of the base dictionary item (for the selected file) within the U2 environment. (I-descriptors are also supported. I-descriptors that use the SUBR keyword or that execute a TRANS to translate to another file should be used with caution. Warnings are sent to the user if they chooses | + | * U2 dictionary is the name of the base dictionary item (for the selected file) within the U2 environment. (I-descriptors are also supported. I-descriptors that use the SUBR keyword or that execute a TRANS to translate to another file should be used with caution. Warnings are sent to users if they choose |
+ | ^ **Key Word**^ **Description** | | ||
+ | |@MULTIVALUEID |Current suggestion is to use multiple primary keys instead of this. However, it is used to explode the controlling attribute of a multi-valued set @MULTIVALUEID: | ||
+ | |@ORDINAL |Assigns a numeric sequence to the value - @ORDINAL: | ||
+ | |@ACTION | Used to specify a delete or insert event | | ||
+ | |@LITERAL | Used to pass static data through the schema - @LITERAL:1 | | ||
+ | |@FIELD | Field based on info - @FIELD: | ||
+ | |@FIELDS | Field for multi-value array. | ||
+ | |@TM | Allows selection of a specific table master - @TM: | ||
+ | |@CHANGE | Used to change a specific string from one literal to another - @CHANGE: | ||
+ | |@CONVERT | Used to change multiple characters from one character to another - @CONVERT: | ||
+ | |@ICONV | Used to convert a string to internal format | ||
+ | |@OCONV | Used to convert a string to external format | ||
+ | |@FMT | Used to format a string | ||
+ | |@NOT | The reverse of a string evaluation - @NOT:mvinfo | | ||
+ | |@TRIM | Removes errant spaces from a string | ||
+ | |@NULL | Returns a null character - @NULL | | ||
+ | |@BLOAT | TBD | | ||
+ | |@USER | Sends the U2 user ID who caused the record change event, or load event | | ||
+ | |@SWAP | Used to change string from one string to another - @SWAP: | ||
+ | |@CAT | Use U2 CATS to combine two arrays of data together - @CAT: | ||
+ | |@TIMESTAMP | transmit a record timestamp for when change / load event happened in U2. This is both date and time in SQL. | | ||
- | * @MULTIVALUEID - Current suggestion is to use multiple primary keys instead of this. However, it is used to explode the controlling attribute of a multi-valued set @MULTIVALUEID: | ||
- | |||
- | * @ORDINAL - Assigns a numeric sequence to the value - @ORDINAL: | ||
- | |||
- | |||
- | * @ACTION - Used to specify a delete or insert event | ||
- | |||
- | |||
- | * @LITERAL - Used to pass static data through the schema - @LITERAL: | ||
- | |||
- | |||
- | * @FIELD - Field based on info - @FIELD: | ||
- | |||
- | |||
- | * @TM - Allows selection of a specific table master - @TM: | ||
- | |||
- | |||
- | * @CHANGE - Used to change a specific string from one literal to another - @CHANGE: | ||
- | |||
- | |||
- | * @CONVERT - Used to change multiple characters from one character to another - @CONVERT: | ||
- | |||
- | |||
- | * @ICONV - Used to convert a string to internal format | ||
- | |||
- | |||
- | * @OCONV - Used to convert a string to external format | ||
- | |||
- | |||
- | * @FMT - Used to format a string | ||
- | |||
- | |||
- | * @NOT - The reverse of a string evaluation - @NOT: | ||
- | |||
- | |||
- | * @TRIM - Removes errant spaces from a string | ||
- | |||
- | |||
- | * @NULL - Returns a null character - @NULL | ||
+ | * In SWAP CONVERT etc above, @AM @VM @SVM can be specified as IN or OUT strings. | ||
* Ordinal considerations: | * Ordinal considerations: | ||
Line 113: | Line 97: | ||
- | {{file_novo_schema2.jpg}} | + | {{: |
Line 128: | Line 112: | ||
- | ==== NovoMotion Schema Editor - SQL Options tab - SA map example | + | ==== NovoMotion Schema Editor - SQL Options tab - SA Map Example |
- | + | {{: | |
- | {{file_novo_schema3.jpg}} | + | |
Line 154: | Line 137: | ||
- | ==== NovoMotion Schema Editor - Post Job Options | + | ==== NovoMotion Schema Editor - Post Job Options |
- | {{file_novo_schema4.jpg}} | + | {{: |
Line 178: | Line 161: | ||
- | The function contains the following drop down menus: | + | ==== NovoMotion Schema Editor - Drop Down Menus ==== |
- | * **File** | + | === File === |
+ | |||
Line 201: | Line 186: | ||
- | * **Edit** | + | === Edit === |
Line 211: | Line 197: | ||
- | * **Tools** | + | === Tools === |
Line 224: | Line 210: | ||
- | **Note:** The Generate SQL Script is used when one wants to generate script to create the SQL table (See the Creating a SQL script information) to avoid the necessity of creating the SQL table by hand. This is often used multiple times during the development of new schema to perfect the information between U2 and SQL. | + | Note: The Generate SQL Script is used when one wants to generate script to create the SQL table (see [[creating_a_sql_script|Creating a SQL Script]]) to avoid the necessity of creating the SQL table by hand. This is often used multiple times during the development of new schema to perfect the information between U2 and SQL. |
- | The SQL script can be pasted into SQL Management Studio and executed. It will drop any existing SQL table of the name defined in the schema and re-create it with the columns defined in the schema. It does this for both the base SQL table and - if an @ACTION row exists - for the parallel SQL trigger table. | + | The SQL script can be pasted into SQL Management Studio and executed. It will drop any existing SQL table of the name defined in the schema and re-create it with the columns defined in the schema. It does this for both the base SQL table and - if an @ACTION row exists - for the parallel SQL trigger table. |
+ | If a SQL table has already been established and the schema needs to change, the user has the following options: | ||
+ | - Generate the SQL script through the Schema Editor, copy it, paste it into SQL Management Studio, and execute the script. | ||
+ | - Change, add, or delete the desired information in the schema via the Schema Editor, then make the same changes to the SQL table via SQL tools. | ||
- | **Additional Usage Notes: | ||
- | - Generate the SQL script through the Schema Editor, copy it, paste it into SQL Management Studio, and execute the script. | ||
- | - Change, add, or delete the desired information in the schema via the Schema Editor, then make the same changes to the SQL table via SQL tools. | ||
- | + | === Help === | |
- | * **Help** | + | |
Line 242: | Line 227: | ||
- | + | \\ | |
+ | [[main_page|NovoMotion Outbound |