I get a problem that I see no progress in. Anyone that can give some input?
I have an interface that gets sls orders from the outside.
It is constructed as
tdsls400-header:
- dal.new.object("tdsls400")
- a couple of dal.set.fields
- dal.save.object("tdsls400")
Then we take in the lines
- dal.new.object("tdsls401")
- a couple of dal.set.fields
- dal.save.object("tdsls401")

Ths tdsls400-creation works fine.
When saving the lines (tdsls401) I expect the DAL to do necessary update, e.g. update tdsls401.stbp with the value of tdsls400.stbp. This doesn't happen. It does some default updates on fields but not all. And it ends with a bad tdsls401 that doesn't pass the validation.

In another company in the same environment and the same pack comb (so it is the same vesion of the DALs and the tools) I have another order inporting interface that is constructed the same way. This one works fine.

I am very confused. Anyone that hear a ringing bell?

Both driving sessions are normal print/update sessions. And I can not imangine that there is aome authorization problem. I can create the orders and lines manually via the normal user interface without any problems or warnings.

Typing error it was! The DAL2 is great but the capability to give error messages at compile and executing could be improved.

Yes, the main problem of using DAL2 is that the dal.* instructions aren't controlled in compilation time but only at runtime. The object and fields are strings, not variables, so the compiler cannot check them.