Sage 100

 View Only

  • 1.  Importing PM Work Tickets fails after first record, v2023

    Posted 09-08-2025 12:29
      |   view attached

    Hello. I'm a bit desperate for help. I've been struggling with a V/I import job for PM work tickets for about a month. Scott Brady originally helped me get through some challenges when I first created the job. He even took my import job and worked with it on his own system and got it dialed in. I guess what neither of us realized was that it would not import more than the first work ticket in the source file. For two weeks now, I've been told by various Sage support people that Brian Reddeman is the person who can help. They try to get his attention while I'm on the phone but I'm usually told that he will get back to me. On Friday, the tech said she had just messaged with him and he told her to transfer my call to him. Then I got his voicemail. I've left vm's and sent emails to him. I'm getting nowhere fast. 

    So now I'm hoping that someone in this community has the magic key. Here's the deal. Every ticket beyond the first one complains about needing a work ticket step record. That number is in the source file on every record. I'm mystified as to why it has no problem with that field on the first record, but does have a problem with it on every subsequent record. I've attached a Word doc with screenshots. I would be ever so grateful for HELP!

    Karen O'Lane



    ------------------------------
    Karen O'Lane
    Accounting Systems, Inc. (ASI)
    kolane@asifocus.com
    559-448-0900
    559-577-4142
    http://www.asifocus.com
    ------------------------------

    Attachment(s)

    docx
    Case 8010569761 PM VI Job.docx   479 KB 1 version


  • 2.  RE: Importing PM Work Tickets fails after first record, v2023

    Posted 09-08-2025 12:49

    I can't see the linekey/stepnumber values in your source file.  Do they include a Step 000000 for each WT?

    • Each work ticket requires Step 000000.  The fields in this step are for the work ticket header.
    • I'm looking at PM_WorkTicketStep in DFDM and it looks like the first linekey value for each WT is 000001.  If your source file pulls the WT step from position 11 (assuming Step 000000 is the first step for each WT), then having the linekey start at 000001 for each WT might do the trick.  Does it allow you to choose Next for that value?  (probably not)  If you set it to Increment, does it go back to 000001 for each WT?  If it does, you may need to add linekey as a column in your source file.

    Also (unrelated), there might be issues with the quote symbols in the WT descriptions.  It looks like they are doubled.  This is a common issue.  I've attached a couple documents with instructions to overcome this.



    ------------------------------
    Susan Pawlowic
    Sage 100 Solutions Architect
    RKL eSolutions, LLC
    spawlowic@rklesolutions.com
    (717) 735-9109 Ext. 4352
    ------------------------------



  • 3.  RE: Importing PM Work Tickets fails after first record, v2023

    Posted 09-08-2025 13:07

    In addition to what Susan mentioned, you might start out by simply Assigning 000001 to the Step# and see if that works.  



    ------------------------------
    Doug Higgs
    Midwest Commerce Solutions, Inc
    (312) 315-0960
    Chauffeur, Chef, and Personal Assistant to Sprinkles
    ------------------------------

    Original Message


  • 4.  RE: Importing PM Work Tickets fails after first record, v2023

    Posted 09-08-2025 23:54
    @Doug Higgs - Interestingly, when I assign a value to WT.StepNo, I get Error 45 Pgm VI_IMPORT_UI.PVC LIne 1849. Brian Reddeman helped me with this a month ago. He was completely baffled; worked on it for 3 hours and then said he would get back to me. When I added a value to the source file and used a Replace operation, it no longer errored. When I reported this, his response was, literally, "Huh? WTH?" And he dropped it, I guess. We don't want to have a value in the source file for it, but we can't all get everything that we want.
     
    @Susan Pawlowic - I manually removed all double quotes from the source file to eliminate the possibility that those were throwing a monkey wrench. It didn't make a difference. Thanks for the info about that, though.
     
    First, the only way to get all the records to import is if there is a new value for WT.StepNo when there is a new work ticket. 
     
    WT 258024 - StepNo 000001
    WT 258025 - StepNo 000002
    WT 258026 - StepNo 000003
     
    Why can't each work ticket have step # 000001? It does when we manually enter work tickets. When importing, each new work ticket must have a step number that is unique from all the other ticket numbers? DUMB.
     
    Second, I decided to go basic and put a column in the source file for L.StepLineKey. This customer will only have one step on every work ticket so I made the value "000001". After MUCH testing and trying to solve for the messages in the job log, I have determined that the WT.StepNo and the L.StepLineKey are inextricably linked. Whatever the value is for WT.StepNo, the value for L.StepLineKey must be the same. I do not understand this. 
     
    I also tried an Increment operation for L.StepLineKey. Every record imports, but each L.StepLineKey field says "To allow import, StepNo <000010> (from the increment value) was not found and replaced with the StepNo <000003> (the WT.StepNo value from the source file)." Again, it's forcing the value for L.StepLineKey to be the SAME as WT.StepNo. DUMB.
     
    Maybe Brian R. isn't calling me back because none of this works logically.
     
    I appreciate your suggestions. I certainly don't expect you to troubleshoot this for me. If anyone has an import job that works, I'll trade you a case of beer. Or a pound of coffee. 



    ------------------------------
    Karen O'Lane
    Accounting Systems, Inc. (ASI)
    kolane@asifocus.com
    559-448-0900
    559-577-4142
    http://www.asifocus.com
    ------------------------------

    Original Message


  • 5.  RE: Importing PM Work Tickets fails after first record, v2023

    Posted 09-09-2025 13:16

    What if you didn't import StepLineKey at all, and allowed Sage 100 to assign it?

    Regarding the step numbers - that's crazy stuff.  I have to believe, for my own sanity, that this is a glitch or there's a workaround.

    For the quotes - there's more than just removing the double quotes.  I do a search and replace in the source file (limited to the Description field) to replace the quotes with a symbol (one that is not already used in any of the descriptions, such as $ or & or another symbol on the ASCII file I sent), add a Temp field to your import and do a Replace on the Description column, and then for the Description field do a Calculation and enter the formula on the Word doc I sent (adjusting it to reflect the value on the ASCII sheet that corresponds with the symbol you used).  It sounds tricky but if you do it a couple times it becomes second nature.  I use this any time there are quotes i a text field.



    ------------------------------
    Susan Pawlowic
    Sage 100 Solutions Architect
    RKL eSolutions, LLC
    spawlowic@rklesolutions.com
    (717) 735-9109 Ext. 4352
    ------------------------------

    Original Message


Related Content