Skip to Content

Dynamic access to user defined fields (KUT fields)

We are building a solution that will be distributed to multiple company's. It uses some customer attributes which are not standard fields, so they are implemented as user defined fields (KUT fields).

When deploying the solution to a system, it could be the case that some of the customer attributes are already implemented as user defined fields. Than we would like to use the existing user defined fields, instead of introducing new user defined fields for the same customer attributes.

We would like to setup our absl code in a flexible way so it can handle any given field name for a specific customer attribute. We have created a customizing table which holds the field names used for a set of customer attributes. In our absl code we read the customizing table, so at runtime we know the correct field names to be used.

How can we fill a user defined field with a value when we only know the correct field name at runtime? We need some kind of dynamic acces to user defined fields.

Any suggestions?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Feb 06, 2018 at 02:51 PM

    I don't think that's possible in the applications studio. A solution can't even be deployed to a system if the front-end field references don't match what's in the system, so it seems like functionality that'll never be used to me.

    Add comment
    10|10000 characters needed characters exceeded

    • That's what I mean --- I've yet to see any evidence that this is possible. I've had a few different solution uploads fail on account of field name mismatches, so it seems reasonable to assume this is something that needs to be sorted out prior to deployment.