The scripts provide by Steve Malmgren are GREAT as are the accompanying scripts in the Custom Office export provided in the Partner File center.

Unfortunately, these sample enhancements point out a significant missing feature of Custom Office. It is that UDF fields on screen panels can only be validated against a UDT and not by standard MAS tables.

Steve goes through significant effort with advanced scripting techniques to build and maintain Shadow copies of the customer master file and inventory item master file for this purpose. Unfortuneately, these Shadow tables can still become out of synchronization with their standard counterpart even though there are advanced scripts to duplicate changes with each new and deleted field. For example, advanced scripts are not invoked when a table/field is changed during a update such as period end or invoice postings. A "Refresh Shadow" button that must be manually invoked is provided to correct this short coming.

A feature to allow a UDF to be validated from a standard MAS table would solve this issue which has been so creatively "worked around" in Steve's examples - almost!

Comments

  • Yes!!! This seems like a no-brainer!!! And having to set up "shadow tables" as an almost-work-around is just so 1990s!

  • Agreed - It's like exporting your GL to Excel to prepare Financials. Get with it!!!

  • This is crazy. There is no good reason not to support native tables

  • this should be available as part of scripting.

  • The more I use scripting, the more I realize that this is a huge hole. Reminds me of the BP gusher in the Gulf of Mexico. This needs to be plugged also......

  • Please please add it, it does not make any sense from data structure not to be able to validate against MAS tables.

  • What is the status of this enhancement? It has been out for almost a year. Is it making the v5.0 release? It would be GREAT to see some feedback on the request!!!!!

  • I remember the first time I created a UDF and needed to validate it against a table in MAS. I was surprised it wasn't an option, and thought I must be missing something. This should not be too hard to do with a simple programming script, especially if the user identifies the table and the field to validate against.

  • Sage 100 is currently in version 5.+ and this matter is still a problem. When will the Gods on Mt. Sage listen?