Sage 100

 View Only
  • 1.  Advanced v5.20.3 From what I can tell in customiz

    Posted 11-27-2017 09:03
    Advanced v5.20.3 From what I can tell in customizer, 'OItem' and 'DMain' are accessing the same ""file."" OItem is the on-the-fly item maintenance screen accessed from Sales Order or the like, and DMain is the primary Item Maint screen. My client has requested adding a drop-down to the UI screen. I can have it on one or the other, but not both. If I try to add the same field to OItem, it tells me it has to be removed from DMain. So what do I need to do to get it on both screens? (and, no, adding it to PMain is not an option for them unfortunately). Anyone have a workaround? TIA


  • 2.  RE: Advanced v5.20.3 From what I can tell in customiz

    Posted 11-27-2017 09:24
    This issue was corrected in product update 4, so you can put on the latest product update.


  • 3.  RE: Advanced v5.20.3 From what I can tell in customiz

    Posted 11-27-2017 09:25
    Excellent! Thanks @MicheleHerzog


  • 4.  RE: Advanced v5.20.3 From what I can tell in customiz

    Posted 11-28-2017 19:46
    @MicheleHerzog applied PU 5 and it didn't fix it. I can't find documentation on the fix anywhere. I tried removing and re-adding the UDF, and rebuilding the panels but no luck. Am I missing something?


  • 5.  RE: Advanced v5.20.3 From what I can tell in customiz

    Posted 11-28-2017 19:57
      |   view attached
    Under Customizer in the attached document it is #1. This update fixed the issue for one of my clients. Are you adding the UDF from the Customizer Module or the Sales Order or Inventory module by hitting F9? I have a client that I have to add all UDF's to the screens directly from the Customizer module and not the specific module it will display in.

    Attachment(s)



  • 6.  RE: Advanced v5.20.3 From what I can tell in customiz

    Posted 11-29-2017 12:34
    Looks like this is for the error between a standard panel and a wide panel. My issue is with the oItem 'on-the-fly' panel, and the DMain panel; so this didn't correct it, darn! Still searching for suggestions if anyone has anything to try!