Sage 100

 View Only
  • 1.  OK, I've had enough of screen BS for this week. C

    Posted 06-14-2018 07:44
    OK, I've had enough of screen BS for this week. Can anyone tell me how to more efficiently fix screen errors such as error 65 or 12 about (for example) the WHS button on the Transaction tab in Inventory, or the case of a field disappearing from a grid and Reset Panel is not available, etc? How does one go about deleting the records that pertain to a workstation's screen customizations? I've gone through SY_GridDefinition and SY_Personalize (which is a horror story since nothing appears to ever get deleted from that) and I've got 2 situations right now where I just don't seem to be able to find the records. Creating a new Custom Office screen for them doesn't work, either.


  • 2.  RE: OK, I've had enough of screen BS for this week. C

    Posted 06-14-2018 07:45
    Classic or Standard view?


  • 3.  RE: OK, I've had enough of screen BS for this week. C

    Posted 06-14-2018 07:53
    Classic - I'm pretty sure all of the issues I've had in the last week have been Classic.


  • 4.  RE: OK, I've had enough of screen BS for this week. C

    Posted 06-14-2018 07:59
    Enhancements?


  • 5.  RE: OK, I've had enough of screen BS for this week. C

    Posted 06-14-2018 08:12
    Version?


  • 6.  RE: OK, I've had enough of screen BS for this week. C

    Posted 06-14-2018 08:20
    Some have enhancements, others do not. I'm looking for general guidelines when this happens because all I get from Sage's KB is to restore the SY_Personalize.M4T file.


  • 7.  RE: OK, I've had enough of screen BS for this week. C

    Posted 06-14-2018 08:28
    I am looking forward to hearing from others. I had a similar issue with a field that disappeared for a user. All attempts to reset the form failed. Worked on creating and deleting customizations and eventually - it came back! Not sure what I did.


  • 8.  RE: OK, I've had enough of screen BS for this week. C

    Posted 06-14-2018 12:32
    To remove a customization: Have you looked in the Custom folder under the module folder, i.e. ...MAS90/AR/Custom/[username]-xxx (""xxx"" = Company Code)? Have had instances where the screen customization had to be copied to a user, only so that it could be deleted, in attempt to reset the ALL group that they should have been apart of. Also, have seen fields that had 0 height for a user, thus the field was not visible only for them (and the Reset Panel didn't resolve).


  • 9.  RE: OK, I've had enough of screen BS for this week. C

    Posted 06-14-2018 12:43
    After copy or delete, run the Rebuild Customizer Log on Custom Office Utilities menu.


  • 10.  RE: OK, I've had enough of screen BS for this week. C

    Posted 06-14-2018 12:45
    Again, this is normally on a screen that does NOT have a Custom Office mod, but I've tried to create a mod in order to make the issue go away.


  • 11.  RE: OK, I've had enough of screen BS for this week. C

    Posted 06-14-2018 13:12
      |   view attached
    The steps that I would go through in similar situation: ensure there are no records in custom office for that screen (since there shouldn't be any), ensure there are no files like ...MAS90/MM/Custom/[username]-xxx/[screenname] (since there shouldn't be any), (after backup) delete all records in the SY_Personalize.m4t table related to that screen except the DMAIN record --> the hightlighted record should be removed in attached screenshot, leaving only the DMAIN next in the list.


  • 12.  RE: OK, I've had enough of screen BS for this week. C

    Posted 06-15-2018 07:46
    That's pretty much what I do, but it hasn't always been working for me lately. Had a client yesterday with an issue with the Positive Pay screen, for Pete's sake, and they even had a super-small SY_Personalize file (relatively - still 8K records - WHY ON WHY DOESN'T SAGE DELETE OLD VERSION RECORDS?). Deleted anything I found (which was virtually nothing). Only option was to restore. IT restored, client reported still having the issue. Then the next morning, all was well. THAT is incredibly frustrating.