Sage 100

 View Only
  • 1.  Sage 100 Advanced 2013, p.u. 4Created a UDT of on

    Posted 01-02-2014 13:53
    Sage 100 Advanced 2013, p.u. 4 Created a UDT of one field. Imported the list of data. Created a UDF in SO Detail same name and size as the UDT's field. Can only select to validate to the UDT if UDF is a multi-line. I want the UDF to validate and be a lookup list off the UDT - what did I miss? tia.


  • 2.  RE: Sage 100 Advanced 2013, p.u. 4Created a UDT of on

    Posted 01-02-2014 13:58
    Isn't that a multi line then??? As I recall, the UDF is a multi line in the ones I have set up...


  • 3.  RE: Sage 100 Advanced 2013, p.u. 4Created a UDT of on

    Posted 01-02-2014 14:11
    Okay but when I drop it into the secondary grid, it's showing as a flat field, no lookup.


  • 4.  RE: Sage 100 Advanced 2013, p.u. 4Created a UDT of on

    Posted 01-02-2014 14:13
    Oh, the secondary grid. I only have installed on header tables.


  • 5.  RE: Sage 100 Advanced 2013, p.u. 4Created a UDT of on

    Posted 01-02-2014 14:31
    Yay, I've had no problems when it's a header UDF based on UDT. Need the same but in the details/grid, I thought for sure I'd done this before, but can't remember how


  • 6.  RE: Sage 100 Advanced 2013, p.u. 4Created a UDT of on

    Posted 01-02-2014 14:42
    Hey Moira, you say your UDT has one field, but really it has to have two, right? One will be the index of the UDT and another would be the data. I just created a UDT in SO, then added a UDF in SO_SalesOderDetail and referenced that UDT on the Validation Tab. Then when I go into Sales Order Lines I do see the ALE Lookup after adding it to the secondary grid. Yours should work like that.


  • 7.  RE: Sage 100 Advanced 2013, p.u. 4Created a UDT of on

    Posted 01-02-2014 15:14
    That was it @CullenLowe - a single field no lookup, added a second one and it works! Thanks!


  • 8.  RE: Sage 100 Advanced 2013, p.u. 4Created a UDT of on

    Posted 01-02-2014 17:45
    Along the same lines...UDF's in the detail row do not follow field format masking rules. Header fields follow masking rules. I think it is a bug.