Auto-populate custom field based on an another custom field

Hi ​@jdoherty,

It is possible.

Long back I mapped this kind of requirement in apps9.

Regards

Abdul Rehman

Thank you for your reply. I was never able to do this despite many attempts.

Could you post some code or maybe post a link to a working example?

I would appreciate it.

Hi ​@jdoherty,

I created two custom fields viz. Part No and Default Location for Project Definition/Site tab, where user would enter Part No and the system would automatically fetch value for Default Location.

Code for Default location - INVENTORY_PART_DEF_LOC_API.GET_LOCATION_NO(SITE,CF$_PART_NO)

Regards

Abdul Rehman

Abdul wrote:

Hi ​@jdoherty,

I created two custom fields viz. Part No and Default Location for Project Definition/Site tab, where user would enter Part No and the system would automatically fetch value for Default Location.

 

Code for Default location - INVENTORY_PART_DEF_LOC_API.GET_LOCATION_NO(SITE,CF$_PART_NO)

 

Regards

Abdul Rehman

Thanks Abdul but it is Apps10 Enterprise Edition I need it for, not Aurena.

​@jdoherty, custom field creation core process has not changed since apps8 and it is almost same for Aurena and IEE versions.

Please check with same code. Hopefully should work.

It really depends if what you’re talking about a field “auto populating” is a read only field (as is the case in your Customer ID / Name example), or another persistent field.

If it’s a read only field, then you just need to create the field as read only with the proper select statement to retrieve the data based on the other (persistent) custom field value, and you can do that exactly as ​@Abdul suggested.

If it’s another persistent field, you’d kinda need to do that through an event or modification through studio developer, to hijack the creation/update of the first custom field and run code to populate the second field with persistent data.

Based on your defined business requirement of gathering the default location (you’d need to pick whether it’s a picking or other type location) (which is set against the inventory part in INVENTORY_PART_DEF_LOC), which you can get through

INVENTORY_PART_DEF_LOC_API.Get_Location_No(contract_         => ,
                                           part_no_          => ,
                                           location_type_db_ => )

Note that to get the part number, you’d first need to convert the referenced objkey in your first custom field to its actual key reference, either through a join on objkey or by calling a custom procedure you’d have done which does that).

Thank you for the replies. I think the solutions suggested won’t work for what I want to do because I want the Location Custom field (below) populated automatically by what is in the Part No. field (also a custom field)

The two fields are on a custom page (see below)

A new record is added by clicking on the “plus” sign(no.1).

A part is entered into the ”Part No” field (no. 2)

Then the location custom field is clicked into. That is an LOV that displays all locations. 

I want to pass in the value that is in “Part No.” to the Location custom field (along with the logged in person’s default site) and populate an LOV with the default location for that part. The user will then select that location from the LOV and it will be entered into the Location field. It would actually be better if the LOV gave a list of all locations for that part and site, not just the default site . 

However the part no. has not been saved to the database, it is only displayed on the Part No. field so I can only refer to it by Text field name when I use the custom event in the Location custom field.

When save is clicked I can then reference the Part no. but I want the location populated before the record is saved.

I don’t think I can do that with a custom field. In the Customer page when a new record is added, the Customer Name is populated automatically by what appears in the Customer No. field.

What I want to do is similar to that.

There are other fields in the custom page that I have painted over, they are not relevant.

Right so you want to keep that field as a PERSISTENT, changeable field, i.e. You want it to DEFAULT to the default location, but you ALSO want the user to be able to CHANGE IT if you want to ? (i.e. the field must remain persistent?)

I don’t believe that’s possible using purely the configuration layer, especially doing a client side update without committing a transaction. Probably possible through a client mod but that requires Studio Developer and is much more involved than just using the configuration layer to create a custom logical unit which is what you’ve done.

Yes when the location field is entered into by the user I want it to trigger an LOV on the left menu that lists all the locations for the part that is in “Part No” (for the default site of the person logged in to IFS).

Or if that is not possible then the LOV can just display the single default location for the the part that is in “Part No” (for the default site of the person logged in to IFS). 

But the key thing is this must be possible before the record is saved. I don’t want to have to enter the part no, then save the record and then enter the Location No. field and select from the LOV that is linked to it.

If what you wanted is just  to display the default location, in a manner that it can’t be changed (read only), in a way that the user doesnt even have to put it in, that’s easy enough to do.

Basically you make the location no custom field read only instead of persistent and you make it read from the part_no field on the same LU, using get default site of the connected user as the parameter.

It won’t show up before saving, but it’ll show up as soon as you save the record (and won’t be able to be changed if it’s set to read only, obviously)

Thanks for the reply. That isn’t the way the requirements I was given want it to work unfortunately.

It has to appear before saving. Similar to the Customer page when a new customer record is added, the Customer Name is populated automatically by what appears in the Customer No. field. That does it before the new customer record is saved. It seems a bit strange it isn’t possible to do it in Custom Logical Unit. 

It actually makes sense that it can’t be done in custom logical units because field population like this is done client side, and custom logical units only affect the backend logic :)

Changes to the client like that are always done with Studio Developer, can’t do it purely through the configuration layer.

Also to be fair, I’m not exactly sure what the problem would be with it not showing before saving if it can’t be changed (or doesnt need to be manually populated) anyways, so that business requirement only makes sense if it has to be an updatable field

In the page you’re talking about (Customer Tab within Project), the customer name is not an actual field but simply a read only attribute. The fact it populates automatically while the record is dirty (i.e. not committed yet) is because the page was specifically designed by IFS to do that, by running a DbImmediate Client call when the customer is selected in the Lov.

This isn’t something you can do in the configuration layer, unfortunately.

The user just wants to be able to visibly see it before it is saved, so they can be sure it is the correct location. 

A possible solution is to take it out of IFS completely and use Novacura flow instead. I may do that.

If the value can’t be changed at all if the field is set to read only, there’s not much point in seeing it before end.

You could even make a custom event that ends up preventing the save if the output result of the custom field would be null (if the part doesnt have its default location set for example) to warn the user that the part doesnt have a default location set :)

If the point is to have them check if it’s the CORRECT location, as in the people who manage part data may have made a mistake in the default location, and the user needs to control that they didn’t do a mistake, then yeah you can’t do that through configuration layer.

That is what I want to do; but as you say it isn’t possible in a logical unit. I could populate the location field at the time the record is saved but the user requirements state that the location must be an LOV that is visible to the user (before saving).