Adding a field/property not belonging to the native Form Collection

In CSI9 (9.01.01 on-premise), I'd like to know all the possible options for adding a field on a Form, when this field's data is not contained in the Form's IDO Collection(s).

I know one method so far, but it's quite troublesome : Creating an "Extend and Replace" IDO in which a new property is added, containing the desired data.

I think this is the "normal" method, but I'd really like to have more options because it's really more complex than it needs to be, and also quite problematic every time there is a patch to apply.

Is there another way? Via UET, SP, CLM, FormScript, EventHandler, Validator, anything else? With pros/cons if possible.

Here's an example: on Vendor Contracts form, we need to see the Item's Overview, because the Description is truncated at 40 characters...

So my question is more about fetching data that lives in another table or IDO, but I'd still be interested to know about data that does not exist yet (so first requiring a UET).

Find more posts tagged with

Syteline Development

Comments

Legacy Contributor

Well, technically it is not being truncated, an Item Description "is" 40 characters.

But, yes, we have a slew of UET fields, especially on the Items table, but on a few others as well.

We also have a few E&R where it makes sense to do those. For example, on the Job Materials Form, users had a business case to see the job_sched_StartDate value. Since the Property already exists, it is text book case to use the E&R to add it.

Using a FormScript or Events, you could do vb.Net stuff that maybe does SP stuff, and then do stuff using that output, with Form variables and such.

Validators, eh, probably not.

Legacy Contributor

"So my question is more about fetching data that lives in another table or IDO"

If you want to access data that is in another table you can add it as a table on the IDO. Similarly, if you want to access data that is in another IDO you can add that IDO as a subcollection to your IDO. However, both of these require that you create your own IDO by extending and replacing the original SL IDO as you cannot modified base SyteLine IDOs. You can technically get around this but it would be more complicated than doing the "normal" process so I wouldn't try and do that. If you do not have a way to link a table or an IDO to the IDO on your form you can always use a derived property. A derived property can be populated by a DB function.

"I'd still be interested to know about data that does not exist yet"

I'm going to assume you have never made a UET before. The steps are as follows:

1. Create field (ItemOverview) 2. Create class (i.e CoClass, ItemClass, etc). 3. Create table/class relationship (ItemClass/item_mst). 4. Create class/field relationship. (ItemOverview/ItemClass) 5. Create a property on the IDO.

You only need to extend and replace and IDO once. After that you can add to it as much as you want. The only thing you have to be careful of is making sure you change the IDO on your form to be your IDO.

For your Vendor example I would create the ItemOverview UET on the item_mst table and then extend and replace the SLItems overview and add the field as a property on your new IDO finally add that to your items form. Then I would extend and replace the SLVendors IDO, and add the item_mst as a table on the IDO. Then create a property on your new Vendor IDO that references the ItemOverview field on the item_mst table.

That's the best practice and probably how you should do it.

Copyright © 2025 Infor. All rights reserved.