This is just to give you a flavor of how it works in simple case.

Assuming you have an item CUSTOMER_ID, table CUSTOMER_INFO and a button called DELETE.

While in the design mode of your page;

1. GO to Processing
2. Right click on Validating
   1. Create Validation
      1. Identification = Check if exists
      2. Validation:
         1. Type No Rows returned
         2. SQL Query = SELECT NULL FROM CUSTOMER_INFO WHERE CUSTOMER_ID = :CUSTOMER_ID
      3. Error:
         1. Error Message = custom already exist, you can not delete.
      4. Server-side Condition:
         1. When Button Pressed = DELETE

It’s just a sketch you may want to accommodate to your needs.

Below is an example to download the CSV file using the Ajax process. To download the file in XLSX format, you need a third party package to convert the query result into the Excel format. The CSV file will also open in Excel.
Create a database procedure that will return the CLOB data type for the data return by the query having multiple tables:

Create or replace PROCEDURE emp_Csv(o_Clobdata OUT CLOB) IS 
l_Blob BLOB; 
l_Clob CLOB; 

BEGIN 

Dbms_Lob.Createtemporary(Lob_Loc => l_Clob, 
Cache => TRUE, 
Dur => Dbms_Lob.Call); 
SELECT Clob_Val 
INTO l_Clob 
FROM (SELECT Xmlcast(Xmlagg(Xmlelement(e, 
Col_Value || Chr(13) || 
Chr(10))) AS CLOB) AS Clob_Val, 
COUNT(*) AS Number_Of_Rows 
FROM (SELECT 'empno, ename, sal, mgrno, hiredate, deptno' AS Col_Value 
FROM Dual 
UNION ALL 
SELECT empno||',' ||ename||','|| sal||','|| mgrno||','|| hiredate||','|| deptno AS Col_Value 
FROM (SELECT empno, ename, sal, mgrno, hiredate, deptno from emp1
union
SELECT empno, ename, sal, mgrno, hiredate, deptno from emp2))); 

o_Clobdata := l_Clob; 
EXCEPTION 
WHEN OTHERS THEN 
NULL; 
END;

Then create an Ajax callback process in Oracle Apex to call the above procedure and convert CLOB to BLOB and download. Add the following code in the Ajax callback text area:

DECLARE
L_BLOB BLOB;
L_CLOB CLOB;
L_DEST_OFFSET INTEGER := 1;
L_SRC_OFFSET INTEGER := 1;
L_LANG_CONTEXT INTEGER := DBMS_LOB.DEFAULT_LANG_CTX;
L_WARNING INTEGER;
L_LENGTH INTEGER;
BEGIN

-- create new temporary BLOB
DBMS_LOB.CREATETEMPORARY(L_BLOB, FALSE);

--get CLOB
emp_csv( L_CLOB);

-- tranform the input CLOB into a BLOB of the desired charset
DBMS_LOB.CONVERTTOBLOB( DEST_LOB => L_BLOB,
SRC_CLOB => L_CLOB,
AMOUNT => DBMS_LOB.LOBMAXSIZE,
DEST_OFFSET => L_DEST_OFFSET,
SRC_OFFSET => L_SRC_OFFSET,
BLOB_CSID => NLS_CHARSET_ID('WE8MSWIN1252'),
LANG_CONTEXT => L_LANG_CONTEXT,
WARNING => L_WARNING
);

-- determine length for header
L_LENGTH := DBMS_LOB.GETLENGTH(L_BLOB);

-- first clear the header
HTP.FLUSH;
HTP.INIT;

-- create response header
OWA_UTIL.MIME_HEADER( 'text/csv', FALSE);

HTP.P('Content-length: ' || L_LENGTH);
HTP.P('Content-Disposition: attachment; filename="emp_data.csv"');
HTP.P('Set-Cookie: fileDownload=true; path=/');

OWA_UTIL.HTTP_HEADER_CLOSE;

-- download the BLOB
WPG_DOCLOAD.DOWNLOAD_FILE( L_BLOB );

-- stop APEX
-- APEX_APPLICATION.STOP_APEX_ENGINE;
EXCEPTION
WHEN OTHERS THEN
DBMS_LOB.FREETEMPORARY(L_BLOB);
RAISE;
END;

Now you can call the above Ajax callback process on the button click as follows:

f?p=&APP_ID.:0:&SESSION.:APPLICATION_PROCESS=download_emp_csv:NO

Where download_emp_csv is the Ajax process name.

Yes you can limit the columns to search on by simply doing the following:

Navigate to a column that you don’t want to the user to be able to search on, for example the EMPNO column.

Under the column properties scroll down to Enable Users To and turn off the Filter property. This will remove this column from the available list of columns to search through.

When you save and run the page you will notice that the EMPNO column no longer appears in the searchable list of columns under the magnifying glass.

Now, even with the default selection of All Columns, the search field will only search on the ENAME column.

Hope this helps!