UET not behaving as expected (to me at least)

*Note: Not sure why images seem blurred.

I added some UETs onto a form today. That was simple enough other than in the cloud using the Web Designer, you can't drag and drop yet.

Once I bound the properties to the fields and tested, the inheritance wasn't there.

I checked the table and it looks fine. I see the 3 UETs I created.

The properties for the 1st UET look fine.

Since these are decimal fields, I expected a mask based on precision and scale. Is that thought incorrect? If I add data, no trailing zeros are added either.

Checking the binding on the 1st control looks fine.

Next, I checked Inheritance.

View Attributes opens a blank IDO Properties form. Edit Properties says the extension doesn't exist, do I want to add.

I must be missing something in the linkage during this process.

Anyone care to take a stab at this?

Thanks,

Lance

Find more posts tagged with

Syteline Development

Accepted answers

acl

try to create IDO Property Class LJ_MaterialGrain that uses LJ_MaterialGrainType and set all PC attributes as needed; components can inherit from PC-PCE-CC; Property Class-Property Class Extension-Component Class...Amount PC is a special case , but you can see the Amount PCE is using a specific Mask in Formatting...

All comments

acl

UETs are dynamically created IDO properties...if you define the SQL column as standard UDF type (ex. uf_amt as AmountType) the framework will use the IDO Property Class Amount to default component's attributes; you probably miss the IDO Property Class for the custom SQL UDF type

Legacy Contributor

In SQL Data Types I have this

In UET User Fields I have

Am I following your thought process here?

Regards,

Lance

acl

try to create the IDO property class to associate SQL data type with Mongoose IDO - see Amount-AmounType example

Legacy Contributor

Thanks again acl.

I created a TESTONLY UET field. I assigned it the Mongoose datatype Amount per your example in lieu of my defined type LJ_MaterialGrainType. I added the UET to the form and when I viewed the form the 0.00 appeared in the field as expected, almost. I noticed that Decimals to Display for Amount is set to 3 but on 2 appear on the form. Something else for me to resolve my understanding.

To recap what you explained and I verified (correct me if I am wrong): A UET is dynamically created IDO Property. The UET cannot derive its properties from a User Defined Type (User SQL Data Type). It must derive a property from a Mongoose Property Type. Hence, use Mongoose AmountType, not LJ_MaterialGrainType.

Regards,

Lance

acl

Legacy Contributor

acl, you have been so helpful, and I really appreciate it.

Your last post that mentions the format mask in the PCE is the resolution to my need. I reviewed how this was set for Amount and made a similar mask for LJ_MaterialGrain. What is presented on the form is what I was after.

I also created the PC LJ_MaterialGrain and used LJ_MaterialGrainType as the Column Data Type per your suggestion.

It may be unique to UET fields, but a Type can' be used for the field but not a PC which contains the Type defined. At least, I found no way of doing so.

This may sound odd but since your post containing the comment about the PCE format which solved my problem, will be the answer I select as Correct for this thread. Hopefully, anyone experiencing similar UET issues will onboard all that has been shared here.

Respectfully,

Lance

acl

glad it helps you further...sql type is not enough...the Mongoose framework needs some metadata to link that sql type to the IDO layer, hence IDO PC must be in place...Cheers

Legacy Contributor

Prior to resolving my issue and testing the suggestions in this thread, I added the additional UET TESTONLY Edit control to the form and thereby, it was added to the table. I cannot directly delete this column from the table and would like to get rid of it since it is garbage.

Is there a method or procedure for deleting unneeded UET columns from the underlying table to which it was assigned?

Regards,

Lance

acl

delete record from UET filed class relationship and impact schema to delete

Legacy Contributor

Copyright © 2025 Infor. All rights reserved.