Differences

This shows you the differences between two versions of the page.

--- novo_motion_schema_editor [2021/02/03 18:29] – [NovoMotion Schema Editor - Post Job Options Tab - SA Map Example] dlm
+++ novo_motion_schema_editor [2024/05/13 16:08] (current) – dlm
@@ Line 1: / Line 1: @@
+[[main_page|NovoMotion Outbound Menu]]
 ====== NovoMotion Schema Editor ======
@@ Line 62: / Line 63: @@
 |@LITERAL | Used to pass static data through the schema - @LITERAL:1 |
 |@FIELD | Field based on info  - @FIELD:info:delimiter:occurrence:numberOfOccurrences|
+|@FIELDS | Field for multi-value array.  Same as @FIELD |
 |@TM | Allows selection of a specific table master - @TM:tablenbr |
 |@CHANGE | Used to change a specific string from one literal to another - @CHANGE:info:from:to |
@@ Line 71: / Line 73: @@
 |@TRIM | Removes errant spaces from a string  - @TRIM:mvinfo |
 |@NULL | Returns a null character - @NULL |
+|@BLOAT | Use to expand (bloat) a dictionary to the value mark count dictated by another dictionary - @BLOAT:DictOne:BoatDict|
+|@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:info:from:to |
+|@CAT | Use U2 CATS to combine two arrays of data together - @CAT:info1:info2 |
+|@TIMESTAMP | transmit a record timestamp for when change / load event happened in U2. This is both date and time in SQL. |
+  * In SWAP CONVERT etc above, @AM @VM @SVM can be specified as IN or OUT strings.
   * Ordinal considerations: The precision and scale assigned to the ordinal are taken from the mvinfo dictionary. Because an ordinal is a number, the precision and scale should be changed to numeric with a scale of 3 or 4.
@@ Line 200: / 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.  See the [[sql_server_management_studio_example]] if you would like to review notes about the SQL Server tasks.
+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.  See the [[sql_server_management_studio_example|SQL Server Management Studio Example]] if you would like to review notes about the SQL Server tasks.
+If a SQL table has already been established and the schema needs to change, the user has the following options:
-**Additional Usage Notes:**  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.  This will drop the existing table  and replace the existing SQL column definitions.  Then use [[load_bci.action|LOAD.BCI.ACTION]]  to reload the data into the SQL table.
-  - Generate the SQL script through the Schema Editor, copy it, paste it into SQL Management Studio, and execute the script.  This will drop the existing table  and replace the existing SQL column definitions.  Then use [[load_bci.action]]  to reload the data into the SQL table.
+  - 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.  Next use [[load_bci.action|LOAD.BCI.ACTION]]  to reload the data into the SQL table.  This can be used when the SQL table has data that cannot be regenerated from the U2 server because the data has already been purged from that server or because the table is large and the data being added is new.
-  - 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.  Next use [[load_bci.action]] to reload the data into the SQL table.  This can be used when the SQL table has data that cannot be regenerated from the U2 server because the data has already been purged from that server or because the table is large and the data being added is new.
@@ Line 218: / Line 227: @@
+\\
+[[main_page|NovoMotion Outbound  Menu]]