I wouldn’t even pursue this, you are just asking for more problems and trouble every time there is an update or upgrade.  Not to mention, paying for the change every time there is an update or upgrade.  Your time would be better served convincing your users, customers, or whomever is asking that it is a really bad idea.  There are few views and columns where you can change things as part of the setup, but that is the exception rather than the rule.

So changing the column names in the front end isn’t feasible in Apps 10 just like for the previous versions of IFS Applications. This is the answer I was looking for.

Thanks!

As a work-around, you could create a custom field just to use its label. In the form layout, move the label for the standard field behind its data box, then move the label for the custom field next to the standard field. (You’ll also need to ditch the custom field’s data box somewhere out of sight.)

This workaround could work, thanks!

Hi, @Srikanth- did you try this ? Did it work? We have a similar issue in our Project data.

“As a work-around, you could create a custom field just to use its label. In the form layout, move the label for the standard field behind its data box, then move the label for the custom field next to the standard field. (You’ll also need to ditch the custom field’s data box somewhere out of sight.)”

Hi @CMOMKIR - Our business user decided not to pursue this workaround since it wasn’t something they absolutely needed. It was more like a ‘is is possible to do in IFS 10’ question.

But the workaround should work. Have you already tried it?

Hi @Srikanth ,

thanks for your reply, we haven’t tried this yet. What do you think @pekkan ?

BR

Miia

Can't you just use the Translation Manager? You can change all the field captions there, even in the English language.

Hello All,

We are currently using IFS 10 UPD 22, can anyone confirm if I can change the label of any IFS standard field without customization?

If yes, please let me now the steps.

Regards

@SaaAvinak search for the LU name at the beginning of the path. I filtered it on language code en also. The base language is PROG which is generally English.  But you can go in and add or change the translation. Save it.

When you’re all done with any changes, right click and refresh Language Cache. Next time you log in you should have the new translations.

I didn’t have to use the Approve Translation when I used it, not sure what drives it.