Module 14: Database Manipulation

Justification:

1. The select forUpdate command indicates that the table buffer will alter the contents of the table and is typically used for inserting or deleting records, not simply reading them.
2. The “select” keyword is used to retrieve and read records.
3. Order by is not used to read records, but rather to order the resulting records that are returned in the select statement.
4. Select into is not used in X++ to read or retrieve records.

Related Lesson: Reading Records

Justification:

1. The “=+” operator is not valid in X++.
2. The “=” is not used in a where statement to indicate equivalency. It is used when assigning values to variables, for example.
3. The “!=” operator returns records that are NOT equivalent.
4. The “==” is a relational operator used in the where statement to determine equivalency.

Related Lesson: Reading Records

Justification:

1. “Info::box” is not a valid output statement.
2. The info keyword is used to output the value(s) to the screen in an informational display format
3. The warning keyword will create a warning output message.
4. The pause keyword is not supported in Dynamics AX.

Related Lesson: Reading Records

Justification:

1. ttsAbort will prevent the data from being written to the table and roll the transaction back to the state before the ttsBegin was called.
2. The insert method is called on table to insert data, but it does not control the transaction tracking system.
3. This is not a valid command used for transaction integrity.
4. This is correct. The ttsCommit command ensures there were no errors during the insertion process. After the ttsCommit is called, the data will be written to the given table.

Related Lesson: Data Insert

Justification:

1. insertRecord is not a valid method call.
2. InsertAll is not a valid method call.
3. The insert method is the correct method to call to insert a record or records into the table that the method is being called on.
4. InsertNow is not a valid method call.

Related Lesson: Data Insert

Justification:

1. Read is not a valid keyword to be used in a select statement or to update records.
2. The forUpdate keyword is used in a select statement to indicate the table is being selected for the purpose of updating or changing data.
3. Lock is not a valid keyword to be used in a select statement or to update records.
4. The firstOnly keyword is used to retrieve only the first record from the table.

Related Lesson: Data Updates

Justification:

1. The “==” is used as a relational operator between the field and the value of 1 in this example. This returns “true” when the two expressions are equal.
2. The “=” operator is an assignment operator. Therefore, it is used when assigning values to variables. It is not a relational operator.
3. The “+=” is an assignment operator that increments the value of the variable on the left by the value of the expression on the right.
4. The “!=” operator is a relational operator returns “true” if the expressions are NOT equal.  

Related Lesson: Data Updates

Justification:

1. The “==” is used as a relational operator. This returns “true” when the two expressions are equal, it does not assign any values.
2. The “=” is the correct operator to use to assign the value of the dbModel field to the value “Big Truck” in this example.
3. The “+=” is an assignment operator that increments the value of the variable on the left by the value of the expression on the right. It does not assign values.
4. The “!=” operator is a relational operator returns “true” if two expressions are NOT equal. It does assign values.

Related Lesson: Data Updates

Justification:

1. Drop is not a valid method call on the given table and does not delete records.
2. Kill is not a valid method call on the given table and does not delete records.
3. Deletefrom is not a valid method call on the given table and will not delete records.
4. The delete method on the table is called when records are to be deleted.

Related Lesson: Data Deletion

Justification:

1. a) The code performs a join between the two tables on SalesID, which means only related records, or records that exists in both locations for that field will be returned. Therefore, we will not see SO0001 in the output.
2. b) The three sales order IDs are correct, but they are in the wrong order because the order of the selects is based on the record ID on the sales line descending - resulting in SO0003 (highest recID on the lines), then SO0002, then finally SO0003 again (lowest recID on the lines).
   
   
3. c) The code performs a join between the two tables on SalesID, which means only related records, or records that exists in both locations for that field will be returned. Therefore, we will not see SO0001 in the output. We then specify to order the salesLine table in descending order based on the RecID field. The while loop will print the SalesID line by line in that order, which would yield the result: SO0003 SO0002 SO0003.
   
   
4. d) The code performs a join between the two tables on SalesID, which means only related records, or records that exists in both locations for that field will be returned. There is only one sales line with SalesID SO0002.

Related Lesson: Data Retrieval

Justification:

• ttsBegin- You mark the beginning of the transaction with ttsbegin.
• ttsCommit - You mark the successful end of a transaction with a ttscommit.
• ttsEnd is not a valid command for the transaction tracking system.
• ttsCommence is not a valid command for the transaction tracking system.
• ttsAbort - This can be used as an exception to make a transaction be aborted and rolled back to its state before the ttsbegin. You insert a ttsAbort wherever you want this to occur.

 

Related Lesson: Transaction Integrity Checking

Justification:

1. This statement will select all records from the CustTable organized by the index titled cityIdx, which is configured on the custTable.
2. This statement selects all records from the custTable and specifies the “city” field in the table to order by. The default direction order by is ascending order.
3. This statement selects all records in the CustTable and specifies to order by the city field in ascending order. This is the same as the default order. The order by clause will default to ascending order if none is specified as well.
4. This statement will not work because the index name is not city, but cityIdx.

Related Lesson: Data Retrieval

Justification:

1. True: This statement is true. The insert command is used on a table buffer.

 Related Lesson: Data Insert

Justification:

1. True: This statement is true. The update() method is called on a table to update its contents using a table buffer. The data is updated by assigning new values to the fields.

 Related Lesson: Data Updates

• A. Incorrect: The update method does not update multiple records without making multiple calls to the database.
• B. Incorrect: The doUpdate method does not update multiple records without making multiple calls to the database.
• C. Correct: The update_recordSet method updates multiple records with one call to the database and is the best method to use.
• D. Incorrect: The insert_recordSet method will create new records, not update existing records.

• A. Incorrect: A join would return customer data and sales order data where the customer was associated with a sales order.
• B. Incorrect: An outer join would return customer data and sales order data regardless of an association between them.
• C. Incorrect: An exists join would return customer data for customers who are associated with a sales order.
• D. Correct: A notExists join would return customer data for customers who are not associated with a sales order.

• A. Incorrect: The individual task modeling does not handle multiple records well.
• B. Incorrect: Because the run time varies between work items, the batch bundling approach does not handle the uneven workload well.
• C. Correct: The top picking approach handles multiple records and handles uneven workloads well.