Differences

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

--- novo_motion_schema_editor [2021/02/03 18:36] – [NovoMotion Schema Editor - Drop Down Menus] 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|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|[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:
@@ Line 217: / Line 227: @@
+\\
+[[main_page|NovoMotion Outbound  Menu]]