Overview

You want to pull more than one event from a queue at a time from the user's interface, instead of doing it individually.

Information

By design, you can assign only one event at a time to one user from the Resource One home page. However, you can use pull more than one event by taking the ownership of the events directly from the database, in batches. To do so, check the following section.

If you want to proceed with the queries mentioned in the following section, please make sure you back up your entire database, and more precisely, the dbo.Events table, which can be found in the production BANK DB, because once you execute the queries listed below, the data will be lost/modified and will be unrecoverable. You can use the method described in the Backing Up Tables for Security KB Article for this purpose.

Input information

To get these records eliminated from the database, you must first reunite the following information:

• The name of the user considered the new owner. (First and last name)
• A list of the events that will belong to this user in CSV format.

Query to execute

First, let's get the user's ID. To do so, execute this query:

select * 
from users 
where first_name = '<first_name>' 
and last_name = '<last_name>'

For this example, we will use:

select *
from users
where first_name = 'Ronald'
and last_name = 'Reagan'

It will fetch a User_ID from the database:

Now, lets create a temporary table in SQL Server with the name events_temp. Ensure that the table has one nvarchar (MAX) column named event_name.

create table events_temp (
event_name nvarchar(MAX)
)

You have to import the CSV file you created previously into this new table. There are many ways to do so, we can recommend the following one, but you can use one of your preference:

• Import csv into SQL server (with query OR without query using SSMS)

Since we have the events that we want to assign to this new user loaded in a table, we must now update the user that is currently owner of those records in the Events table, by matching the information we have using a query like the following one:

UPDATE Events 
SET user_id = '<ID_found_in_first_step>', queue_id = NULL
WHERE event_name IN 
(
SELECT event_name 
FROM events_temp
)

In our example, it would be:

UPDATE Events
SET user_id = '<87F08013-3E85-4711-9056-23C2BE56CED9>', queue_id = NULL
WHERE event_name IN
(
SELECT event_name
FROM events_temp
)

This last query is the query that must be used to update the Events table, setting the User_ID of Ronald Reagan and the Queue_ID to NULL to the events whose names are repeated in the events_temp table, which is the CSV file that was previously created.

Contacting Support

If you want support to execute this backend modification on your behalf, please contact the Support staff and provide them with the information described in the Input information section.

A customer support representative will contact you back with the result of the execution of the aforementioned query.