Skip to main content

Hello,

On our Sales Part, we add a secondary reference which is our client product number (the sales number is our internal reference)


When an user add a Sales Part to a customer agreement, he select a sales part then do is configuration and validate it.
Once it’s created, the secondary reference custom attribute which is a read only is filled.
What I want, for clarity for user, is when they choose a sales part, the custom attribute is refreshed to display the value.
You can see example on screenshots of what I except : 
 


For now, the user can see this custom attribute only after validation and page refreshed (triggered by validation).

Is there a way to achieve this ?

Thank you

Hi ​@REOGIRARD,

It is not possible, as far as I know, since the system executes the custom attribute logic once the record gets saved. 

Alternatively, in addition to the existing layout, add the secondary reference in the Sales Part No LoV also. Please refer to the screenshot below. 

 

 

This way, business users can refer to the Secondary Reference with the Sales Part.

Hope this helps.

 

Regards

Abdul Rehman


This is true. Custom read-only custom attributes (select) are only populated when the record is fetched from the server. Depending on from where you select the data to be shown with this custom attribute, ‘Computed Field’ might be a solution for you. This is something that was added support for in 25R1.

https://docs.ifs.com/techdocs/25r1/040_tailoring/225_configuration/200_client_configurations/305_computed_fields/


@REOGIRARD Abdul’s idea is very good for your case.

My point is something else. There is standard functionality in IFS for what you wanna achieve - you can create a Sales Part Cross Reference - giving your customer part no and part description. Setting this up is valuable since the Order Confirmation / Customer Invoice layouts will use your customer part no and description to make it easier for them to recognize what they bought.


@REOGIRARD Abdul’s idea is very good for your case.

My point is something else. There is standard functionality in IFS for what you wanna achieve - you can create a Sales Part Cross Reference - giving your customer part no and part description. Setting this up is valuable since the Order Confirmation / Customer Invoice layouts will use your customer part no and description to make it easier for them to recognize what they bought.

This is especially true given that unless I’m mistaken, using a custom field on the sales part would mean you can’t differentiate the secondary reference PER customer, it’d be a site specific reference.

 

All well and good if you only sell that part to 1 customer I suppose, but if you’re selling a part to multiple different customers, they might each have their own distinct product reference for it, which is what Sales Part Cross Reference is great for :)


Thank you guys for your answers !
We already use the Sales Part Cross Reference but when we implemented IFS V8 years ago, it has been chosen to introduce this secondary reference (customer product number) by a custom field because in our business processes a lot of people need this information, not only financial or sales teams
I’m gonna ​@Abdul solution , sales team will love this when adding sales part to their customer contracts


Reply