.. _bulk-load-transaction-log:

Bulk load transactions
-----------------------

.. _24.1|EKB-16560:


.. tip:: 

   :ref:`use-action-search-to-navigate-automate`


Overview 
...........

Once you run a bulk load transaction, you can view its transaction details on the **Transaction** log (accessible 
via the toolbar).



.. rubric:: Related topics 

*
  .. raw:: latex

     Transaction logging and audit in the Core Feature Guide 

  .. raw:: html

     <a href="concepts-transaction-logging-audit.html">Transaction logging and audit</a>

*
  .. raw:: latex

     View a transaction in the Core Feature Guide 

  .. raw:: html

     <a href="tasks-transaction.html">View a transaction</a>




View bulk load transaction details 
...................................

Click the toolbar icon to go to the **Transaction Log**. Bulk load transactions show in the log: 

.. image:: /src/images/bulk-transactions-log.png 

* In the list view, the bulk load is shown in the **Action** column of the log. If the bulk load 
  was scheduled, this is shown as a schedule with the detail column indicating it
  to be a bulk load. The **Action** column will show "Execute Bulk Load" or "Execute Schedule"
  respectively.
* The submitted, start, and stop time for the entire bulk load transaction is also shown.
* The Detail tab displays the name of the bulk loaded file as the workbook sheet number and the 
  number of successful rows out of the total, for example:

  ::
 
      [ 8/9 ] succeeded from [ 1 ] sheet in data_Users_bulkloadsheet.xlsx.
  
  
Checks are made to validate the user's access profile, the 
provided hierarchy information, and data constraints for the bulk load 
transaction when updating the target models. The parent bulk load 
transaction will show the error message if this validation fails and
no rows will be loaded.

Where rows are loaded, each row in the bulk load sheet appears 
as a sub-transaction within the bulk load transaction. The Message dialog displays the number of 
successful and failed rows loaded.

Failed asynchronous transactions display below the sub transactions. If the number of failed 
asynchronous transactions exceeds 10, these details display on a new tab on the page. 

.. image:: /src/images/failed-async-transactions.png 


For each loaded sheet, bulk load transactions are run in series for each row.
Multiple bulk load sheets can be loaded and these transactions will load 
in parallel.

Sheet rows can be processed in parallel. The sheet should then not contain 
multiple, sequence dependent models.  Refer to :ref:`bulk-load-sheet-layout`.

For each row of the bulk load sheet carrying out the default add action, 
a Create action is shown on the list of transactions. Sheet rows that 
led to a successful *Create* action have a *Success* status, while rows that failed 
show a *Fail* status. If a row fails, the load process continues. For failed 
actions, the transaction can be selected to show the error message.

If one or more rows of the sheet failed to load, the Bulk Load Sub Transaction 
shows a *Success* status, while the Log list will show "error" for failed
rows.

On the list of sub transactions, you can
inspect the details of each sub transaction. For example, the submitted, start, 
and stop time for the bulk load sub transaction corresponding with a row on the 
bulk load sheet is shown. In the case of a failed sub transaction, further 
information about the failure - such as the error message and row data - is 
shown in the sub transaction.

A canceled bulk load transaction means the Processing worksheet 
sub transaction, as well as all sub transactions within the worksheet 
transaction in a *Processing* or *Queued* state, will fail. 

For parallel transactions, multiple resource transactions may be in 
a *Queued* or *Processing* state. By default, 14 rows are processed in parallel. Refer to 
:ref:`bulk-load-sheet-layout` for details.

If a worksheet transaction fails as a result of 
bulk load transaction cancellation, subsequent worksheet tabs in the bulk 
load workbook will not be processed by the bulk loader.