nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Sale order and lines creation using DAL

Sameer

I have created a custom session with mandatory fields for Sales Order creation. Using DAL, I am able to successfully generate the Sales Order header details. However, I am facing an issue while trying to add lines to the Sales Order.

Find more posts tagged with

Accepted answers

All comments

Stephan Woessmann

Hi Sameer,

Could you please provide more details on the issue that you are facing when trying to add sales order lines?

Are you getting an error message? If possible, please provide your code logic.

Yours,
Stephan

Sameer

Hi Stephan,

I am encountering the error “The Item field has an invalid value in Sales Order Lines” while inserting a sales order line into the tdsls401 table using DAL.

I also attempted using the standard function
tdsls.dll4041.generate.sales.orderline, but the same error persists.

However, when I create the sales order line manually through the session, the line is created successfully without any errors.

This issue appears to be specific to insertion via DAL/function, while standard session processing works as expected.

Fabiano Silva

When you set the value for the item field, are you considering the values from the first segment? like

Item " 123456"

Item.segment.1 = " " (9 caracters)

Item.segment.2 = "123456"

What LN version do you use?

Stephan Woessmann

Hi Sameer,

While you are currently using LN on-premise and you have the ability to call standard library functions, I am highly recommending that you avoid them, and that you try to utilize public interfaces or develop your own logic. The path of LN is going into the cloud, where the standard libraries cannot be used anymore. Unless you want to refactor all your custom code logic later, now is the time to prepare for the migration.
The mentioned tdsls.dll4041.generate.sales.orderline() function is specific to items of type List. It won't work for other items.
When you are capturing the error message from the DAL error stack, there might be more than one message. I suggest using a loop to retrieve and check all of them. The message(s) before might give you the key information to the problem.
Are you using the DAL functions correctly? You should have a call to dal.new.object(), multiple calls to dal.set.field(), and finally a call to dal.save.object(). If you are not using the dal.set.field() function to notify the DAL that a field value has been set, the DAL logic can fail.
Finally, I am suspecting that the error is that the item cannot be found in the item sales data, which is likely caused by not sending a correct item code with the project and item segment.

Yours,
Stephan

Sameer

Hi Fabiano,

We use LN 10.7 On-Prem. What you are suggesting is that I should assign the item with segments. However, when I use DAL, it is not accepting the segments properly.

When I assign the field data as:

dal.set.field("tdsls401.item", "1234567891234567891234")

it gives an "Invalid Item" error.

When I set it with segments and enable debug to trace the process, at the line where the segment was being assigned, it threw the following error:

Error: Cut-off in _get_sval() called by bshell function __dal_select_field. The entered string is 23 bytes long, exceeding the limit of 17 bytes.
(dal.set.field() in object ottstpamdll)

The process stopped at that point.

Sameer

Hi Fabiano,

To use dal.set.field("tdsls401.item", " 123456") . my item have project so total length is 21.

Copyright © 2025 Infor. All rights reserved.