Sage 100

 View Only
  • 1.  Work Ticket Edit parts tab script issue

    Posted 05-19-2023 12:23

    Operations Management 2022.2, customer wants a way to uncheck the chargeable and print flags on all parts on a work ticket at once.  I have created a button script to loop through the lines and make the change.
    I can get the value of the JT158_WTChargePart & JT158_WTPrintPart fields, but SetValue on them returns "the column is not on the IO list".

    Any ideas?

    #script



    ------------------------------
    Phil McIntosh
    President
    Friendly Systems, Inc.
    ------------------------------


  • 2.  RE: Work Ticket Edit parts tab script issue

    Posted 05-21-2023 09:31
    Hi Phil,
    To resolve this issue create a custom office UDF's field on both those tables and update. Once you do that it will fix the Data Dictionary issue and should take care of that error message. Have a great day.

    Carmen Cruz
    Sage Consultant
    carmen.cruz@compudata.com
    215-969-1000 Ext. 279
    www.compudata.com
    Work Smarter... Together 

    CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106





  • 3.  RE: Work Ticket Edit parts tab script issue

    Posted 05-22-2023 08:41

    @Carmen Cruz ,
    By "both tables" did you mean JT_WorkTicket and SO_SalesOrderDetail?
    If so, it didn't fix the issue...



    ------------------------------
    Phil McIntosh
    President
    Friendly Systems, Inc.
    ------------------------------



  • 4.  RE: Work Ticket Edit parts tab script issue

    Posted 05-23-2023 10:31
    I Phil,
    Yes, I was talking about the table from this field that you're trying to update. If you did try to add a UDF an update of the data dictionary and that didn't work I'm sorry but I know a lot of times when I get that weird error that's what works for me. Maybe the error Sage is throwing is not the real error at all but the only way Sage knew how to respond.  Sorry bout that :(

    Carmen Cruz
    Sage Consultant
    carmen.cruz@compudata.com
    215-969-1000 Ext. 279
    www.compudata.com
    Work Smarter... Together 

    CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106





  • 5.  RE: Work Ticket Edit parts tab script issue

    Posted 05-23-2023 12:53

    JobOps has always broken things differently...
    Shall I  try the data dictionary hack?



    ------------------------------
    Phil McIntosh
    President
    Friendly Systems, Inc.
    ------------------------------



  • 6.  RE: Work Ticket Edit parts tab script issue

    Posted 05-25-2023 10:08
    Good morning, Phil,

    While going through this issue again, I noticed that these fields that you were mentioning start with JT but in a prior email you mentioned the table that you're talking to is SO_salesorderdetail.   SO table would not have fields that start with JT. Am I missing something?

    Carmen Cruz
    Sage Consultant
    carmen.cruz@compudata.com
    215-969-1000 Ext. 279
    www.compudata.com
    Work Smarter... Together 

    CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106





  • 7.  RE: Work Ticket Edit parts tab script issue

    Posted 05-25-2023 16:36

    JobOps / Operations Management fields DO hit the SO_detail table. 



    ------------------------------
    Mary Jo Krueger
    Senior Software Consultant
    CLA (CliftonLarsonAllen LLP)
    ------------------------------



  • 8.  RE: Work Ticket Edit parts tab script issue

    Posted 05-25-2023 23:42

    I did manage to get past the first problem, but there is still a discrepancy between the behavior in the UI and when a script changes the print and charge fields:  if a script makes a change, you have to manually change the price field.  If you check or uncheck the box in the UI, the price gets removed or calculated.



    ------------------------------
    Phil McIntosh
    President
    Friendly Systems, Inc.
    ------------------------------