[dmashburn3]

I have created a custom transaction type that resembles a journal and I’m trying to have a user event generate this transaction. However on the “save” piece it return the error:

The transaction could not be saved. The transaction’s status is posting, yet the Custom GL Lines Plug-In implementation associated with this transaction type did not create any GL lines.

This is odd given that Custom GL Lines feature is not even turned on. Anyone else experience anything like this?

Further more, I can generate the custom transaction via:

1. Manual UI entry. Saves without issue.

2. Dev Console – Creates without issue.

3. Suitelet – Creates without issue

4. Scheduled Script – Creates without issue.

It’s when I use a user event beforeSubmit or afterSubmit that it fails. In addition it also fails when I tried to have the userEvent call the aforementioned suitelet to generate it.

Any advice?
This is a cached copy. Click here to see the original post.

[pcutler]

I imagine the error reads that way because the custom transactions feature shares underlying code with the custom GL lines feature.

Anyways, although I’m not familiar with the error, since you said it works in a Suitelet, have you tried calling a suitelet/restlet from your user event script via nlapiRequestURL to create the custom transaction?

[dmashburn3]

So I initially wrote the suitelet with default values, and then deployed, clicked the link on the deployment, and it creates with no issue.

However then I decided to try what you suggested, I passed the parameters from the user event over to the suitelet, read them, attempted to create the custom transaction, and it spit back the same error as above.

This leads me to believe its something specifically tied to the user event and the timing of the execution for some reason.

[pcutler]

Would you business process be adaptable to creating this custom transaction with a scheduled script that runs every 15 minutes instead?

[dmashburn3]

Turns out that my script had a separate problem setting the line item values. Without any values in the line items, that was the error it generated. Odd that it referenced the plug-in implementation and that’s what threw me off, but it works now and generates custom transactions perfectly.

[Author]

Posts