Problem: Planning Worksheet -> Carry Out for Purchase Ite

sonvdb
sonvdb Member Posts: 33
edited 2007-01-23 in NAV/Navision Classic Client
I got the message below when perform Carry Out Action Message for Purchase Item in Planning Worksheet, the message show:

"The following C/AL functions can be used only to a limited degree during write transactions (because one or more table will be locked).

Form.RunModal is not allow in write transactions.

CodeUnit.Run() is allow in write transactions only if the return value is not used. For example, 'OK:=CodeUnit.Run()' is not allow.

Report.RunModal is allow in write transactions only if ' RequestForm = FALSE'. For example, 'Report.RunModal(...,FALSE)' is allowed.

DataPort.RunModal is allow in write transactions only if ' RequestForm = FALSE'. For example, 'DataPort.RunModal(...,FALSE)' is allowed.

Use the commit function to save the changes before this call, or structured the code differently
"

There is no such problem for Production Items. I am a consultant not developer, it's seem to problem with coding. Could you give a advise? Thank alot!

Comments

  • ara3n
    ara3n Member Posts: 9,258
    Hello Sonvdb
    On the option tab there is a checkbox. Stop and Show First Error. Check that option.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • sonvdb
    sonvdb Member Posts: 33
    Hello ara3n, thank you very much. It's work now. But I am confusing about this option, I talk that if we check it then it will stop and show the error (like the message I wrote).
  • kine
    kine Member Posts: 12,562
    There is some part of the process (may be customization or :bug: ) which want to run modal report, form etc. but the write transaction is running. You can use the debugger to see, where it will be called. But this can be deep in the code (for example, the process is validating some field, this validation trigger printing of some document etc.)
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • ara3n
    ara3n Member Posts: 9,258
    That is a standard Navision :bug: . I have seen it three times now. SP2 i believe where it started happening.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • sonvdb
    sonvdb Member Posts: 33
    I have just tested with SP1 & SP2 the same problem occured.
  • ara3n
    ara3n Member Posts: 9,258
    Thanks Sonvdb. Have you tried it in sp3?
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • sonvdb
    sonvdb Member Posts: 33
    Sorry, I don't have SP3 here. Can someone else try it in SP3?

Categories