Button to Fire IOL Script

Display a table report and paste this code into the console:

var dbidTable = "your table dbid";
$("table[qbdbid=" + dbidTable  + "] tr:first").before("<tr><td><a href=# id=QBU_Button class='Vibrant Success'>Pinch Me</a></td></tr>");
$("#QBU_Button").on("click", function(event) {
  alert("Ouch!");
});

It will splice a button atop the report and establish a listener for clicks on that button. When you click the button the callback will execute in this case alerting a message.

To implement this you could set up the IOL technique and include the IOL field [-] in the report - typically as the last column of the report to not call attention to itself (it will be a skinny column). The formula for [-] will be just this:

[iol] & "myScript.js" & [/iol]

The code snippet you pasted is for setting up a button on each row of a report:

[iol] & "myScript.js" & [/iol]
&
"<a class='QBU_Button Vibrant Success'>Button</a>"

Although it would normally pass the [Record ID#] through a data attribute:

[iol] & "myScript.js" & [/iol]
&
"<a class='QBU_Button Vibrant Success' " &
"  data-rid='" & [Record ID#] & "'" &
">Button</a>"

And obtain the record id in the script as follows:

  $("a.QBU_Button").on("click", function(event) {
    var rid = this.dataset.rid;
    var message = 'You clicked on record with rid=${rid}';
    alert(message);

  });

BTW, I think it is best to always name your code page with the prefix "module" followed by the name of the table and perhaps the function of the script. Examples:

moduleTable1.js
moduleTable1Form1.js
moduleTable1UpdateSomething.js

Hey Dan,

I ran my code within the console and it does everything I needed. Displays a button above the table, fires off my script, and completes my task.

However, this script does not execute when put into a code page with the IOL set up correctly.

From my understanding, the script does not run until an individual record is open, so how can my script be executed, which puts the button above my dbid table, when we are not viewing a record? 

Everything is working perfectly until this last step

>From my understanding, the script does not run until an individual record is open, so how can my script be executed, which puts the button above my dbid table, when we are not viewing a record? 

This is not correct. Post your code to work towards a solution.

function main(){

    var dbidTable = "blahblah";
    $("table[qbdbid=" + dbidTable  + "] tr:first").before("<tr><td><a href=# id=QBU_Button class='Vibrant Success'>Calculate Time Between Stops</a></td></tr>");
    $("#QBU_Button").on("click", function(event) {
        getDiff();
        alert("Button was clicked");
    });
}
main(); 

This is a snippet from my script. When running it in the console from the table dbid page, the button is correctly created above the table and executes my getDiff function. I must not understand the real details behind the IOL if my original understanding is not correct, because from my own testing, the code is NEVER ran unless we are viewing, editing, or adding a record.

How can my code, which puts a button above the table, be executed if we are never accessing an individual record?

My IOL is set up for this table, iol variables are there, the form is setup. Everything is in place. What could be the problem?

You are probably not including the iol field on the report. It is normally named [-] and placed as the last column in the report to not call attention to itself. You can debug this and other scenarios by placing console.log() statements in your script,

Are you referring to the Fields under Settings of the table? I have the iol set up there:

[iol] & "myScript.js" & [/iol] 

All appropriate values unchecked. I have the IOL set up for many tables and haven't had this issue until this project, I'm not sure what I could be doing wrong.

Yes that is the iol field typically named [-]. Is [-] included in the report? If so it will display as a skinny column with the heading "-" and nothing displayed in any of the rows.

No, it was not included in the report. That was definitely the problem. My teammate and I got it working. Thanks Dan!