Just a simple xbasic command to disable a button

[MRall]

Thanks for any help you can provide

I have a dialog that allows the user to create a transaction with many parts. Submit saves the transaction and associated parts (for a audit trail) I have a process records button that becomes active once the submit is successful. This acually performs the tranction to the inventory table using an ajax callback xbasic code. Everything works. The issue I have is; How do I disable the process records button and/or reload the page to start over once the the records are processed. I don't want the user to be able to keep clicking on the process records button.

[christappan]

Re: Just a simple xbasic command to disable a button

How does the process records button "[become] active once the submit is successful"?

Well, and for that matter, does it need to be done manually, or could you just put the code from the callback in your AfterDialogValidate event?

[MRall]

Re: Just a simple xbasic command to disable a button

When the submit is successful the transaction returns with a auto generated transaction number which is needed to process the correct records. Whithout that number, the parts can't be linked and processed. The process button is enabled when the transaction number >0. Until the submit is performed I won't have a transaction number.

I would love to run the xbasic code when the submit is pressed, but I don't know how to make this happen.

[MRall]

Re: Just a simple xbasic command to disable a button

I can explain what the process record button does.

With the transaction number, the xbasic code finds all of the parts for that transaction and adds or subtracts them from inventory one at a time. It can be more complicated than that depending on what kind of transcation it is (physical count, Issue, return, Receive) and what setting are enabled.

[GGandhi]

Re: Just a simple xbasic command to disable a button

hello

is this something like a purchase order?
there is po_header information and po_detail information.
you fill in the dialog for both parts then when you submit the po_header information is saved to that table and the po_details information is saved to that table, while doing it it adjusts the inventory data.
(po_header and po_detail names are used as an example. basically a header table and detail table is the idea)
is this the idea?

[MRall]

Re: Just a simple xbasic command to disable a button

Yes, the header is the transaction details going to one table and the repeating section contains all of the parts going to another table. Unfortunately, processing the records is not always strieght forward. That is why it requires some custom xbasic code.

[GGandhi]

Re: Just a simple xbasic command to disable a button

would be able to list what you have on the header table and detail table, you don't have to list all the fields just a few
and what type of transaction you need to accomplish ( adding subtracting are no different, just + and - in the process)

[christappan]

Re: Just a simple xbasic command to disable a button

Martin,

If you've already created an Ajax Callback that works with the button push, you're 90% of the way there.

In the AfterDialogValidate, I assume you have

ExecuteServerSideAction([saveRecords])

.

After that, add:

if rtc.primaryTableEditMode = "Enter" 'if it's an update to the record, you don't want to recreate the related records
RecordID = rtc.primaryTablePrimaryKey
(see below)
end if

Then just copy and paste your Ajax Callback code into the code above where it says "(see below)" and change any references to the e.dataSubmitted.ID in your Ajax Callback to the variable RecordID.

To see where this info comes from, click back up on your

ExecuteServerSideAction([saveRecords])

and then click Action Scripting > Show variables exposed by this action.

[MRall]

Re: Just a simple xbasic command to disable a button

I'll give that a try. That would get rid of the need for a process records button?

[christappan]

Re: Just a simple xbasic command to disable a button

That's correct.