Wrong Property Lengths from Syteline IDOPropInfo

capashere

I want to make sure I'm not missing something dumb here.

I've got a app started that's creating SQL tables based on the property information coming back from the IDOPropInfo endpoint under the IDORequestService. Creating the tables isn't an issue, it's that the data that comes back from LoadCollection overruns on properties that we haven't customized.

For instance on SLJobs there is a derived property called DerJob with a length set at 10. When I query the SLJobs loadcollection and look at some of the values returning for DerJob they all have a length of 16 characters.

Has anyone run into or worked around this?

EDIT BELOW

I've been digging around and found this https://docs.infor.com/csi/latest/en-us/csbiolh/default.html?helpcontent=mgsdug_cl_sl/mergedprojects/core/fields/d/data_type_ido_properties_.html

That DerJob field is a NumSortedString type and according to this it's a maximum length of 4000 characters. Why would the property show 10? ugh.

Carsten Steinhoefel

The IDOPropInfo returns the Data Type and Length fields from the IDO Definition. For bound properties this corresponds to the length of the database table column it is bound to. Strings (any type of) can have a maximum length of 4000 characters but are usually shorter.

DerJob is a derived property. For derived (and unbound) properties, the IDO Data Type and Length are defined on the IDO with no direct connection to a database column. Of course, the definition should be correct for what is expected.

In this case, DerJob has the same length as Job (10) which is incorrect as it actually returns Job + Suffix.